Open a support ticket
File a ticket on your plan's desk from outside code, and poll it until someone replies.
ticket_api_submit opens a ticket on the desk your API key's plan owns, the same desk the
dashboard's Ticketing screen manages. ticket_api_get reads one back, including the public
replies, everything you need to build a "contact us" form backed by a real desk instead of a
mailbox.
Methods
API: Submit Ticket
External service: opens a ticket on the desk owned by the API key. Requires a plan with full API access.
API: Get Ticket
External service: one ticket with its public interactions. Internal notes are never returned.
Walkthrough
Submit the ticket
name, email and details are required. The email doubles as the contact-book lookup:
resubmitting from the same address links to the same contact, the way
add a contact does.
2. Poll it for a reply
Save data.id from the submit call and read it back with ticket_api_get whenever you want to
check for movement; interactions only ever carries the public thread, internal desk notes are
filtered out before this method answers.
The response
Both methods answer the same narrow, external-safe ticket view, no owner ids, no internal state:
ticket_api_get adds one more key, interactions, an array of { direction, from, channel, body, ts } in thread order, empty until someone on the desk (or the requester, over another channel)
replies.