The Tooli Suite API and webhooks
What it is for
The API lets your own tools read what Tooli Suite holds for your organisation: its documents, websites, visitors and Event log, with the same figures the app shows. Webhooks send each view, click and visit to your server as it happens. Every route, filter and field is in the API reference, which is checked against the running API whenever Tooli Suite is tested.
Tooli Suite runs no AI model. The API is a way in for your own programs, with your organisation's own key.
Make a key
Owners and admins make keys, in Organisation → API.
- Choose New key and say what will use it.
- Choose what it can do: Read, or Read and write. Every route today reads, so a read-only key is all most tools need.
- Copy the key. It is shown once, and only its last four characters are kept where it can be read again.
Send it with every request, in the Authorization header:
curl -H "Authorization: Bearer $TOOLI_API_KEY" https://track.tooli.dev/api/v1/organization
A key reads what an admin of your organisation sees. It works only on /api/v1/, and a sign-in to the app never works there.
Roll or revoke
- Roll the key makes a new one with the same name and reach. The old one works for 24 more hours, then stops, so you have a day to change what uses it.
- Revoke stops a key at once.
Limits
Each key may make a set number of requests a minute; past it, the answer is 429 with a Retry-After header. The number is in the reference. Lists come in pages: pass back the answer's next as cursor for the page after.
Webhooks
In Organisation → API, choose Add webhook, give the https address to send to and choose the events: an email viewed, a link clicked, a document viewed, a visit to a website beginning. An organisation may have 10 webhooks.
Each delivery is signed the way the Standard Webhooks convention signs them, so a library you already have can check it: three headers, webhook-id, webhook-timestamp and webhook-signature, the signature an HMAC-SHA-256 of the id, the time and the body with your webhook's secret. Refuse a delivery whose time is far from your own clock, and drop one whose id you have already handled. Rolling the secret signs with both the old and the new for 24 hours.
A delivery that fails is tried again, waiting longer each time; the reference lists the waits. A webhook that has had nothing through for three days is switched off, and its page says so.
Exports
Tracked emails, Links, Documents, Websites, Visitors and the Event log each export to a CSV file, with the list's own filters and only what you may see. A link's page exports its clicks, a document's its views and a website's its page views.