PUT
/v1/admin/tickets/{ticket}A new subject, a new priority, or both. Only what you send changes, so renaming a ticket never puts back a priority a colleague changed meanwhile.
The trader sees a new subject too, in their own list of tickets. Write it for them.
Answers with the ticket as it is now.
Needs a firm. Our own staff name one with the Propper-Workspace header.
Request
| Field | Description |
|---|---|
subject | Up to 150 characters. Not empty when sent |
priority | low, normal, high or urgent |
curl -X PUT "https://api.proppertrading.com/v1/admin/tickets/tkt_cbqjrnz84cq45ca7" \
-H "Authorization: Bearer ptat_9f2c1a44_3b8e7d2f5c9a1b4e6d8f0a2c4e6b8d1f" \
-H "Propper-Workspace: acme" \
-H "Content-Type: application/json" \
-d '{"subject": "Moving to a 100K account", "priority": "normal"}'
Response
The ticket, with its new subject and priority.
Errors
| Status | Code | Meaning |
|---|---|---|
| 400 | workspace_required | Asked by our own staff without naming a firm |
| 401 | invalid_token | Not a token, or the secret does not match |
| 401 | revoked_token | Signed out here or from another device |
| 401 | expired_token | Ninety days without use, or a set expiry passed |
| 403 | admin_access_required | This account no longer helps run the environment |
| 403 | insufficient_scope | This device does not hold admin:write |
| 403 | workspace_not_permitted | The Propper-Workspace header names an environment this account cannot act in |
| 403 | forbidden | Without view_tickets and manage_tickets |
| 404 | resource_not_found | No ticket with that id in this firm |
| 409 | ticket_ended | The ticket was resolved or closed |
| 422 | validation_failed | An empty subject or one longer than 150 characters, or an unknown priority |