Log time against a ticket
Record minutes worked on this ticket, optionally marked billable.
/v1/tickets/{ticket_id}/time-logsEditor- Operation id
- create_time_log
- Access
- A viewer is refused.
/v1/tickets/{ticket_id}/time-logsRecord minutes worked on this ticket, optionally marked billable.
The entry is attributed to the calling user and also appears on the ticket
timeline as a time_log event. Minutes must be at least 1 and strictly less
than 43200 (30 days). The bound is exclusive.
Tenancy: the request is scoped to one workspace, and the credential presented is what selects it. A caller with no membership in that workspace is refused with 404, which is indistinguishable from a workspace that does not exist.
Authorisation: editor, admin or owner. A viewer receives 403 insufficient_role.
Access: Authorization: Bearer carrying either a realm access token or an API key. A key must hold the ticket-rail:write scope, and the workspace role of the person who owns it must meet the floor above.
A realm-issued access token, presented as Authorization: Bearer <token>. It acts as the person who signed in, and every operation resolves their workspace role live from the membership record.
In: header
Path Parameters
uuidRequest Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/tickets/497f6eca-6276-4993-bfeb-53cbbbba6f08/time-logs" \ -H "Content-Type: application/json" \ -d '{ "minutes": 45 }'{}Reopen a solved or closed ticket
Reopen a terminal ticket (solved/closed). Sets status=open, stamps reopened_at, emits a `reopen` event, and re-stamps SLA so the timer is honest about how long the next leg has to...
Add a todo to a ticket
Create a follow-up item on this ticket, optionally assigned and with a due date. New todos are appended to the end of the list.