API and webhooks
Create and update tickets from other tools, and let other tools know when a ticket reaches a step.
Most teams never need this. But if you have a website, a booking tool or an accounting system that should talk to TicketStacker, the API is there.
API tokens
Company Admins create tokens in Settings → API & webhooks: click Create token, give it a name (like Website), and copy it right away. You won't be able to see it again. Revoke a token anytime.
The same page has a short guide to Using the API. In short, you can:
- list your stacks with their fields, statuses and steps,
- create a ticket (title, fields, due date, owner, requester),
- update it, add comments, move it to a step, or close it.
A token only ever reaches your own company's data. Every endpoint, with examples, is in the API reference.
Webhooks
Add a Call a web address (webhook) automatic action to a step. When a ticket arrives there, TicketStacker sends the ticket to that address. Each request is signed (the X-TicketStacker-Signature header), so the other side can check it came from you. See Webhooks for the payload and code to check it.
No code? Use Zapier, Make or n8n
Connect TicketStacker to Slack, Google Sheets, QuickBooks and thousands of other apps. See Connect TicketStacker to other apps.
During the pilot, API access and webhooks turn on once we activate your company.
Related
- API referenceCreate, update, move and close tickets from your own code or other tools, with a simple JSON API and a token.
- WebhooksHave TicketStacker call your system the moment a ticket reaches a step, with a signed JSON payload you can trust.
- Connect TicketStacker to other appsUse Zapier, Make or n8n to link TicketStacker with Slack, Google Sheets, QuickBooks and thousands of other apps, without writing code.
- Automatic actionsLet a step assign the owner, fill in a field or call another system, so routine busywork happens by itself.
Still stuck? Email hello@ticketstacker.com. A real person reads every message.