Skip to main content
The TIKT API lets your own tools do what you do in the console, for one workspace:
  • Read your leads with their full profile, their score and the verdict on each criterion of your ICP; the posts, the tracked profiles, the lists, your credits, the events.
  • Answer TIKT from a scenario: add a lead to a list, discard it or restore it, exclude its company, pause a post or a profile, track a new profile, turn a workflow on or off, manage your webhook destinations.
Everything the API does, the console does too, under the same rules: what you can’t do in the console, you can’t do with the API. The API does not start a harvest and does not spend credits.

​
The address

Every request carries an API key in the Authorization header — see Authentication. Every answer is JSON.
Server to server only. Never call the API from a web page: the key would be visible to anyone who opens it. The API sends no CORS headers, so browsers refuse its answers anyway.

​
Webhooks or the API?

They work together. Webhooks bring TIKT’s news to you as it happens: a new lead, a lead who comes back. The API is how you fetch more, catch up, or answer back. A common pattern: a webhook delivers lead.matched, your scenario checks the lead in your CRM, then calls the API to file it in a list. See Syncing changes.

Quickstart

Create a key and read your first leads, in five minutes.

Authentication

The two kinds of keys, and how to keep them safe.

Pagination

Read long lists page by page, without missing anything.

Errors

What each status and code means.

Rate limits

How many calls, and how to stay well within them.

Syncing changes

Keep a CRM up to date with what changed.
The API reference, in the menu, describes each of the 64 operations with its parameters and its answer, and lets you try them with your key.