Support infrastructure behind one clean API
Everything in TickOS is available through a documented REST API. Create tickets from your app, send transactional email, sync contacts and react to events with signed webhooks.
- API resources20+
- spec at /v1/openapi.jsonOpenAPI
- SHA-256 signed webhooksHMAC
- requests per minute on Enterprise6,000
01 — REST API
Everything in the dashboard, available through the API
Tickets, messages, customers, emails, campaigns, contact groups, automations, changelog, tags, inboxes and surveys. Authenticate with an API key and get predictable JSON back.
- Bearer API keys, full or read-only
- Keys revocable, with last-used time
- OpenAPI 3 spec
- cURL, JavaScript and Python examples
- Consistent errors and pagination
- Per-plan rate limits
- GET/tickets42 ms200
- POST/tickets/{id}/messages
- POST/emails
- PATCH/customers/{id}
- GET/campaigns
- POST/contact-groups/{id}/members
- POST/automations/trigger
- GET/changelog
- DELETE/tags/{id}
02 — Webhooks
React to every ticket in real time
Subscribe an endpoint per inbox and receive events as they happen. Every delivery is signed with your secret so you can verify it came from TickOS.
- ticket.created, updated, closed, deleted
- message.created
- inbox.updated and inbox.deleted
- X-Tickos-Signature with HMAC-SHA256
- Timestamped to block replays
- Per-inbox configuration
03 — Email infrastructure
Transactional email by API or SMTP
Send from your verified domain with POST /v1/emails or point any SMTP client at smtp.tickos.dev. Schedule sends, attach files and track opens and clicks.
- POST /v1/emails with scheduling
- SMTP relay on port 587
- Attachments and HTML or text
- Open and click tracking
- Automatic bounce suppression
- SPF, DKIM and DMARC setup guided
SMTP relay · Nodemailer
- host
- smtp.tickos.dev
- port
- 587
- user
- apikey
- pass
- sk_live_••••••••••
Add X-Track-Opens to enable tracking.
04 — Developer tooling
Debug in the dashboard, not in production
Try any endpoint in the Playground, inspect every request in Logs and follow events from the API, dashboard and system in one timeline.
- Playground for live requests
- Request logs from 5 minutes to 90 days
- Filter by 2xx and 4xx
- Event stream by source
- SMTP logs and stats
- In-app API reference
What teams build on the API
A few of the patterns we see most.
In-app support
Create tickets straight from your product's help widget.
Transactional email
Receipts, magic links and alerts from your domain.
Event pipelines
Stream ticket events to your data warehouse or CRM.
Automation triggers
Enroll users into workflows from your backend.
What's new panels
Render your changelog inside your app.
Legacy apps
Anything that speaks SMTP can send through TickOS.
API surface
Base URL https://api.tickos.dev/v1 — the full reference lives in the docs.
$ curl https://api.tickos.dev/v1/openapi.json | jq '.paths | keys'
# support
- /v1/tickets
- /v1/messages
- /v1/customers
- /v1/tags
- /v1/inboxes
- /v1/surveys
- /v1/emails
- /v1/campaigns
- /v1/contact-groups
- /v1/connections
# workflows
- /v1/automations
- /v1/automations/trigger
- /v1/changelog
# workspace
- /v1/users
- /v1/members
- /v1/invitations
- /v1/accounts
- /v1/keys
Create an API key in the dashboard and send it as Authorization: Bearer <key>. Keys can have full or read-only access.
More modules
NEW TICKET — from your team
Get an API key in under a minute
Create a workspace, generate a key and send your first request from the Playground.
PLAN
Free
TICKETS
Unlimited
TEAMMATES
Unlimited