Skip to main content

​
1. Create a key

In the console, open Settings › API (app.trytikt.com), then Create key.
  1. Name — say what the key is for, for example Make · CRM sync. One key per tool: you can then revoke one without breaking the others.
  2. Access — Read only to read leads, lists, posts, tracked profiles and events; Read and write to also act on them (add leads to lists, discard leads, exclude companies…). See Authentication.
  3. Create key, then Copy. The key is shown once: paste it into your tool’s secret store now. If you lose it, revoke it and create another one.
A key looks like tikt_live_EXAMPLE…: tikt_live_ followed by 32 letters and digits. Below, it is in the TIKT_API_KEY environment variable.

​
2. Check the key

The answer names the key you called with and its workspace:
A 401 means the key is missing, mistyped or revoked — see Errors.

​
3. Read your leads

The leads whose job role matches your ICP and who meet at least 4 of its 5 criteria:
Each lead is the same object the webhooks send — every field is described in Objects. Without filters, GET /v1/leads returns what the Leads page shows: the leads at your workspace’s threshold, without the ones you discarded, newest first. has_more says another page follows: Pagination shows how to read it.

​
4. The same call in n8n

  1. Add an HTTP Request node.
  2. Method: GET. URL: https://api.trytikt.com/v1/leads.
  3. Authentication: a generic Header Auth credential, with Name Authorization and Value Bearer followed by your key.
  4. Turn on Send Query Parameters and add criteria_met = job_role and min_score = 4.
  5. Run the node: the leads are in data. Add a Split Out node on data to get one item per lead.

​
Next

  • Respond to TIKT from a scenario: file a lead in a list when your CRM marks it as contacted.
  • Rate limits: 120 reads per minute per workspace, and how to stay well under them.
  • The API reference, in the menu: every operation, with a playground where you paste your key.