Your own applications, for example a plugin, a desktop app or a website, can open tickets for their users and send technical details with them, such as the version of the application or the server. Each application gets its own key. Revoke a key, and that application stops at once.
Where to find it: Setup → Support → Application keys (administrators only).
Create an application key
- Open Setup → Support → Application keys.
- Enter the name of the Application, for example
WordPress plugin. Staff see this name as the channel of the tickets it opens. - Choose the Product when the request names none, or Request must name the product.
- Click Create key.
- Copy the key now and keep it in the settings of the application. It is shown only this once; Ticketix stores only a hash of it.
The list shows each application with the start of its key, its product, the number of its tickets, when it was Last used and when it was created. Revoke stops a key at once; tickets that the application opened keep its name.
Open a ticket
Send a POST request with a JSON body to /api/ticket-create.php under the address of your installation, for example https://support.example.com/api/ticket-create.php. Send the key in the Authorization: Bearer header, or in X-Ticketix-Key where your server drops the Authorization header.
POST /api/ticket-create.php
Authorization: Bearer tkx_…
Content-Type: application/json
{
"email": "customer@example.com",
"name": "Customer Name",
"product": "helpdesk",
"subject": "Licence shows Inactive after moving the site",
"message": "We moved the site to a new domain …",
"priority": "normal",
"technical_details": {
"WordPress": "6.8",
"PHP": "8.3",
"Plugin version": "2.0.2"
}
}
| Field | Required | Meaning |
|---|---|---|
| Yes | The customer's email address; a new customer is created for an unknown address | |
| name | No | The customer's name, up to 120 characters |
| product | No | A product key; without it, the product of the key is used |
| subject | Yes | Up to 200 characters |
| message | Yes | Plain text, up to 20,000 characters |
| priority | No | low, normal (default) or high |
| technical_details | No | Up to 30 names and values; a name up to 60 and a value up to 500 characters; values are text, numbers or true and false |
The request body can be up to 64 KB.
What happens with the ticket
- The ticket is open at once; the key vouches for the request, so there is no email verification.
- The customer receives the usual Ticket created email with the ticket link, and staff receive the usual notifications.
- Routing rules, workflows, SLA policies and AI triage run as for any new ticket.
- The ticket screen shows the name of the application as the channel, "with technical details", and the technical details under the first message ("Sent by" and the application name). The customer sees the same details on their ticket.
Answers
| Status | Meaning |
|---|---|
| 201 | The ticket was opened; the answer contains ticket_no and status |
| 401 | The key is missing, wrong or revoked |
| 405 | The request was not a POST |
| 413 | The body is larger than 64 KB |
| 415 | The body is not JSON (Content-Type: application/json) |
| 422 | A field is wrong; fields names each field with the reason |
| 429 | Too many tickets: 60 an hour per application and 10 an hour per customer |
On Nginx, the server must run PHP in the api folder; see Ticketix server requirements.