ZYNT
API / v1.0.0Get an API key

For developers

ZYNT API

Read your signals, events, companies and people over HTTP, rate, star, move and assign your signals, add, rate and answer events, add tasks and notes, fill your audiences, change your statuses, excluded companies, notifications and preferences, send your business notes to a setup, and get webhooks when signals arrive or are assigned.

Set up ZYNT with your AI agent

  1. Sign up, or sign in.
  2. Connect ZYNT to Claude, ChatGPT, Codex or Claude Code.
  3. In a new chat, paste: Set up ZYNT for me: read https://getzynt.com/agent-setup.md and follow it.

Your agent follows the setup guide. How it works

01

Get a key

Open Settings, API keys and press New key. Give it a name you will recognise later, for example the name of the script that uses it.

The secret is shown one time. Copy it now and keep it somewhere safe. If you lose it, revoke the key and make a new one. Revocation can take up to 30 seconds to reach every server.

A key belongs to one user, in one organization. It reads the signals and events available to that user in the app, and it can rate, move and assign those signals as that user. Anyone who has the key can do the same, so keep it as safe as a password.

02

Your first call

Bash
curl https://app.getzynt.com/api/v1/signals \
  -H "Authorization: Bearer <your key>"

You get up to 25 of the newest signals. You do not send anything else. Your organization, and the scenarios you can see, come from the key.

JSON response
{
  "data": [
    {
      "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
      "scenario_id": "9a417d2e-6c3b-4f80-a195-7e2d4c6b8a01",
      "title": "Acme Robotics raises €18M to expand warehouse automation",
      "score": 97,
      "status": {
        "id": "3b7e2c9d-1a5f-4d68-b023-9c7e6a4f2d10",
        "name": "New",
        "type": "todo"
      },
      "assignee_id": null,
      "summary": "Acme Robotics announced a Series A round to grow its European operations.",
      "source_url": "https://news.example.com/acme-robotics-series-a",
      "image_url": "https://news.example.com/favicon.ico",
      "app_url": "https://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
      "received_at": "2026-09-01T08:14:00.000Z",
      "companies": [
        {
          "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
          "name": "Acme Robotics",
          "website_url": "https://acme-robotics.example",
          "linkedin_url": null,
          "description": "",
          "is_target": true
        }
      ],
      "favorite": false
    }
  ],
  "next_cursor": null
}

Every top-level signal field is returned unless you select specific fields with fields. Empty values are "", 0 or []. next_cursor, assignee_id, status, and company website_url and linkedin_url can be null. A score breakdown item omits explanation when none is available.

To read one signal in full, with the score breakdown and the people on it, replace the id below with one from your list:

Bash
curl https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d \
  -H "Authorization: Bearer <your key>"
03

Read every page

For signals and events, send the previous response's next_cursor as the cursor query parameter. When next_cursor is null, you have them all.

This example uses Bash, curl and jq. It starts at offset 0 and stops at the end of the list or if a request fails.

Bash
cursor=0
while true; do
  page=$(curl --fail-with-body -sS "https://app.getzynt.com/api/v1/signals?limit=100&cursor=$cursor" \
    -H "Authorization: Bearer <your key>") || break
  echo "$page" | jq -c '.data[]' || break
  cursor=$(echo "$page" | jq -er '.next_cursor // empty') || break
done

limit accepts 1 to 100. Without it you get 25.

Keep the same filters on every page. New records can arrive while you read. The cursor counts from the top of the list, so a record can move between pages. Keep the ids you already have and skip them.

05

Read and search events

GET /api/v1/events returns a page of events with dates, location, scores, and score breakdowns. Use search to match the event name, description, venue, or full location, and city to match the city. Both filters are case-insensitive, ignore blank values, and combine with AND.

Bash
curl --get "https://app.getzynt.com/api/v1/events" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "search=summit" \
  --data-urlencode "city=Warsaw" \
  --data-urlencode "limit=25"
JSON response
{
  "data": [
    {
      "id": "7c13...",
      "title": "Technology Summit",
      "source_url": "https://example.com/events/technology-summit",
      "website_url": "https://example.com/summit",
      "app_url": "https://app.getzynt.com/events?eventId=7c13...",
      "start_at": "2026-10-15T08:00:00.000Z",
      "end_at": "2026-10-15T16:00:00.000Z",
      "location_name": "Conference Centre",
      "location_address": "Warsaw, Poland",
      "city": "Warsaw",
      "is_virtual": false,
      "score": 74,
      "score_breakdown": {
        "items": [
          {
            "key": "audience-value",
            "label": "audience-value",
            "icon": "users",
            "points": 18,
            "max_points": 20
          }
        ],
        "recommendation": "Book a meeting slot with the logistics track speakers."
      },
      "watched_participants": [
        {
          "id": "company_123",
          "type": "company",
          "name": "Northwind Logistics",
          "role": "exhibitor"
        }
      ]
    }
  ],
  "next_cursor": null
}

Pagination uses cursor and limit, just like signals. Event endpoints always return all their fields; they do not support fields selection. To also get the description, key insights, and nullable topic, use GET /api/v1/events/{id} with an id from your event list:

Bash
curl "https://app.getzynt.com/api/v1/events/7c13..." \
  -H "Authorization: Bearer <your key>"

To check your API key, call GET /api/v1/healthwith the same Authorization header. A valid key returns {"status":"ok"}.

06

Follow a company or person

When you know the company, look it up by its LinkedIn URL or website. Add include=signals to get its 10 newest signals in the same call. For a person, call /api/v1/people/lookup with their LinkedIn URL. A company or person ZYNT does not know returns 404.

Bash
curl --get "https://app.getzynt.com/api/v1/companies/lookup" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "linkedin_url=https://www.linkedin.com/company/acme-robotics" \
  --data-urlencode "include=signals"
JSON response
{
  "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
  "name": "Acme Robotics",
  "domain": "acme-robotics.example",
  "website_url": "https://acme-robotics.example",
  "linkedin_url": "https://www.linkedin.com/company/acme-robotics",
  "description": "Warehouse automation robots for European logistics.",
  "industry": "Automation Machinery Manufacturing",
  "employee_range": "51-200",
  "location": "Wrocław, Poland",
  "logo_url": "https://media.example.com/acme-robotics.png",
  "is_target": true,
  "signals": {
    "data": [
      {
        "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
        "scenario_id": "9a417d2e-6c3b-4f80-a195-7e2d4c6b8a01",
        "title": "Acme Robotics raises €18M to expand warehouse automation",
        "score": 97,
        "status": {
          "id": "3b7e2c9d-1a5f-4d68-b023-9c7e6a4f2d10",
          "name": "New",
          "type": "todo"
        },
        "assignee_id": null,
        "summary": "Acme Robotics announced a Series A round to grow its European operations.",
        "source_url": "https://news.example.com/acme-robotics-series-a",
        "image_url": "https://news.example.com/favicon.ico",
        "app_url": "https://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
        "received_at": "2026-09-01T08:14:00.000Z",
        "companies": [
          {
            "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
            "name": "Acme Robotics",
            "website_url": "https://acme-robotics.example",
            "linkedin_url": null,
            "description": "",
            "is_target": true
          }
        ],
        "favorite": false
      }
    ],
    "next_cursor": null
  }
}

You also find a company id in companies on any signal, and a person id in people on /api/v1/signals/{id}.

To get that company’s signals, add company_id to the signal list. For a person, use person_id. You get the same signals as the profile in the app, and every other signal filter still works.

Bash
curl --get "https://app.getzynt.com/api/v1/signals" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "company_id=7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49"

The timeline lists every source that mentions the company: news, articles, LinkedIn posts, comments, reactions, job posts and signals. It is the same timeline as the profile in the app. Newest come first; send sort=oldest to start from the oldest. occurred_at is when ZYNT found the source. For a person, call /api/v1/people/{id}/timeline.

Bash
curl --get "https://app.getzynt.com/api/v1/companies/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49/timeline" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "period=90" \
  --data-urlencode "limit=25"
JSON response
{
  "data": [
    {
      "id": "5b8e2f14-7a3c-4d91-b6e0-2c4f8a1d9e73",
      "kind": "news",
      "title": "Acme Robotics opens a second plant in Gdańsk",
      "occurred_at": "2026-09-24T08:30:00.000Z",
      "relation": "subject",
      "evidence": "Acme Robotics will open a second plant in Gdańsk next spring.",
      "source": {
        "label": "example.com",
        "platform": null,
        "url": "https://example.com/news/acme-gdansk-plant"
      },
      "signal": {
        "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
        "score": 82,
        "scenario": "Manufacturing expansion",
        "app_url": "https://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d"
      }
    }
  ],
  "next_cursor": null
}

relation says whether the entity wrote the item (author), is what it is about (subject), or is only mentioned. When your organization has a signal from the source, signal holds its id; otherwise it is null. Narrow the list with kind, relation, period (30, 90, 365 or all days) and search. Pagination uses cursor and limit, like signals. An unknown id returns 404; a known id with nothing that matches returns an empty page.

To find the people to talk to, /api/v1/companies/{id}/employees lists who works at the company now. The relationships of a company or person list the companies and people tied to it, such as founders, employers, investors and partners, with the quotes that show it.

Bash
curl --get "https://app.getzynt.com/api/v1/people/2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816/relationships" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "section=business"
JSON response
{
  "data": [
    {
      "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
      "type": "company",
      "name": "Acme Robotics",
      "subtitle": "Automation Machinery Manufacturing · 51-200",
      "image_url": "https://media.example.com/acme-robotics.png",
      "is_target": true,
      "relationship": "Works at",
      "other_relationships": [],
      "section": "business",
      "direction": null,
      "status": "current",
      "last_confirmed_at": "2026-10-02T07:40:00.000Z",
      "details": [
        {
          "key": "role",
          "value": "Head of Operations"
        }
      ],
      "evidence": [
        {
          "quote": "Anna Nowak, Head of Operations at Acme Robotics, said the new site opens in March.",
          "source": "logistics-news.example",
          "url": "https://logistics-news.example/acme-robotics-opens-poznan-site",
          "occurred_at": "2026-10-02T07:40:00.000Z",
          "confidence": 0.92
        }
      ]
    }
  ],
  "total": 1,
  "truncated": false,
  "next_cursor": null
}
07

Work with one list

A list (an audience) holds the companies or people you work on together, such as one client’s prospects. Make one with POST /api/v1/audiences, then send the rows in calls of up to 100 with the id the new list got as audience_id: 1,000 rows take 10 calls. ZYNT matches each row to a company it knows by its website, or adds it. Each result says which happened and gives the id; rows whose outcome is invalid or failed were not added.

Bash
curl -X POST "https://app.getzynt.com/api/v1/companies" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"audience_id":"6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63","companies":[{"name":"Nordwave Logistics","website_url":"nordwave-logistics.example","linkedin_url":"https://www.linkedin.com/company/nordwave-logistics"}]}'

Then read the list’s signals with audience_id. Every signal filter still works. Which companies on the list had a signal this week, the best signal of each:

Bash
curl --get "https://app.getzynt.com/api/v1/signals" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "audience_id=6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63" \
  --data-urlencode "received_after=2026-11-04" \
  --data-urlencode "one_per_company=true" \
  --data-urlencode "sort=highest-score" \
  --data-urlencode "limit=100" \
  --data-urlencode "fields=id,title,summary,source_url,received_at,companies"

Each signal brings its summary, the one line on why it matters, its source_url and its companies. It counts for the company on the list its source names most. received_after is when ZYNT received the signal, not when the news happened. Follow next_cursor until it is null, as in Read every page.

With received_after 90 days back, the same call gives a hook for the first line of an email to each company that has one. A company missing from the answer has no signal ZYNT knows yet; one ZYNT watches only from today may need time. To find a topic, add search. It matches the words as written, with no synonyms, so run a few, such as hiring, SDR and account executive, and merge them by id. A digest of the past week is the same call without one_per_company, grouped by the signal’s companies whose is_target is true; ZYNT does not send it on a schedule.

For a person list, the signals are those that name its people.

A signal comes after ZYNT scores a source, so a list added today can have news and no signals yet. For “any news about my list?”, read the list’s timeline: every source about its members as soon as ZYNT finds it, newest first, each with the member it is about. Start with the last 7 days; with nothing there, ask for 30, then 90.

Bash
curl "https://app.getzynt.com/api/v1/audiences/6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63/timeline?period=7" \
  -H "Authorization: Bearer <your key>"
08

Rate, move and assign a signal

A key can change a signal the way its user does in the app. Send JSON with the Content-Type: application/json header. To rate a signal, send 1 to 5 stars and an optional comment:

Bash
curl -X PUT "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/feedback" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"stars":4,"comment":"Good fit, talking to them next week"}'

A signal has one rating, as in the app. Each call replaces the last one, whoever sent it, and the app shows it as rated by the key’s user. The app shows 1 or 2 stars as less like this and 3 to 5 as more like this. Send "stars": null to clear it. When the signal has no assignee, 3 stars or more assign it to the key’s user if their Assign signals I want more of setting is on. Send "auto_assign": false to keep it unassigned, or true to assign it whatever the setting says. A signal someone has stays theirs unless the key’s user has Take over from the current owner on.

To move a signal to a status or give it to a teammate, send the status name your team sees in ZYNT and the teammate’s email. Send either one alone, or "assignee": null to unassign. A new status can assign the signal to the key’s user when their Assign signals I move setting is on; an assignee you send wins. You get the signal back as GET /api/v1/signals/{id} returns it.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"status":"Contacted","assignee":"anna@acme-sales.example"}'

GET /api/v1/statuses lists the status names and ids. A name is matched without case. An id keeps working after someone renames the status. GET /api/v1/members lists your teammates’ emails and ids. An unknown status or assignee returns 400 and changes nothing.

To make the same change on many signals, send their ids as ids to PATCH /api/v1/signals, up to 100 at once. The answer lists the ids that changed and the ones ZYNT could not find.

09

Record the follow-up

Record what happens next where your team sees it. Add a task to a signal:

Bash
curl -X POST "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/tasks" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"text":"Call Anna Nowak about the warehouse rollout"}'

Tick it later with PATCH and "done": true on /tasks/{task_id}. A task id stays the same when other tasks come and go. Notes work the same way on a signal, company, person or event: /api/v1/companies/{id}/notes takes content and public. A note is private to the key’s user unless public is true, and reading notes returns their private ones too, so check public before you post one in a shared channel. To put a company or person on one of your team’s lists, take its id from /api/v1/audiences and send PUT to /api/v1/audiences/{id}/members/{record_id}.

Star a signal for the team with PUT on /api/v1/signals/{id}/favorite, and list the starred ones with favorite=true. Events take a rating on /feedback and the key user’s answer to “are you going” on /attendance. To add events ZYNT has not found, send links to their pages to POST /api/v1/events; they show in your events once ZYNT scores them.

An admin’s key also makes, renames and deletes lists on /api/v1/audiences; a deleted list cannot come back, so an agent asks before every deletion. To add companies or people ZYNT does not know yet, send them to POST /api/v1/companies with a website, or POST /api/v1/people with a LinkedIn profile and an email; they go on a list and ZYNT starts following them. GET /api/v1/people/{id}/contacts reads the emails and phones your team already has.

10

Change your settings

A key changes its user’s own settings the way Settings does in the app. Send only the fields you change; the rest stay as they are, and you get every setting back as saved. To pick when the digest goes out and which new signals reach it:

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/me/notifications" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"digest_time":"08:30","rules":{"new_signal":{"minimum_score":80}}}'

/api/v1/me/preferences holds when signals become the user’s and the instructions ZYNT follows in the outreach messages it writes for them. Two settings belong to the whole team: excluded companies, which any member changes with PUT and DELETE on /api/v1/exclusions/{company_id}, and statuses, which only an admin adds, renames and deletes on /api/v1/statuses.

Writing skills, the briefs ZYNT follows in outreach messages, live on /api/v1/writing-skills. A manager invites people on /api/v1/invitations and changes roles or removes people on /api/v1/members/{user_id}. A key can make and revoke its user’s keys on /api/v1/api-keys; a new key’s secret shows only once.

11

Set ZYNT up with your agent

An AI agent can set ZYNT up for the user. An assistant connects through MCP (Connect an AI assistant) and follows the setup guide; no key goes into a chat. A script with an API key follows the API setup guide: it reads the setup with GET /api/v1/setup and answers each question with POST /api/v1/setup/answer, as the user would, while the user watches in the app.

Bash
curl -X POST "https://app.getzynt.com/api/v1/setup/answer" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"revision":7,"answer":{"kind":"text","text":"Poland first, then Germany"}}'

An agent that already knows the business, such as one running GTM Brain, first sends what it knows once, so the setup asks only what the files leave open. The files go to the setup the key’s user has open: their sign-up, or a scenario they add in Settings, Business. One setup reads 20 files in all.

Bash
curl -X POST "https://app.getzynt.com/api/v1/setup/context" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"files":[{"name":"context.md","path":"brain/contexts/icp/context.md","content":"## Who buys\n- Heads of logistics at mid-size carriers (customer interviews)\n\n## Markets\n- Poland first, then Germany (strategy.md)"}]}'

ZYNT reads each file and adds what it states as guesses. The answer holds counts only; the user confirms the guesses on the setup’s summary, in the app or through the agent once they agree. ZYNT keeps the files and no endpoint returns their text, so never send passwords, keys, personal emails or copied conversations.

12

Get signals in Slack

A webhook tells your tool about signals as they happen, within a few minutes. In Slack, make a workflow that starts from a webhook with a text variable and posts it, or add an incoming webhook, and register its URL. With assignee, the webhook gets only the signals given to that teammate, so each person can have their own:

Bash
curl -X POST "https://app.getzynt.com/api/v1/webhooks" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://hooks.slack.com/triggers/T0123ABCD/8123456789/3f9c2b7e1d4a","events":["signal.assigned"],"assignee":"anna@acme-sales.example"}'

Without assignee, send ["signal.created"] for every new signal about a company or person on your watchlist, the default lists of companies and people in Audiences, or ["signal.assigned"] for every signal given to someone. Add audience_id to ["signal.created"] to get the new signals about one list instead, such as one client’s accounts in their Slack channel. The answer holds the signing secret, once. Check the URL with POST /api/v1/webhooks/{id}/ping. Each event is signed with the Standard Webhooks headers and carries the whole signal:

JSON body
{
  "id": "signal.assigned:c41e7a92-5b3d-4f68-8a20-9e6d1b7c3f58",
  "type": "signal.assigned",
  "created_at": "2026-11-10T10:02:00.000Z",
  "text": "Signal for Anna Kowalska (score 97): Acme Robotics raises €18M to expand warehouse automation\nhttps://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
  "data": {
    "signal": {
      "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
      "scenario_id": "9a417d2e-6c3b-4f80-a195-7e2d4c6b8a01",
      "title": "Acme Robotics raises €18M to expand warehouse automation",
      "score": 97,
      "status": {
        "id": "6d2a9f41-8c7e-4b35-a0d6-1f3e5b7c9a82",
        "name": "Contacted",
        "type": "in_progress"
      },
      "assignee_id": "user_2nX8kQvB4yLmR7tZ",
      "summary": "Acme Robotics announced a Series A round to grow its European operations.",
      "source_url": "https://news.example.com/acme-robotics-series-a",
      "image_url": "https://news.example.com/favicon.ico",
      "app_url": "https://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
      "received_at": "2026-09-01T08:14:00.000Z",
      "companies": [
        {
          "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
          "name": "Acme Robotics",
          "website_url": "https://acme-robotics.example",
          "linkedin_url": null,
          "description": "",
          "is_target": true
        }
      ],
      "favorite": false,
      "score_breakdown": {
        "items": [
          {
            "key": "strategic_value",
            "label": "strategic",
            "icon": "trending-up",
            "explanation": "The expansion matches the workspace growth priorities.",
            "points": 28,
            "max_points": 30
          },
          {
            "key": "bonus_factors",
            "label": "bonus",
            "icon": "award",
            "points": 7,
            "max_points": 10
          }
        ],
        "recommendation": "Review the round and contact the expansion lead."
      },
      "reasoning": "The funding, region and operating focus make this a high-priority signal.",
      "sector": "Industrial automation",
      "people": [
        {
          "id": "2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816",
          "first_name": "Anna",
          "last_name": "Nowak",
          "title": "Head of Operations",
          "company_name": "Acme Robotics",
          "linkedin_url": "https://www.linkedin.com/in/anna-nowak",
          "is_target": true,
          "signal_role": "Leads the expansion"
        }
      ]
    },
    "assignee": {
      "id": "user_2nX8kQvB4yLmR7tZ",
      "name": "Anna Kowalska",
      "email": "anna@acme-sales.example"
    }
  }
}

In your own code, a receiver is this small server: it checks the signature and posts each event to a Slack incoming webhook. It needs Node 18 or newer and no packages:

server.mjs
// server.mjs: run with node server.mjs (Node 18 or newer)
import { createHmac, timingSafeEqual } from 'node:crypto'
import { createServer } from 'node:http'

const secret = Buffer.from(
  process.env.ZYNT_WEBHOOK_SECRET.replace(/^whsec_/, ''),
  'base64',
)
const slackUrl = process.env.SLACK_WEBHOOK_URL

// Standard Webhooks: v1,<base64 HMAC-SHA256 of id.timestamp.body>
function signedByZynt(headers, body) {
  const timestamp = Number(headers['webhook-timestamp'])
  if (Math.abs(Date.now() / 1000 - timestamp) > 5 * 60) return false
  const expected = Buffer.from(
    createHmac('sha256', secret)
      .update(`${headers['webhook-id']}.${timestamp}.${body}`)
      .digest('base64'),
  )
  return String(headers['webhook-signature'])
    .split(' ')
    .map((part) => Buffer.from(part.replace(/^v1,/, '')))
    .some(
      (signature) =>
        signature.length === expected.length &&
        timingSafeEqual(signature, expected),
    )
}

createServer(async (request, response) => {
  let body = ''
  for await (const chunk of request) body += chunk
  if (!signedByZynt(request.headers, body)) return response.writeHead(401).end()

  // Answer at once: ZYNT waits 10 seconds, then sends the event again.
  response.writeHead(204).end()

  const event = JSON.parse(body)
  await fetch(slackUrl, {
    method: 'POST',
    headers: { 'Content-Type': 'application/json' },
    body: JSON.stringify({ text: event.text }),
  })
}).listen(3000, () => console.log('Waiting for ZYNT on http://localhost:3000'))

ZYNT posts only to a public https address, so on your own computer put a tunnel in front of the server, register the tunnel’s address, start the server with the secret from that answer and send a ping. The ping lands in Slack and shows the whole path works:

Bash
# 1. Give your computer a public https address (cloudflared, free, no account)
cloudflared tunnel --url http://localhost:3000
#    It prints https://<random>.trycloudflare.com; keep it running.

# 2. Register that address for new signals; the answer holds id and secret
curl -X POST "https://app.getzynt.com/api/v1/webhooks" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://<random>.trycloudflare.com", "events": ["signal.created"]}'

# 3. Start the server with that secret and your Slack incoming webhook
ZYNT_WEBHOOK_SECRET="whsec_..." \
SLACK_WEBHOOK_URL="https://hooks.slack.com/services/..." \
node server.mjs

# 4. Send a test event; it shows in Slack within seconds
curl -X POST "https://app.getzynt.com/api/v1/webhooks/<id>/ping" \
  -H "Authorization: Bearer <your key>"
13

When something goes wrong

Every error has the same shape: error is the code to branch on, message says what went wrong, and hint says what to do next. Show the message to a person; an agent can follow the hint.

JSON response
{
  "error": "not_found",
  "message": "ZYNT does not know a company by this key",
  "hint": "Try the other key (linkedin_url or website), or find companies with /api/v1/companies/search. ZYNT does not add companies on lookup."
}
CodeMeaningWhat to do
400The body is not valid JSON, the status, assignee or scenario in it is unknown, or the setup does not take this answer nowSend a status name from /api/v1/statuses; unknown_status lists them in allowed. Send an email or id from /api/v1/members as assignee. unknown_scenario lists your scenario ids in allowed. unknown_answer lists the answers the setup takes now in allowed.
401The key is missing, wrong, or revokedCheck the Authorization header. Make a new key.
403The key’s user cannot read or change this, or the feature is off for your organizationUse a key of a user with access; only an admin changes statuses. For feature_disabled, ask ZYNT to turn the feature on.
404The id does not exist or is not yours, or ZYNT does not know the company or person you looked upUse an id from your own list, a lookup, a search or a signal. For a company lookup, try the other key.
409The status still has signals or is the status new signals get, it is the last status of its type, the key’s user has no setup open, the setup moved on since you read it, your team has as many lists, writing skills or people as it can, the user has as many keys as they can, or the person is already on the teamSend move_to with another status for its signals. Keep at least one status of each type. For no_open_setup, its message says what state the setup is in and its hint what to tell the user (reason names the case); usually they click New scenario in Settings → Business, or a new account signs up at /sign-up. For setup_changed, read the setup again and answer its new question. For the limits, delete a list or a skill, revoke an invitation or a key, or remove a member.
415A body was sent without the Content-Type: application/json headerSend the body as JSON with that header.
422A parameter or a body field is invalid, for example limit=101 or stars=6Send limit between 1 and 100, a valid cursor, supported field names, and only the body fields the endpoint lists.
429The setup has read the 20 files of notes it takes, or your team sent as many invitations as an hour allowsSend only the files that matter most, or let the user finish the setup in the chat. For rate_limited, wait an hour.
503A required service is temporarily unavailableWait a moment and retry.
500The server could not complete the requestRetry later. Contact support if the error persists.

AI assistants

Connect an AI assistant

Same data as the API, but for an AI assistant instead of a script. Add ZYNT as a custom connector and it reads your signals and events directly, no dashboard, no copy-paste. Works with Claude, ChatGPT, Codex and Claude Code, and any MCP client that supports OAuth. It can also do what the API writes: rate, move and assign signals, add tasks and notes, add events from links, rate events and say whether you go, fill audiences, and change statuses, excluded companies, your notifications and your preferences. A connection added before the assistant could make changes only reads: remove the ZYNT connector and add it again. In Codex, run codex mcp logout zynt, then codex mcp login zynt.

Connector URL
https://app.getzynt.com/mcp

It signs in with your ZYNT account, not your API key. There is no separate MCP key to generate or revoke. This is a remote connector, over Streamable HTTP, not a local command your client runs over stdio, so there is nothing to install.

Claude

  1. 1Open Customize, Connectors, and click the + button.
  2. 2Click Add custom connector.
  3. 3Paste the connector URL above.
  4. 4Claude opens your browser to sign in. Approve it.

Free, Pro, Max, Team and Enterprise all work. On Team and Enterprise, an Owner adds the connector once under Organization settings, Connectors, then each member connects from Customize, Connectors.

ChatGPT

  1. 1Open chatgpt.com/plugins, click Add, then Create MCP server.
  2. 2Paste the connector URL above and pick Streamable HTTP.
  3. 3Pick OAuth and leave the client ID and secret empty.
  4. 4ChatGPT opens your browser to sign in. Approve it.

Not every ChatGPT plan can add a custom MCP server. On a workspace, an admin may have to allow it first. If ZYNT does not show in a chat, turn it on there.

Codex

  1. 1In a terminal, run codex mcp add zynt --url and the connector URL above.
  2. 2Codex opens your browser to sign in. Approve it.
  3. 3Open a new chat: Codex loads the tools when a chat starts.

ZYNT is listed already, or the sign-in did not finish: run codex mcp login zynt. No API key or header is needed.

Claude Code

  1. 1In a terminal, run claude mcp add --transport http zynt and the connector URL above.
  2. 2In Claude Code, type /mcp and pick zynt.
  3. 3Claude Code opens your browser to sign in. Approve it.

Claude Code connects over Streamable HTTP and signs in with OAuth. No API key or header is needed.

The following tools are exposed:

list_signalsSame as GET /api/v1/signals, with the same parameters.
get_signalSame as GET /api/v1/signals/:id: signalId, fields.
list_eventsSame as GET /api/v1/events, with the same parameters, but timing defaults to upcoming.
get_eventSame as GET /api/v1/events/:id: eventId.
list_event_participantsSame as GET /api/v1/events/:id/participants: eventId, type, role, cursor, limit.
lookup_companySame as GET /api/v1/companies/lookup: linkedin_url or website, include.
lookup_personSame as GET /api/v1/people/lookup: linkedin_url, include.
search_companiesSame as GET /api/v1/companies/search, with the same filters. Needs lead search.
search_peopleSame as GET /api/v1/people/search, with the same filters. Needs lead search.
get_timelineSame as GET /api/v1/companies/:id/timeline and /people/:id/timeline: entity, id and the same filters.
get_list_timelineSame as GET /api/v1/audiences/:id/timeline: audienceId, period (7 by default), cursor, limit. The news about every member of one list.
list_employeesSame as GET /api/v1/companies/:id/employees: companyId, cursor, limit.
get_relationshipsSame as GET /api/v1/companies/:id/relationships and /people/:id/relationships: entity, id and the same filters.
rate_signalSame as PUT /api/v1/signals/:id/feedback: signalId, stars, comment, auto_assign.
update_signalSame as PATCH /api/v1/signals/:id: signalId, status, assignee.
update_signalsSame as PATCH /api/v1/signals: ids, status, assignee.
favorite_signalSame as PUT and DELETE /api/v1/signals/:id/favorite: signalId, favorite.
add_eventsSame as POST /api/v1/events: urls, scenario_id.
rate_eventSame as PUT /api/v1/events/:id/feedback: eventId, stars, comment.
set_event_attendanceSame as PUT /api/v1/events/:id/attendance: eventId, decision.
list_membersSame as GET /api/v1/members, as { members }.
list_invitationsSame as GET /api/v1/invitations, as { invitations }.
invite_memberSame as POST /api/v1/invitations: email, role.
revoke_invitationSame as DELETE /api/v1/invitations/:id: invitationId.
change_member_roleSame as PATCH /api/v1/members/:user_id: userId, role.
remove_memberSame as DELETE /api/v1/members/:user_id: userId. Always needs the user’s yes.
list_writing_skillsSame as GET /api/v1/writing-skills, as { skills }.
add_writing_skillSame as POST /api/v1/writing-skills: name, body, visibility.
update_writing_skillSame as PATCH /api/v1/writing-skills/:id: skillId, name, body, visibility.
delete_writing_skillSame as DELETE /api/v1/writing-skills/:id: skillId.
set_default_writing_skillSame as PUT /api/v1/writing-skills/default: id.
list_api_keysSame as GET /api/v1/api-keys, as { api_keys }.
create_api_keySame as POST /api/v1/api-keys: name, expires_in_days.
revoke_api_keySame as DELETE /api/v1/api-keys/:id: apiKeyId. Always needs the user’s yes.
list_statusesSame as GET /api/v1/statuses, as { statuses }.
create_statusSame as POST /api/v1/statuses: name, type, color.
update_statusSame as PATCH /api/v1/statuses/:id: statusId, name, color.
delete_statusSame as DELETE /api/v1/statuses/:id: statusId, move_to.
list_exclusionsSame as GET /api/v1/exclusions, as { companies }.
exclude_companySame as PUT /api/v1/exclusions/:company_id: companyId.
include_companySame as DELETE /api/v1/exclusions/:company_id: companyId.
get_preferencesSame as GET /api/v1/me/preferences.
update_preferencesSame as PATCH /api/v1/me/preferences, with the same fields.
get_notification_settingsSame as GET /api/v1/me/notifications.
update_notification_settingsSame as PATCH /api/v1/me/notifications, with the same fields.
list_tasksSame as GET /api/v1/signals/:id/tasks, as { tasks }: signalId.
add_taskSame as POST /api/v1/signals/:id/tasks: signalId, text.
update_taskSame as PATCH /api/v1/signals/:id/tasks/:task_id: signalId, taskId, done, text.
delete_taskSame as DELETE /api/v1/signals/:id/tasks/:task_id: signalId, taskId.
list_notesSame as GET /api/v1/:record/:id/notes, as { notes }: record (signals, companies, people or events), recordId.
add_noteSame as POST /api/v1/:record/:id/notes: record, recordId, content, public.
update_noteSame as PATCH /api/v1/:record/:id/notes/:note_id: record, recordId, noteId, content, public.
delete_noteSame as DELETE /api/v1/:record/:id/notes/:note_id: record, recordId, noteId.
list_audiencesSame as GET /api/v1/audiences, as { audiences }.
add_to_audienceSame as PUT /api/v1/audiences/:id/members/:record_id: audienceId, recordId.
remove_from_audienceSame as DELETE /api/v1/audiences/:id/members/:record_id: audienceId, recordId.
create_audienceSame as POST /api/v1/audiences: name, subject_type.
rename_audienceSame as PATCH /api/v1/audiences/:id: audienceId, name.
delete_audienceSame as DELETE /api/v1/audiences/:id: audienceId. Always needs the user’s yes.
add_companiesSame as POST /api/v1/companies: audience_id, companies.
add_peopleSame as POST /api/v1/people: audience_id, people.
get_person_contactsSame as GET /api/v1/people/:id/contacts: personId.
get_setupSame as GET /api/v1/setup: the setup chat, its question, the answers it takes now and the next thing to do.
answer_setupSame as POST /api/v1/setup/answer: revision, answer. Answers the setup for the user; a yes on the summary confirms it.
add_setup_contextSame as POST /api/v1/setup/context: files, each with name, path and content. The user confirms what ZYNT read on the setup’s summary.
list_webhooksSame as GET /api/v1/webhooks, as { webhooks }.
create_webhookSame as POST /api/v1/webhooks: url, events, assignee.
delete_webhookSame as DELETE /api/v1/webhooks/:id: webhookId.
ping_webhookSame as POST /api/v1/webhooks/:id/ping: webhookId.
scan_webhookSame as POST /api/v1/webhooks/:id/scan: webhookId.

Try asking it:

  • “What are my highest scoring signals this week?”
  • “Summarize the signal about [company name] and who to contact.”
  • “Which new signals mention a funding round?”
  • “Find summit events in Warsaw and show their scores.”
  • “What is new at linkedin.com/company/[company]? Show its signals.”
  • “Who works at [company name], and who founded or invested in it?”
  • “Move the signal about [company name] to Contacted and assign it to me.”
  • “Send my digest at 8:00 and only for signals scoring 80 or more.”
  • “Add a task to call Anna on the [company name] signal and note what she said.”
  • “Send what you know about our company to my ZYNT setup.”
  • “Send the signals assigned to me to this Slack webhook: [URL].”

API reference

Each endpoint with an example call, its parameters and body fields, and an example response. All of them need the Authorization: Bearer <your key> header.

OpenAPI JSON

Signals

List signals

GET/api/v1/signals

Newest signals first unless sort says otherwise. app_url opens the signal in the ZYNT app; share it with your team. assignee_id, status, and a company’s website_url and linkedin_url can be null. Filters combine with AND. Blank search, company and person values are ignored. Keep the same filters on every page and skip ids you already have, because new signals can shift the pages.

Bash
curl --get "https://app.getzynt.com/api/v1/signals" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "search=funding" \
  --data-urlencode "sort=highest-score" \
  --data-urlencode "received_after=2026-09-01" \
  --data-urlencode "limit=25"
search
Case-insensitive match in the title, description, sector, AI summary, market and reasoning.
company
Case-insensitive company name, matched through the companies extracted from the signal. A name only mentioned in the text does not match.
person
Case-insensitive person name, matched through the people extracted from the signal. A person’s employer does not match them.
company_id
Only signals about this company, by its id from lookup, search or a signal: the same signals as its profile in the app.
person_id
Only signals about this person, by their id from lookup, search or a signal: the same signals as their profile in the app.
audience_id
Only signals about a member of this list, by its id from GET /api/v1/audiences: the companies of a company list, the people of a people list. An unknown id answers 404.
sort
newest, oldest, highest-score or lowest-score. Defaults to newest.
received_after
Only signals received at or after this ISO 8601 date or timestamp, e.g. 2026-09-01 or 2026-09-01T08:00:00Z. A date alone means 00:00 UTC.
received_before
Only signals received at or before this ISO 8601 date or timestamp. A date alone means 00:00 UTC, so it leaves that day out.
favorite
true returns only the signals your team starred; false, or leaving it out, returns all signals.
one_per_company
true keeps the best matching signal of each company: the highest score, then the newest. A signal counts for the company its source names most, the first of its companies; with audience_id of a company list, for the company on that list its source names most. On a people list, two people of one company count as that company. A signal that names no company stays. The other filters apply first, so with audience_id and received_after it answers “who on my list had a signal this week”. false, or leaving it out, keeps every signal.
cursor
The next_cursor of the previous page. Omit it on the first request.
limit
How many signals to return, from 1 to 100; 25 when you leave it out. To read more than a few, ask for 100: one page of 100 is one request instead of four, and fields keeps a big page small.
fields
Comma-separated fields to return. Omit it to get every field. Available: id, scenario_id, title, score, status, assignee_id, summary, source_url, image_url, app_url, received_at, companies, favorite.
JSON response
{
  "data": [
    {
      "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
      "scenario_id": "9a417d2e-6c3b-4f80-a195-7e2d4c6b8a01",
      "title": "Acme Robotics raises €18M to expand warehouse automation",
      "score": 97,
      "status": {
        "id": "3b7e2c9d-1a5f-4d68-b023-9c7e6a4f2d10",
        "name": "New",
        "type": "todo"
      },
      "assignee_id": null,
      "summary": "Acme Robotics announced a Series A round to grow its European operations.",
      "source_url": "https://news.example.com/acme-robotics-series-a",
      "image_url": "https://news.example.com/favicon.ico",
      "app_url": "https://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
      "received_at": "2026-09-01T08:14:00.000Z",
      "companies": [
        {
          "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
          "name": "Acme Robotics",
          "website_url": "https://acme-robotics.example",
          "linkedin_url": null,
          "description": "",
          "is_target": true
        }
      ],
      "favorite": false
    }
  ],
  "next_cursor": null
}

Get a signal

GET/api/v1/signals/{id}

One signal with every list field, plus its score breakdown, reasoning, sector and the people on it. A score breakdown item has no explanation when none is available.

Bash
curl "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d" \
  -H "Authorization: Bearer <your key>"
id
A signal id from your signal list.
fields
Comma-separated fields to return. Omit it to get every field. Available: id, scenario_id, title, score, status, assignee_id, summary, source_url, image_url, app_url, received_at, companies, favorite, score_breakdown, reasoning, sector, people.
JSON response
{
  "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
  "scenario_id": "9a417d2e-6c3b-4f80-a195-7e2d4c6b8a01",
  "title": "Acme Robotics raises €18M to expand warehouse automation",
  "score": 97,
  "status": {
    "id": "3b7e2c9d-1a5f-4d68-b023-9c7e6a4f2d10",
    "name": "New",
    "type": "todo"
  },
  "assignee_id": null,
  "summary": "Acme Robotics announced a Series A round to grow its European operations.",
  "source_url": "https://news.example.com/acme-robotics-series-a",
  "image_url": "https://news.example.com/favicon.ico",
  "app_url": "https://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
  "received_at": "2026-09-01T08:14:00.000Z",
  "companies": [
    {
      "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
      "name": "Acme Robotics",
      "website_url": "https://acme-robotics.example",
      "linkedin_url": null,
      "description": "",
      "is_target": true
    }
  ],
  "favorite": false,
  "score_breakdown": {
    "items": [
      {
        "key": "strategic_value",
        "label": "strategic",
        "icon": "trending-up",
        "explanation": "The expansion matches the workspace growth priorities.",
        "points": 28,
        "max_points": 30
      },
      {
        "key": "bonus_factors",
        "label": "bonus",
        "icon": "award",
        "points": 7,
        "max_points": 10
      }
    ],
    "recommendation": "Review the round and contact the expansion lead."
  },
  "reasoning": "The funding, region and operating focus make this a high-priority signal.",
  "sector": "Industrial automation",
  "people": [
    {
      "id": "2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816",
      "first_name": "Anna",
      "last_name": "Nowak",
      "title": "Head of Operations",
      "company_name": "Acme Robotics",
      "linkedin_url": "https://www.linkedin.com/in/anna-nowak",
      "is_target": true,
      "signal_role": "Leads the expansion"
    }
  ]
}

Move or assign a signal

PATCH/api/v1/signals/{id}

Sets the status, the assignee, or both, as the key’s user would in the app. A field you leave out stays as it is. Both are checked before either is saved, so an unknown status or assignee changes nothing: the answer is 400 with unknown_status and the allowed names, or with invalid_assignee. The assignee gets the same notification as in the app. Moving a signal to any status but a to-do one assigns it to the key’s user when their “Assign signals I move” setting is on and the signal has no assignee, or has one and their “Take over from the current owner” setting is on; an assignee you send wins. Returns the signal as GET /api/v1/signals/{id} does.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"status":"Contacted","assignee":"anna@acme-sales.example"}'
id
A signal id from your signal list.
status
A status name as your team sees it in ZYNT, matched without case and spaces at the ends, or a status id, which still works after a rename. /api/v1/statuses lists them.
assignee
The email or user id of a member of your organization, or null to unassign. /api/v1/members lists them.
JSON response
{
  "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
  "scenario_id": "9a417d2e-6c3b-4f80-a195-7e2d4c6b8a01",
  "title": "Acme Robotics raises €18M to expand warehouse automation",
  "score": 97,
  "status": {
    "id": "6d2a9f41-8c7e-4b35-a0d6-1f3e5b7c9a82",
    "name": "Contacted",
    "type": "in_progress"
  },
  "assignee_id": "user_2nX8kQvB4yLmR7tZ",
  "summary": "Acme Robotics announced a Series A round to grow its European operations.",
  "source_url": "https://news.example.com/acme-robotics-series-a",
  "image_url": "https://news.example.com/favicon.ico",
  "app_url": "https://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
  "received_at": "2026-09-01T08:14:00.000Z",
  "companies": [
    {
      "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
      "name": "Acme Robotics",
      "website_url": "https://acme-robotics.example",
      "linkedin_url": null,
      "description": "",
      "is_target": true
    }
  ],
  "favorite": false,
  "score_breakdown": {
    "items": [
      {
        "key": "strategic_value",
        "label": "strategic",
        "icon": "trending-up",
        "explanation": "The expansion matches the workspace growth priorities.",
        "points": 28,
        "max_points": 30
      },
      {
        "key": "bonus_factors",
        "label": "bonus",
        "icon": "award",
        "points": 7,
        "max_points": 10
      }
    ],
    "recommendation": "Review the round and contact the expansion lead."
  },
  "reasoning": "The funding, region and operating focus make this a high-priority signal.",
  "sector": "Industrial automation",
  "people": [
    {
      "id": "2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816",
      "first_name": "Anna",
      "last_name": "Nowak",
      "title": "Head of Operations",
      "company_name": "Acme Robotics",
      "linkedin_url": "https://www.linkedin.com/in/anna-nowak",
      "is_target": true,
      "signal_role": "Leads the expansion"
    }
  ]
}

Move or assign many signals

PATCH/api/v1/signals

The same change as PATCH /api/v1/signals/{id} on up to 100 signals at once. The status and assignee are checked once, before any signal changes, so an unknown one changes nothing. Then each signal changes on its own, as it would one by one. An id that does not exist or that the key’s user cannot see comes back in not_found and does not stop the rest.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/signals" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"ids":["0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d","5e8b2d14-7a9c-4f3e-b6d1-0c2a9f4e7b38"],"status":"Contacted","assignee":"anna@acme-sales.example"}'
ids
Signal ids from your signal list, 1 to 100.
status
A status name as your team sees it in ZYNT, matched without case and spaces at the ends, or a status id, which still works after a rename. /api/v1/statuses lists them.
assignee
The email or user id of a member of your organization, or null to unassign. /api/v1/members lists them.
JSON response
{
  "updated": [
    "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d"
  ],
  "not_found": [
    "5e8b2d14-7a9c-4f3e-b6d1-0c2a9f4e7b38"
  ]
}

Rate a signal

PUT/api/v1/signals/{id}/feedback

Sets the stars and comment, the same rating as the app’s feedback: the app shows 1 or 2 stars as less like this and 3 to 5 as more like this. A signal has one rating, so each call replaces the last one, whoever sent it, and the app shows it as the key’s user’s. Returns the rating as saved; stars and comment are null when not set, and less like this given in the app reads as 1 star.

Bash
curl -X PUT "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/feedback" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"stars":4,"comment":"Good fit, talking to them next week"}'
id
A signal id from your signal list.
stars
1 to 5, or null to clear the rating. 1 or 2 show in the app as less like this, 3 to 5 as more like this. Required.
comment
Up to 1000 characters. Omit it, or send null or an empty text, for no comment; a rating sent without one clears the old comment.
auto_assign
Whether rating an unassigned signal assigns it to the key’s user. A signal someone has stays theirs unless the user’s “Take over from the current owner” setting is on, and clearing a rating assigns nothing. Omit it to follow their “Assign signals I want more of” setting in the app, which assigns on 3 stars or more.
JSON response
{
  "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
  "stars": 4,
  "comment": "Good fit, talking to them next week"
}

Mark a signal as favorite

PUT/api/v1/signals/{id}/favorite

Stars the signal, as the star in the app. The star is shared, so the whole team sees it. Starring it again changes nothing. Market signals have no star and answer 404. GET /api/v1/signals?favorite=true lists the favorites; every signal carries favorite.

Bash
curl -X PUT "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/favorite" \
  -H "Authorization: Bearer <your key>"
id
A signal id from your signal list.
JSON response
{
  "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
  "favorite": true
}

Take a signal off the favorites

DELETE/api/v1/signals/{id}/favorite

Takes the star off for the whole team. A signal that is not a favorite answers the same.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/favorite" \
  -H "Authorization: Bearer <your key>"
id
A signal id from your signal list.
JSON response
{
  "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
  "favorite": false
}

List statuses

GET/api/v1/statuses

Every status of your organization, in the order the app shows them: todo first, then in_progress, then done. type is one of todo, in_progress or done; color is a hex color such as #3b82f6. No paging.

Bash
curl "https://app.getzynt.com/api/v1/statuses" \
  -H "Authorization: Bearer <your key>"
JSON response
[
  {
    "id": "3b7e2c9d-1a5f-4d68-b023-9c7e6a4f2d10",
    "name": "New",
    "type": "todo",
    "color": "#3b82f6"
  },
  {
    "id": "6d2a9f41-8c7e-4b35-a0d6-1f3e5b7c9a82",
    "name": "Contacted",
    "type": "in_progress",
    "color": "#f59e0b"
  },
  {
    "id": "c4e81b6f-2d9a-4f73-8e05-7a1b3d5f9c26",
    "name": "Won",
    "type": "done",
    "color": "#22c55e"
  }
]

Add a status

POST/api/v1/statuses

Adds a status for the whole team at the end of its type, as Settings → Statuses does. Only an admin of your organization can; anyone else gets 403 forbidden. A name another status has, compared without case, is 422 invalid_request. Returns the new status.

Bash
curl -X POST "https://app.getzynt.com/api/v1/statuses" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"name":"Meeting booked","type":"in_progress","color":"#8b5cf6"}'
name
Up to 100 characters. Required.
type
todo, in_progress or done. It decides where the status sits and how the app treats its signals, and cannot change later. Required.
color
A hex color as #RRGGBB. Defaults to #3b82f6.
JSON response
{
  "id": "1f7b3d95-4e2a-4c68-9a0b-5d3e7f1c2b84",
  "name": "Meeting booked",
  "type": "in_progress",
  "color": "#8b5cf6"
}

Rename or recolor a status

PATCH/api/v1/statuses/{id}

Changes the name, the color, or both. A field you leave out stays as it is; the type cannot change. Signals in the status keep it, and a status id sent to PATCH /api/v1/signals/{id} still works after a rename. Only an admin of your organization can. Returns the status as saved.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/statuses/6d2a9f41-8c7e-4b35-a0d6-1f3e5b7c9a82" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"name":"Reached out"}'
id
A status id from /api/v1/statuses, or its current name.
name
Up to 100 characters, not the name of another status.
color
A hex color as #RRGGBB.
JSON response
{
  "id": "6d2a9f41-8c7e-4b35-a0d6-1f3e5b7c9a82",
  "name": "Reached out",
  "type": "in_progress",
  "color": "#f59e0b"
}

Delete a status

DELETE/api/v1/statuses/{id}

Deletes the status for the whole team. When signals are in it, or it is the status new signals get, send move_to: they move there first. Without move_to such a status answers 409 status_in_use and nothing changes. The last status of a type cannot go: 409 last_status_of_type. An unknown move_to is 400 unknown_status with the allowed names. Only an admin of your organization can. Returns the status that was deleted.

Bash
curl --get -X DELETE "https://app.getzynt.com/api/v1/statuses/6d2a9f41-8c7e-4b35-a0d6-1f3e5b7c9a82" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "move_to=New"
id
A status id from /api/v1/statuses, or its current name.
move_to
The name or id of the status that takes the deleted one’s signals and, when it was the status new signals get, its place.
JSON response
{
  "id": "6d2a9f41-8c7e-4b35-a0d6-1f3e5b7c9a82",
  "name": "Contacted",
  "type": "in_progress",
  "color": "#f59e0b"
}

Tasks

List a signal’s tasks

GET/api/v1/signals/{id}/tasks

The signal’s tasks in the order the app shows them, with done true for a ticked one. A task’s id comes from its text: it stays the same when other tasks are added or removed, and changes when the text changes. Tasks with the same text share an id; a change goes to the first of them it alters, so ticking takes an unticked one. No paging.

Bash
curl "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/tasks" \
  -H "Authorization: Bearer <your key>"
id
A signal id from your signal list.
JSON response
[
  {
    "id": "ta2ee81fcd32b344e",
    "text": "Call Anna Nowak about the warehouse rollout",
    "done": false
  },
  {
    "id": "t8273671229fe0894",
    "text": "Send the case study on Gdańsk logistics",
    "done": true
  }
]

Add a task to a signal

POST/api/v1/signals/{id}/tasks

Adds a task at the top of the signal’s list, where the app puts the ones a rep adds. Works on market signals too. Returns the new task.

Bash
curl -X POST "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/tasks" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"text":"Call Anna Nowak about the warehouse rollout"}'
id
A signal id from your signal list.
text
1 to 500 characters. Required.
JSON response
{
  "id": "ta2ee81fcd32b344e",
  "text": "Call Anna Nowak about the warehouse rollout",
  "done": false
}

Tick or reword a task

PATCH/api/v1/signals/{id}/tasks/{task_id}

Ticks or unticks the task, rewords it, or both; send at least one field. A new text gives the task a new id, which the answer holds. An id no task has, also an old one after a rewording, answers 404.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/tasks/ta2ee81fcd32b344e" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"done":true}'
id
A signal id from your signal list.
task_id
A task id from GET /api/v1/signals/{id}/tasks.
done
true ticks the task, false unticks it.
text
The new text, 1 to 500 characters.
JSON response
{
  "id": "ta2ee81fcd32b344e",
  "text": "Call Anna Nowak about the warehouse rollout",
  "done": true
}

Delete a task

DELETE/api/v1/signals/{id}/tasks/{task_id}

Removes the task from the signal. The other tasks keep their ids. Returns the id with deleted true.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/tasks/ta2ee81fcd32b344e" \
  -H "Authorization: Bearer <your key>"
id
A signal id from your signal list.
task_id
A task id from GET /api/v1/signals/{id}/tasks.

Notes

List a signal’s notes

GET/api/v1/signals/{id}/notes

The notes on the signal that the key’s user can see, newest first: their own, private ones included, and the ones teammates shared. own is true for the user’s own; public is false for a private one, so check it before you post a note where the team can read it. No paging.

Bash
curl "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/notes" \
  -H "Authorization: Bearer <your key>"
id
A signal id from /api/v1/signals.
JSON response
[
  {
    "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
    "content": "Anna wants a demo after their Q4 board meeting.",
    "public": true,
    "own": true,
    "author_name": "Ada Lovelace",
    "created_at": "2026-11-09T10:12:00.000Z",
    "updated_at": "2026-11-09T10:12:00.000Z"
  }
]

Add a note to a signal

POST/api/v1/signals/{id}/notes

Adds a note by the key’s user to the signal. It is private unless public is true, as in the app. Returns the new note.

Bash
curl -X POST "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/notes" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"content":"Anna wants a demo after their Q4 board meeting.","public":true}'
id
A signal id from /api/v1/signals.
content
The text, 1 to 5000 characters. Required.
public
true shares the note with the team, false keeps it to its author. Defaults to false.
JSON response
{
  "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
  "content": "Anna wants a demo after their Q4 board meeting.",
  "public": true
}

Edit or share a signal note

PATCH/api/v1/signals/{id}/notes/{note_id}

Changes the text, shares the note or makes it private again; send at least one field. Only the note’s author can: anyone else’s note answers 404. Returns the note as saved.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/notes/4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"public":false}'
id
A signal id from /api/v1/signals.
note_id
The id of a note of yours, one with own true.
content
The text, 1 to 5000 characters.
public
true shares the note with the team, false keeps it to its author.
JSON response
{
  "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
  "content": "Anna wants a demo after their Q4 board meeting.",
  "public": false
}

Delete a signal note

DELETE/api/v1/signals/{id}/notes/{note_id}

Removes the note for everyone. Only its author can: anyone else’s note answers 404. Returns the id with deleted true.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/signals/0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d/notes/4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74" \
  -H "Authorization: Bearer <your key>"
id
A signal id from /api/v1/signals.
note_id
The id of a note of yours, one with own true.

List a company’s notes

GET/api/v1/companies/{id}/notes

The notes on the company that the key’s user can see, newest first: their own, private ones included, and the ones teammates shared. own is true for the user’s own; public is false for a private one, so check it before you post a note where the team can read it. No paging.

Bash
curl "https://app.getzynt.com/api/v1/companies/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49/notes" \
  -H "Authorization: Bearer <your key>"
id
A company id from a signal, /api/v1/companies/lookup or /search.
JSON response
[
  {
    "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
    "content": "Anna wants a demo after their Q4 board meeting.",
    "public": true,
    "own": true,
    "author_name": "Ada Lovelace",
    "created_at": "2026-11-09T10:12:00.000Z",
    "updated_at": "2026-11-09T10:12:00.000Z"
  }
]

Add a note to a company

POST/api/v1/companies/{id}/notes

Adds a note by the key’s user to the company. It is private unless public is true, as in the app. Returns the new note.

Bash
curl -X POST "https://app.getzynt.com/api/v1/companies/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49/notes" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"content":"Anna wants a demo after their Q4 board meeting.","public":true}'
id
A company id from a signal, /api/v1/companies/lookup or /search.
content
The text, 1 to 5000 characters. Required.
public
true shares the note with the team, false keeps it to its author. Defaults to false.
JSON response
{
  "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
  "content": "Anna wants a demo after their Q4 board meeting.",
  "public": true
}

Edit or share a company note

PATCH/api/v1/companies/{id}/notes/{note_id}

Changes the text, shares the note or makes it private again; send at least one field. Only the note’s author can: anyone else’s note answers 404. Returns the note as saved.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/companies/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49/notes/4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"public":false}'
id
A company id from a signal, /api/v1/companies/lookup or /search.
note_id
The id of a note of yours, one with own true.
content
The text, 1 to 5000 characters.
public
true shares the note with the team, false keeps it to its author.
JSON response
{
  "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
  "content": "Anna wants a demo after their Q4 board meeting.",
  "public": false
}

Delete a company note

DELETE/api/v1/companies/{id}/notes/{note_id}

Removes the note for everyone. Only its author can: anyone else’s note answers 404. Returns the id with deleted true.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/companies/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49/notes/4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74" \
  -H "Authorization: Bearer <your key>"
id
A company id from a signal, /api/v1/companies/lookup or /search.
note_id
The id of a note of yours, one with own true.

List a person’s notes

GET/api/v1/people/{id}/notes

The notes on the person that the key’s user can see, newest first: their own, private ones included, and the ones teammates shared. own is true for the user’s own; public is false for a private one, so check it before you post a note where the team can read it. No paging.

Bash
curl "https://app.getzynt.com/api/v1/people/2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816/notes" \
  -H "Authorization: Bearer <your key>"
id
A person id from a signal, /api/v1/people/lookup or /search.
JSON response
[
  {
    "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
    "content": "Anna wants a demo after their Q4 board meeting.",
    "public": true,
    "own": true,
    "author_name": "Ada Lovelace",
    "created_at": "2026-11-09T10:12:00.000Z",
    "updated_at": "2026-11-09T10:12:00.000Z"
  }
]

Add a note to a person

POST/api/v1/people/{id}/notes

Adds a note by the key’s user to the person. It is private unless public is true, as in the app. Returns the new note.

Bash
curl -X POST "https://app.getzynt.com/api/v1/people/2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816/notes" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"content":"Anna wants a demo after their Q4 board meeting.","public":true}'
id
A person id from a signal, /api/v1/people/lookup or /search.
content
The text, 1 to 5000 characters. Required.
public
true shares the note with the team, false keeps it to its author. Defaults to false.
JSON response
{
  "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
  "content": "Anna wants a demo after their Q4 board meeting.",
  "public": true
}

Edit or share a person note

PATCH/api/v1/people/{id}/notes/{note_id}

Changes the text, shares the note or makes it private again; send at least one field. Only the note’s author can: anyone else’s note answers 404. Returns the note as saved.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/people/2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816/notes/4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"public":false}'
id
A person id from a signal, /api/v1/people/lookup or /search.
note_id
The id of a note of yours, one with own true.
content
The text, 1 to 5000 characters.
public
true shares the note with the team, false keeps it to its author.
JSON response
{
  "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
  "content": "Anna wants a demo after their Q4 board meeting.",
  "public": false
}

Delete a person note

DELETE/api/v1/people/{id}/notes/{note_id}

Removes the note for everyone. Only its author can: anyone else’s note answers 404. Returns the id with deleted true.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/people/2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816/notes/4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74" \
  -H "Authorization: Bearer <your key>"
id
A person id from a signal, /api/v1/people/lookup or /search.
note_id
The id of a note of yours, one with own true.

List a event’s notes

GET/api/v1/events/{id}/notes

The notes on the event that the key’s user can see, newest first: their own, private ones included, and the ones teammates shared. own is true for the user’s own; public is false for a private one, so check it before you post a note where the team can read it. No paging.

Bash
curl "https://app.getzynt.com/api/v1/events/7c13.../notes" \
  -H "Authorization: Bearer <your key>"
id
A event id from /api/v1/events.
JSON response
[
  {
    "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
    "content": "Anna wants a demo after their Q4 board meeting.",
    "public": true,
    "own": true,
    "author_name": "Ada Lovelace",
    "created_at": "2026-11-09T10:12:00.000Z",
    "updated_at": "2026-11-09T10:12:00.000Z"
  }
]

Add a note to a event

POST/api/v1/events/{id}/notes

Adds a note by the key’s user to the event. It is private unless public is true, as in the app. Returns the new note.

Bash
curl -X POST "https://app.getzynt.com/api/v1/events/7c13.../notes" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"content":"Anna wants a demo after their Q4 board meeting.","public":true}'
id
A event id from /api/v1/events.
content
The text, 1 to 5000 characters. Required.
public
true shares the note with the team, false keeps it to its author. Defaults to false.
JSON response
{
  "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
  "content": "Anna wants a demo after their Q4 board meeting.",
  "public": true
}

Edit or share a event note

PATCH/api/v1/events/{id}/notes/{note_id}

Changes the text, shares the note or makes it private again; send at least one field. Only the note’s author can: anyone else’s note answers 404. Returns the note as saved.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/events/7c13.../notes/4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"public":false}'
id
A event id from /api/v1/events.
note_id
The id of a note of yours, one with own true.
content
The text, 1 to 5000 characters.
public
true shares the note with the team, false keeps it to its author.
JSON response
{
  "id": "4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74",
  "content": "Anna wants a demo after their Q4 board meeting.",
  "public": false
}

Delete a event note

DELETE/api/v1/events/{id}/notes/{note_id}

Removes the note for everyone. Only its author can: anyone else’s note answers 404. Returns the id with deleted true.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/events/7c13.../notes/4f1c8e2a-7b3d-4a69-9e05-2d6b8c1f3a74" \
  -H "Authorization: Bearer <your key>"
id
A event id from /api/v1/events.
note_id
The id of a note of yours, one with own true.

Audiences

List audiences

GET/api/v1/audiences

Your team’s lists of companies and people. subject_type is company or person and says which records a list holds; from_crm_list is true for a list imported from your CRM. The Excluded list is not here: /api/v1/exclusions holds it. No paging.

Bash
curl "https://app.getzynt.com/api/v1/audiences" \
  -H "Authorization: Bearer <your key>"
JSON response
[
  {
    "id": "8b2e4c61-3f9a-4d07-a5c1-6e8d2b4f0a93",
    "name": "Logistics prospects",
    "subject_type": "company",
    "member_count": 42,
    "from_crm_list": false
  }
]

Make an audience

POST/api/v1/audiences

Makes an empty list for the team. Only an organization admin can. A team has at most 5 lists of its own; CRM lists do not count, and a sixth answers 409 audience_limit_reached.

Bash
curl -X POST "https://app.getzynt.com/api/v1/audiences" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"name":"Trade fair leads","subject_type":"company"}'
name
The list’s name.
subject_type
company or person: what the list holds.
JSON response
{
  "id": "6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63",
  "name": "Trade fair leads",
  "subject_type": "company",
  "member_count": 0,
  "from_crm_list": false
}

Rename an audience

PATCH/api/v1/audiences/{id}

Renames the list for the whole team. Only an organization admin can.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/audiences/6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"name":"Trade fair leads 2027"}'
id
An audience id from /api/v1/audiences.
name
The new name.
JSON response
{
  "id": "6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63",
  "name": "Trade fair leads 2027",
  "subject_type": "company",
  "member_count": 0,
  "from_crm_list": false
}

Delete an audience

DELETE/api/v1/audiences/{id}

Deletes the list for the whole team; it cannot be undone. Its companies and people stay in ZYNT. Only an organization admin can. An agent must ask the user and get a clear yes before every deletion, even when told to work without asking.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/audiences/6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63" \
  -H "Authorization: Bearer <your key>"
id
An audience id from /api/v1/audiences.
JSON response
{
  "id": "6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63",
  "deleted": true
}

Get a list’s timeline

GET/api/v1/audiences/{id}/timeline

The newest news, articles, LinkedIn posts, comments, reactions, job posts and signals about every company or person on the list, newest first; member says which one each item is about. Use it for “any news about my list?”: a source shows as soon as ZYNT finds it, while a signal comes later, after scoring, so a list added today can have items and no signals. occurred_at is when ZYNT found the source. One URL comes once for each member, and a source about two members comes for each. A company merged into one on the list counts as that company. signal holds your organization’s highest-scored signal from the source that is not archived, with app_url, its link in the ZYNT app, or null; source.platform and signal.scenario can be null. An unknown id, or another team’s list, returns 404 not_found.

Bash
curl --get "https://app.getzynt.com/api/v1/audiences/6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63/timeline" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "period=7"
id
An audience id from /api/v1/audiences.
period
Only items ZYNT found in the last 7, 30, 90 or 365 days, or all. Defaults to 7. With nothing in 7 days, ask for 30, then 90.
cursor
The next_cursor of the previous page. Omit it on the first request.
limit
How many items to return, from 1 to 100; 25 when you leave it out. To read more than a few, ask for 100: one page of 100 is one request instead of four.
JSON response
{
  "data": [
    {
      "id": "5b8e2f14-7a3c-4d91-b6e0-2c4f8a1d9e73:7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
      "member": {
        "type": "company",
        "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
        "name": "Acme Robotics"
      },
      "kind": "news",
      "title": "Acme Robotics opens a second plant in Gdańsk",
      "occurred_at": "2026-09-24T08:30:00.000Z",
      "source": {
        "label": "example.com",
        "platform": null,
        "url": "https://example.com/news/acme-gdansk-plant"
      },
      "signal": {
        "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
        "score": 82,
        "scenario": "Manufacturing expansion",
        "app_url": "https://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d"
      }
    }
  ],
  "next_cursor": null
}

Add a company or person to an audience

PUT/api/v1/audiences/{id}/members/{record_id}

Adds a company or person ZYNT already knows to the audience, as the app does; ZYNT makes no new record. Adding one the audience holds changes nothing. A record of the other kind, or one ZYNT does not know, answers 404. A list imported from your CRM (from_crm_list true) takes its members from the CRM again at its next import, so a record you add there can leave it. Any member of the team can.

Bash
curl -X PUT "https://app.getzynt.com/api/v1/audiences/8b2e4c61-3f9a-4d07-a5c1-6e8d2b4f0a93/members/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49" \
  -H "Authorization: Bearer <your key>"
id
An audience id from /api/v1/audiences.
record_id
A company or person id, from a signal, a lookup or a search, of the kind the audience holds.
JSON response
{
  "audience_id": "8b2e4c61-3f9a-4d07-a5c1-6e8d2b4f0a93",
  "record_id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
  "included": true
}

Remove a company or person from an audience

DELETE/api/v1/audiences/{id}/members/{record_id}

Takes the record off the audience. A record the audience does not hold answers the same, with included false; an id ZYNT does not know answers 404.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/audiences/8b2e4c61-3f9a-4d07-a5c1-6e8d2b4f0a93/members/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49" \
  -H "Authorization: Bearer <your key>"
id
An audience id from /api/v1/audiences.
record_id
A company or person id, from a signal, a lookup or a search, of the kind the audience holds.
JSON response
{
  "audience_id": "8b2e4c61-3f9a-4d07-a5c1-6e8d2b4f0a93",
  "record_id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
  "included": false
}

Excluded companies

List excluded companies

GET/api/v1/exclusions

The companies your team excluded, by name, as Settings → Exclusions lists them. Nobody on the team gets signals about them. Companies the business setup names are not in this list. No paging.

Bash
curl "https://app.getzynt.com/api/v1/exclusions" \
  -H "Authorization: Bearer <your key>"
JSON response
[
  {
    "company_id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
    "name": "Acme Robotics"
  }
]

Exclude a company

PUT/api/v1/exclusions/{company_id}

Puts the company on your team’s Excluded list, as Exclude on a signal does. Its signals are hidden for everyone at once, and the next research skips it. Excluding a company already on the list changes nothing. Any member of the team can. An unknown id is 404 not_found.

Bash
curl -X PUT "https://app.getzynt.com/api/v1/exclusions/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49" \
  -H "Authorization: Bearer <your key>"
company_id
A company id from a signal, /api/v1/companies/lookup or /api/v1/companies/search.
JSON response
{
  "company_id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
  "name": "Acme Robotics",
  "excluded": true
}

Include a company again

DELETE/api/v1/exclusions/{company_id}

Takes the company off the Excluded list, as Include in Settings → Exclusions does, and its signals show again. A company that is not on the list answers the same, with excluded false.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/exclusions/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49" \
  -H "Authorization: Bearer <your key>"
company_id
The company id from /api/v1/exclusions.
JSON response
{
  "company_id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
  "name": "Acme Robotics",
  "excluded": false
}

Team

List team members

GET/api/v1/members

The members of your organization, as the app’s member pickers list them. Send an email or id from here as assignee to PATCH /api/v1/signals/{id}. name is null for a member who has not set one. No paging.

Bash
curl "https://app.getzynt.com/api/v1/members" \
  -H "Authorization: Bearer <your key>"
JSON response
[
  {
    "id": "user_2nX8kQvB4yLmR7tZ",
    "name": "Anna Kowalska",
    "email": "anna@acme-sales.example"
  },
  {
    "id": "user_2pR4mWcT9hJsK1vD",
    "name": null,
    "email": "tom@acme-sales.example"
  }
]

Change a member’s role

PATCH/api/v1/members/{user_id}

Makes a teammate a manager or a member, as Settings → Team does. Only a manager can, and not for themselves.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/members/user_2nX8kQvB4yLmR7tZ" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"role":"manager"}'
user_id
A user id from /api/v1/members.
role
manager changes the team, statuses and settings for everyone; member works with signals.
JSON response
{
  "id": "user_2nX8kQvB4yLmR7tZ",
  "email": "anna@acme-sales.example",
  "role": "manager"
}

Remove a member

DELETE/api/v1/members/{user_id}

Takes the person off the team: they lose access at once, and their signals, tasks and notes stay. Only a manager can, and not themselves or ZYNT support. An agent must ask the user and get a clear yes first.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/members/user_2nX8kQvB4yLmR7tZ" \
  -H "Authorization: Bearer <your key>"
user_id
A user id from /api/v1/members.
JSON response
{
  "id": "user_2nX8kQvB4yLmR7tZ",
  "deleted": true
}

List open invitations

GET/api/v1/invitations

Invitations nobody has accepted yet. Only a manager can read them. No paging.

Bash
curl "https://app.getzynt.com/api/v1/invitations" \
  -H "Authorization: Bearer <your key>"
JSON response
[
  {
    "id": "orginv_2pT7xQwK9mLzR4bN",
    "email": "ola@acme-sales.example",
    "role": "member",
    "created_at": "2026-11-10T09:30:00.000Z"
  }
]

Invite someone to the team

POST/api/v1/invitations

Emails an invitation, as Settings → Team does. Only a manager can. Invitations count toward the people your plan allows: past it, 409 user_limit_reached; someone already on the team or invited, 409 already_member. A team sends at most 20 invitations an hour; past that, 429 rate_limited.

Bash
curl -X POST "https://app.getzynt.com/api/v1/invitations" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"email":"ola@acme-sales.example","role":"member"}'
email
The address to invite.
role
manager or member.
JSON response
{
  "id": "orginv_2pT7xQwK9mLzR4bN",
  "email": "ola@acme-sales.example",
  "role": "member",
  "created_at": "2026-11-10T09:30:00.000Z"
}

Revoke an invitation

DELETE/api/v1/invitations/{id}

Takes back an invitation nobody has accepted, so its link stops working. Only a manager can.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/invitations/orginv_2pT7xQwK9mLzR4bN" \
  -H "Authorization: Bearer <your key>"
id
An invitation id from /api/v1/invitations.
JSON response
{
  "id": "orginv_2pT7xQwK9mLzR4bN",
  "deleted": true
}

Writing skills

List writing skills

GET/api/v1/writing-skills

The briefs ZYNT follows when it writes an outreach message, the team’s and the key’s user’s own, as Settings → Writing skills shows them. is_default marks the team’s default; can_edit says whether the key’s user may change one. No paging.

Bash
curl "https://app.getzynt.com/api/v1/writing-skills" \
  -H "Authorization: Bearer <your key>"
JSON response
[
  {
    "id": "2c7e9b14-5a3d-4f81-b0c6-8e1f4d2a9b57",
    "name": "Short and warm",
    "body": "- Three sentences at most.\n- Open with the news from the signal.\n- End with one question, no meeting link.",
    "visibility": "team",
    "is_default": false,
    "can_edit": true,
    "is_own": true
  }
]

Add a writing skill

POST/api/v1/writing-skills

Adds a skill for the key’s user, or for the team with visibility team. A workspace keeps up to 50; past that, 409 writing_skill_limit_reached.

Bash
curl -X POST "https://app.getzynt.com/api/v1/writing-skills" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"name":"Short and warm","body":"- Three sentences at most.\n- Open with the news from the signal.\n- End with one question, no meeting link.","visibility":"team"}'
name
Up to 60 characters.
body
How ZYNT should write, in Markdown, up to 8000 characters: tone, structure, what to mention and avoid.
visibility
me keeps it to the key’s user; team shares it.
JSON response
{
  "id": "2c7e9b14-5a3d-4f81-b0c6-8e1f4d2a9b57",
  "name": "Short and warm",
  "body": "- Three sentences at most.\n- Open with the news from the signal.\n- End with one question, no meeting link.",
  "visibility": "team",
  "is_default": false,
  "can_edit": true,
  "is_own": true
}

Change a writing skill

PATCH/api/v1/writing-skills/{id}

Changes the fields you send. The key’s user changes their own skills, and an admin the team’s too; only the author changes visibility.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/writing-skills/2c7e9b14-5a3d-4f81-b0c6-8e1f4d2a9b57" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"name":"Short, warm, Polish"}'
id
A writing skill id.
name
Up to 60 characters.
body
How ZYNT should write, in Markdown, up to 8000 characters: tone, structure, what to mention and avoid.
visibility
me keeps it to the key’s user; team shares it.
JSON response
{
  "id": "2c7e9b14-5a3d-4f81-b0c6-8e1f4d2a9b57",
  "name": "Short, warm, Polish",
  "body": "- Three sentences at most.\n- Open with the news from the signal.\n- End with one question, no meeting link.",
  "visibility": "team",
  "is_default": false,
  "can_edit": true,
  "is_own": true
}

Delete a writing skill

DELETE/api/v1/writing-skills/{id}

Deletes the skill for good. When it was the default, ZYNT writes its own way until someone picks another.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/writing-skills/2c7e9b14-5a3d-4f81-b0c6-8e1f4d2a9b57" \
  -H "Authorization: Bearer <your key>"
id
A writing skill id.
JSON response
{
  "id": "2c7e9b14-5a3d-4f81-b0c6-8e1f4d2a9b57",
  "deleted": true
}

Pick the team’s default writing skill

PUT/api/v1/writing-skills/default

The team skill ZYNT follows for anyone who picked no other, or null for ZYNT’s own way. Only an organization admin can. Answers with every skill.

Bash
curl -X PUT "https://app.getzynt.com/api/v1/writing-skills/default" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"id":"2c7e9b14-5a3d-4f81-b0c6-8e1f4d2a9b57"}'
id
A team skill id, or null.
JSON response
[
  {
    "id": "2c7e9b14-5a3d-4f81-b0c6-8e1f4d2a9b57",
    "name": "Short and warm",
    "body": "- Three sentences at most.\n- Open with the news from the signal.\n- End with one question, no meeting link.",
    "visibility": "team",
    "is_default": true,
    "can_edit": true,
    "is_own": true
  }
]

API keys

List your API keys

GET/api/v1/api-keys

The key’s user’s working keys, as Settings → API lists them, without their secrets. No paging.

Bash
curl "https://app.getzynt.com/api/v1/api-keys" \
  -H "Authorization: Bearer <your key>"
JSON response
[
  {
    "id": "ak_2qH8vNcR5tYwK3mP",
    "name": "Slack signal bot",
    "created_at": "2026-11-10T09:30:00.000Z",
    "last_used_at": null
  }
]

Make an API key

POST/api/v1/api-keys

A new key with the key’s user’s access. It ends after expires_in_days, never after the key that makes it; a key that never ends is made in Settings → API. A user keeps at most 20 working keys. secret is the key itself and ZYNT never shows it again, so store it at once.

Bash
curl -X POST "https://app.getzynt.com/api/v1/api-keys" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"name":"Slack signal bot","expires_in_days":30}'
name
Where the key is used, up to 100 characters.
expires_in_days
Required. 1 to 90 days, and no longer than the key that sends the request has left.
JSON response
{
  "id": "ak_2qH8vNcR5tYwK3mP",
  "name": "Slack signal bot",
  "created_at": "2026-11-10T09:30:00.000Z",
  "last_used_at": null,
  "secret": "ak_live_example_shown_once"
}

Revoke an API key

DELETE/api/v1/api-keys/{id}

Turns one of the key’s user’s keys off for good; every tool using it stops at once. An agent must ask the user first.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/api-keys/ak_2qH8vNcR5tYwK3mP" \
  -H "Authorization: Bearer <your key>"
id
A key id from /api/v1/api-keys.
JSON response
{
  "id": "ak_2qH8vNcR5tYwK3mP",
  "deleted": true
}

Your settings

Get your preferences

GET/api/v1/me/preferences

The key’s user’s own settings from Settings → Signal ownership and Settings → Preferences: when signals become theirs, and the instructions ZYNT follows in every outreach message it writes for them.

Bash
curl "https://app.getzynt.com/api/v1/me/preferences" \
  -H "Authorization: Bearer <your key>"
JSON response
{
  "assign_on_rating": true,
  "assign_on_status_change": false,
  "assign_override": false,
  "assign_crm_clients": true,
  "outreach_instructions": "Write casually and use first names. No emojis. Sign off as Ada from Acme."
}

Change your preferences

PATCH/api/v1/me/preferences

Changes the fields you send for the key’s user only; the rest stay as they are, and nobody else’s change. Returns every preference as saved.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/me/preferences" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"assign_on_status_change":true}'
assign_on_rating
Assign signals I want more of: rating a signal nobody owns 3 stars or more makes it the user’s.
assign_on_status_change
Assign signals I move: moving a signal nobody owns past to-do makes it the user’s.
assign_override
Take over from the current owner: with either of the two above, rating or moving a signal takes it from whoever owns it.
assign_crm_clients
Assign signals about my clients and deals: new signals about companies and contacts the user owns in the connected CRM, clients or in a deal, are theirs.
outreach_instructions
Up to 2000 characters ZYNT follows in every outreach message it writes for the user: tone, what to mention, what to avoid, how to sign off. An empty text clears them.
JSON response
{
  "assign_on_rating": true,
  "assign_on_status_change": true,
  "assign_override": false,
  "assign_crm_clients": true,
  "outreach_instructions": "Write casually and use first names. No emojis. Sign off as Ada from Acme."
}

Get your notification settings

GET/api/v1/me/notifications

The key’s user’s settings from Settings → Notifications. rules has one rule per type: new_signal, assigned_signal, signal_status, event_status, new_event, watched_event and event_scoring_failed. A rule says whether the notification shows in the inbox (in_app), sends an email at once (email) or goes to the digest (digest), and, for new_signal only, the lowest score a signal needs (minimum_score). scenarios lists the scenarios the user can see and set apart, each with its own rules; it is empty when there are none.

Bash
curl "https://app.getzynt.com/api/v1/me/notifications" \
  -H "Authorization: Bearer <your key>"
JSON response
{
  "email_opt_out": false,
  "digest_enabled": true,
  "digest_frequency": "daily",
  "digest_include_weekends": false,
  "digest_time": "09:00",
  "time_zone": "Europe/Warsaw",
  "rules": {
    "new_signal": {
      "in_app": false,
      "email": false,
      "digest": true,
      "minimum_score": 70
    },
    "assigned_signal": {
      "in_app": true,
      "email": false,
      "digest": false,
      "minimum_score": 0
    },
    "signal_status": {
      "in_app": true,
      "email": false,
      "digest": false,
      "minimum_score": 0
    },
    "event_status": {
      "in_app": true,
      "email": false,
      "digest": false,
      "minimum_score": 0
    },
    "new_event": {
      "in_app": false,
      "email": false,
      "digest": false,
      "minimum_score": 0
    },
    "watched_event": {
      "in_app": false,
      "email": false,
      "digest": false,
      "minimum_score": 0
    },
    "event_scoring_failed": {
      "in_app": true,
      "email": false,
      "digest": false,
      "minimum_score": 0
    }
  },
  "scenarios": []
}

Change your notification settings

PATCH/api/v1/me/notifications

Changes the fields you send for the key’s user only; the rest stay as they are. In rules, send only the types and fields you change. Scenario overrides cannot be changed here and stay as they are. Returns every setting as saved.

Bash
curl -X PATCH "https://app.getzynt.com/api/v1/me/notifications" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"digest_time":"08:30","rules":{"new_signal":{"minimum_score":80}}}'
email_opt_out
true stops every email from ZYNT, whatever the rules say.
digest_enabled
Send the digest email.
digest_frequency
daily or weekly.
digest_include_weekends
Send the daily digest on Saturday and Sunday too.
digest_time
When the digest goes out, as HH:MM in time_zone.
time_zone
An IANA time zone, for example Europe/Warsaw.
rules
Rules by type (new_signal, assigned_signal, signal_status, event_status, new_event, watched_event, event_scoring_failed), each with in_app, email, digest and minimum_score from 0 to 100, which only new_signal uses.
JSON response
{
  "email_opt_out": false,
  "digest_enabled": true,
  "digest_frequency": "daily",
  "digest_include_weekends": false,
  "digest_time": "08:30",
  "time_zone": "Europe/Warsaw",
  "rules": {
    "new_signal": {
      "in_app": false,
      "email": false,
      "digest": true,
      "minimum_score": 80
    },
    "assigned_signal": {
      "in_app": true,
      "email": false,
      "digest": false,
      "minimum_score": 0
    },
    "signal_status": {
      "in_app": true,
      "email": false,
      "digest": false,
      "minimum_score": 0
    },
    "event_status": {
      "in_app": true,
      "email": false,
      "digest": false,
      "minimum_score": 0
    },
    "new_event": {
      "in_app": false,
      "email": false,
      "digest": false,
      "minimum_score": 0
    },
    "watched_event": {
      "in_app": false,
      "email": false,
      "digest": false,
      "minimum_score": 0
    },
    "event_scoring_failed": {
      "in_app": true,
      "email": false,
      "digest": false,
      "minimum_score": 0
    }
  },
  "scenarios": []
}

Webhooks

Add a webhook

POST/api/v1/webhooks

ZYNT posts an event to your https URL within a few minutes. signal.created: a new signal the key’s user can see shows in ZYNT and names a company or person on your watchlist (the default lists of companies and people in Audiences); other signals are not sent. A signal shows once ZYNT has prepared it, which can be a while after it was found, and created_at says when it was found. signal.assigned: someone gave a signal to a member, in the app, through the API or MCP, or a CRM client or audience rule did; a member taking a signal themselves (assigning it to themselves, or rating or moving it) is not sent. With assignee, the webhook gets only the signals given to that member, of the scenarios both they and the key’s user can see: one webhook per person sends each their own signals, for example into their Slack. Events are not promised in order. Each post is JSON with id, type, created_at, text and data. text is a short message with a link to the signal, escaped for Slack (&, < and > as &amp;, &lt; and &gt;), so a Slack incoming webhook, or a Slack workflow with a text variable, can show it as it is. data.signal is the signal as GET /api/v1/signals/{id} returns it when the post is sent; every company and person in it has is_target, true when they are on your watchlist; for signal.assigned, data.assignee is the member with id, name and email. An assignment is not sent once the signal belongs to someone else. Posts are signed as Standard Webhooks sign them: the webhook-signature header is v1, and then the base64 HMAC-SHA256 of {webhook-id}.{webhook-timestamp}.{body}, keyed with the base64-decoded part of the secret after whsec_. The Standard Webhooks libraries check it. Answer 2xx within 10 seconds. A timeout, no answer, 408, 429 or 5xx is tried again for about 7 hours (after 1, 2.5, 6, 16, 39, 98 and 244 minutes, or when Retry-After asks); a retry keeps the id. A redirect or another 4xx is not tried again. A URL that has failed for 3 days is switched off at its next failure, and at once on 410 Gone; disabled_at is set then. The webhook acts as the key’s user: it stops when they, or the member it is for, leave the organization, or when its list is deleted. The URL must resolve to a public address. At most 50 webhooks per organization. The secret is in this answer only.

Bash
curl -X POST "https://app.getzynt.com/api/v1/webhooks" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://hooks.slack.com/triggers/T0123ABCD/8123456789/3f9c2b7e1d4a","events":["signal.assigned"],"assignee":"anna@acme-sales.example"}'
url
The https URL ZYNT posts to, such as a Slack workflow or incoming webhook URL.
events
One or more of signal.created and signal.assigned. A webhook with assignee takes only signal.assigned (422 otherwise).
assignee
An email or user id from /api/v1/members. Leave it out for the whole team. An unknown member is 400 invalid_assignee.
audience_id
A list id from GET /api/v1/audiences. signal.created then sends the new signals about the list’s members, as GET /api/v1/signals?audience_id lists them, instead of those about your watchlist. It needs signal.created in events and cannot go with assignee (422 otherwise). An unknown list is 404. When the list is deleted, ZYNT switches the webhook off.
JSON response
{
  "id": "5d8e2f61-0b4c-4a97-9e13-7c2a6b8d4f05",
  "url": "https://hooks.slack.com/triggers/T0123ABCD/8123456789/3f9c2b7e1d4a",
  "events": [
    "signal.assigned"
  ],
  "assignee_id": "user_2nX8kQvB4yLmR7tZ",
  "audience_id": null,
  "created_by": "user_2nX8kQvB4yLmR7tZ",
  "created_at": "2026-11-10T09:30:00.000Z",
  "failing_since": null,
  "last_error": null,
  "disabled_at": null,
  "secret": "whsec_Zk3QmV9xR2pL7tYw4nB8cD1fH6jK0sA5"
}

List webhooks

GET/api/v1/webhooks

The webhooks you made, oldest first; for an admin, every webhook of the organization. url shows only the host and the last four characters: a Slack URL lets anyone who has it post to the channel. assignee_id is null for a team webhook, and audience_id null for one that is not narrowed to a list. failing_since is when the URL started failing and last_error what went wrong last, both null once an attempt succeeds; disabled_at is set once ZYNT stopped sending. The secret is never listed. No paging.

Bash
curl "https://app.getzynt.com/api/v1/webhooks" \
  -H "Authorization: Bearer <your key>"
JSON response
[
  {
    "id": "5d8e2f61-0b4c-4a97-9e13-7c2a6b8d4f05",
    "url": "https://hooks.slack.com/…1d4a",
    "events": [
      "signal.assigned"
    ],
    "assignee_id": "user_2nX8kQvB4yLmR7tZ",
    "audience_id": null,
    "created_by": "user_2nX8kQvB4yLmR7tZ",
    "created_at": "2026-11-10T09:30:00.000Z",
    "failing_since": null,
    "last_error": null,
    "disabled_at": null
  },
  {
    "id": "8a1f4c27-6e3d-4b80-a952-1d7e3c9b6f42",
    "url": "https://crm.acme-sales.example/…ents",
    "events": [
      "signal.created",
      "signal.assigned"
    ],
    "assignee_id": null,
    "audience_id": null,
    "created_by": "user_2nX8kQvB4yLmR7tZ",
    "created_at": "2026-11-10T09:30:00.000Z",
    "failing_since": "2026-11-09T22:04:00.000Z",
    "last_error": "The URL answered 503",
    "disabled_at": null
  },
  {
    "id": "2c7d9e41-8f3a-4b6c-9d25-6a1e0f4b8c37",
    "url": "https://hooks.slack.com/…7b2e",
    "events": [
      "signal.created"
    ],
    "assignee_id": null,
    "audience_id": "8b2e4c61-3f9a-4d07-a5c1-6e8d2b4f0a93",
    "created_by": "user_2nX8kQvB4yLmR7tZ",
    "created_at": "2026-11-10T09:30:00.000Z",
    "failing_since": null,
    "last_error": null,
    "disabled_at": null
  }
]

Send a test event

POST/api/v1/webhooks/{id}/ping

Posts a webhook.ping event to the URL now, signed like any other, with a text saying ZYNT is connected, and answers with what the URL said: delivered, the HTTP status (null when it could not be reached) and error. It changes nothing, so a webhook ZYNT switched off stays off.

Bash
curl -X POST "https://app.getzynt.com/api/v1/webhooks/5d8e2f61-0b4c-4a97-9e13-7c2a6b8d4f05/ping" \
  -H "Authorization: Bearer <your key>"
id
A webhook id from GET /api/v1/webhooks.
JSON response
{
  "delivered": true,
  "status": 200,
  "error": null
}

Send unsent events now

POST/api/v1/webhooks/{id}/scan

ZYNT checks a webhook for new and assigned signals after each one arrives; this runs that check now. Within a minute the URL gets every event of the last 48 hours it has not had yet, counted from when the webhook was made if that is later. An event already sent is never sent again, so calling this twice sends nothing new. Useful right after adding a webhook, to see the signals of the past hours. It takes no body. started is false when ZYNT switched the webhook off; delete it and add it again to send.

Bash
curl -X POST "https://app.getzynt.com/api/v1/webhooks/5d8e2f61-0b4c-4a97-9e13-7c2a6b8d4f05/scan" \
  -H "Authorization: Bearer <your key>"
id
A webhook id from GET /api/v1/webhooks.
JSON response
{
  "started": true
}

Delete a webhook

DELETE/api/v1/webhooks/{id}

Stops the webhook at once; an event still being retried is dropped. A member deletes only the webhooks they made, an admin any. To turn on a webhook ZYNT switched off, delete it and add it again.

Bash
curl -X DELETE "https://app.getzynt.com/api/v1/webhooks/5d8e2f61-0b4c-4a97-9e13-7c2a6b8d4f05" \
  -H "Authorization: Bearer <your key>"
id
A webhook id from GET /api/v1/webhooks.
JSON response
{
  "id": "5d8e2f61-0b4c-4a97-9e13-7c2a6b8d4f05",
  "deleted": true
}

Events

List events

GET/api/v1/events

Events with dates, location and scores, earliest start first unless sort says otherwise. For the events most worth a visit, ask timing=upcoming&sort=highest-score. score is null for an event that is not scored. app_url opens the event in the ZYNT app. watched_participants lists the companies and people you watch that take part; an upcoming event with one is added at once, before its score. Every field is always returned; fields is not supported. Keep the same filters on every page and skip ids you already have.

Bash
curl --get "https://app.getzynt.com/api/v1/events" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "timing=upcoming" \
  --data-urlencode "sort=highest-score" \
  --data-urlencode "city=Warsaw" \
  --data-urlencode "limit=25"
search
Case-insensitive match in the event name, description, venue and full location.
city
Case-insensitive city match. Combines with search using AND.
watched
true keeps only events where a company or person you watch takes part; false or no value keeps all. Combines with the other filters using AND.
timing
upcoming keeps events that start now or later, past keeps events that started before now, all (the default) keeps both.
sort
earliest (the default) and latest order by start date; highest-score and lowest-score order by score, where an unscored event counts as 0.
cursor
The next_cursor of the previous page. Omit it on the first request.
limit
How many events to return, from 1 to 100; 25 when you leave it out. To read more than a few, ask for 100: one page of 100 is one request instead of four.
JSON response
{
  "data": [
    {
      "id": "7c13...",
      "title": "Technology Summit",
      "source_url": "https://example.com/events/technology-summit",
      "website_url": "https://example.com/summit",
      "app_url": "https://app.getzynt.com/events?eventId=7c13...",
      "start_at": "2026-10-15T08:00:00.000Z",
      "end_at": "2026-10-15T16:00:00.000Z",
      "location_name": "Conference Centre",
      "location_address": "Warsaw, Poland",
      "city": "Warsaw",
      "is_virtual": false,
      "score": 74,
      "score_breakdown": {
        "items": [
          {
            "key": "audience-value",
            "label": "audience-value",
            "icon": "users",
            "points": 18,
            "max_points": 20
          }
        ],
        "recommendation": "Book a meeting slot with the logistics track speakers."
      },
      "watched_participants": [
        {
          "id": "company_123",
          "type": "company",
          "name": "Northwind Logistics",
          "role": "exhibitor"
        }
      ]
    }
  ],
  "next_cursor": null
}

Get an event

GET/api/v1/events/{id}

One event with every list field, plus description, key_insights and topic. topic can be null.

Bash
curl "https://app.getzynt.com/api/v1/events/7c13..." \
  -H "Authorization: Bearer <your key>"
id
An event id from your event list.
JSON response
{
  "id": "7c13...",
  "title": "Technology Summit",
  "source_url": "https://example.com/events/technology-summit",
  "website_url": "https://example.com/summit",
  "app_url": "https://app.getzynt.com/events?eventId=7c13...",
  "start_at": "2026-10-15T08:00:00.000Z",
  "end_at": "2026-10-15T16:00:00.000Z",
  "location_name": "Conference Centre",
  "location_address": "Warsaw, Poland",
  "city": "Warsaw",
  "is_virtual": false,
  "score": 74,
  "score_breakdown": {
    "items": [
      {
        "key": "audience-value",
        "label": "audience-value",
        "icon": "users",
        "points": 18,
        "max_points": 20
      }
    ],
    "recommendation": "Book a meeting slot with the logistics track speakers."
  },
  "watched_participants": [
    {
      "id": "company_123",
      "type": "company",
      "name": "Northwind Logistics",
      "role": "exhibitor"
    }
  ],
  "description": "A one-day summit for technology leaders in Central Europe.",
  "key_insights": "Several logistics companies from your target list are speaking.",
  "topic": "Technology"
}

List who is at an event

GET/api/v1/events/{id}/participants

The companies (type=company, the default) or the people (type=person) that take part in one event, as the event in the app lists them: watchlist entries first, then by name. record_id is the matched ZYNT company or person, null when not matched. title, company, linkedin_url and website_url are null when unknown. booth, hall, tier, session, session_at and source_url say what the event pages say, null when they say nothing. total counts the participants of this type and role. An event you cannot see returns 404.

Bash
curl --get "https://app.getzynt.com/api/v1/events/7c13.../participants" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "type=company" \
  --data-urlencode "role=exhibitor" \
  --data-urlencode "limit=50"
id
An event id from your event list.
type
company (the default) or person.
role
Only participants with this role: speaker, organizer, sponsor, exhibitor, partner, attendee, speaker_affiliation, influencer, decision_maker, other. No value keeps every role.
cursor
The next_cursor of the previous page. Omit it on the first request.
limit
How many participants to return, from 1 to 100; 25 when you leave it out. To read more than a few, ask for 100: one page of 100 is one request instead of four.
JSON response
{
  "data": [
    {
      "id": "7c1f3a52-9d4e-4b8a-a0c6-3e5f7b9d1a24",
      "type": "company",
      "name": "Northwind Logistics",
      "role": "exhibitor",
      "record_id": "company_123",
      "on_watchlist": true,
      "title": null,
      "company": null,
      "linkedin_url": "https://www.linkedin.com/company/northwind-logistics",
      "website_url": "https://northwind.example",
      "booth": "B12",
      "hall": "Hall 3",
      "tier": null,
      "session": null,
      "session_at": null,
      "source_url": "https://summit.example/exhibitors"
    }
  ],
  "total": 1,
  "next_cursor": null
}

Add events from links

POST/api/v1/events

The app’s “Add event”. ZYNT reads each page, scores the event for a scenario and adds it to your events, usually within minutes; it shows in GET /api/v1/events once scored. ZYNT drops tracking parameters and a trailing slash and sends a link once, so the answer lists the cleaned links. outcome is queued, requeued after an earlier failure, or already_scored when ZYNT has it.

Bash
curl -X POST "https://app.getzynt.com/api/v1/events" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"urls":["https://logistics-expo.example.com/2027"]}'
urls
1 to 25 http or https links to event pages.
scenario_id
The scenario the events are for, as scenario_id on a signal. Leave it out when your organization has one scenario; with several, unknown_scenario lists them.
JSON response
{
  "scenario_id": "9a417d2e-6c3b-4f80-a195-7e2d4c6b8a01",
  "events": [
    {
      "url": "https://logistics-expo.example.com/2027",
      "outcome": "queued"
    }
  ]
}

Rate an event

PUT/api/v1/events/{id}/feedback

The same feedback as on the event in the app. An event has one rating for the team, so each call replaces the last one. Returns the rating as saved.

Bash
curl -X PUT "https://app.getzynt.com/api/v1/events/7c13.../feedback" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"stars":4,"comment":"Our buyers go there every year"}'
id
An event id from your event list.
stars
1 to 5, or null to clear the rating. 1 or 2 show in the app as less like this, 3 to 5 as more like this. Required.
comment
Up to 1000 characters. Omit it, or send null or an empty text, for no comment; a rating sent without one clears the old comment.
JSON response
{
  "id": "7c13...",
  "stars": 4,
  "comment": "Our buyers go there every year"
}

Say whether you go to an event

PUT/api/v1/events/{id}/attendance

The key’s user’s own answer to “are you going”, as on the event in the app. Each teammate has their own answer.

Bash
curl -X PUT "https://app.getzynt.com/api/v1/events/7c13.../attendance" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"decision":"yes"}'
id
An event id from your event list.
decision
yes, no or undecided.
JSON response
{
  "event_id": "7c13...",
  "decision": "yes"
}

Companies

Add companies

POST/api/v1/companies

The app’s company import: puts up to 100 companies on one of your lists and adds to ZYNT the ones it does not know yet, so ZYNT starts following them. outcome is created, existing, already_in_audience, invalid with the reason in issue (name_required, website_required, first_name_required, last_name_required, linkedin_required, invalid_linkedin, invalid_website or invalid_email), or failed. Without a list of that kind the answer is 404 and ZYNT adds nothing.

Bash
curl -X POST "https://app.getzynt.com/api/v1/companies" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"audience_id":"6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63","companies":[{"name":"Nordwave Logistics","website_url":"nordwave-logistics.example","linkedin_url":"https://www.linkedin.com/company/nordwave-logistics"}]}'
audience_id
A list of companies from /api/v1/audiences. Leave it out for the team’s default list.
companies
Each with name and website_url, and optionally linkedin_url and tax_id. ZYNT matches companies by website and LinkedIn.
JSON response
{
  "audience_id": "6a2f9c41-8d3e-4b7a-a915-2c4e8f0b7d63",
  "results": [
    {
      "index": 0,
      "outcome": "created",
      "id": "3d8e1a5c-7f2b-4c90-b6e4-9a1d0c5f2e87",
      "name": "Nordwave Logistics",
      "issue": null
    }
  ]
}

Look up a company

GET/api/v1/companies/lookup

Use this when you already know the company: send its LinkedIn URL or website and get the one company ZYNT knows by it, or 404. The company needs no recent activity, and lead search does not need to be on. ZYNT does not add a company it has never seen. Fields ZYNT does not know are null. is_target is true when the company is in one of your audiences. With both, the LinkedIn URL is tried first, then the website. A website can be shared, for example a social page saved as a company's website, so a match by website is less sure than one by LinkedIn URL. When two companies share a website, the oldest wins. To find new companies, use search.

Bash
curl --get "https://app.getzynt.com/api/v1/companies/lookup" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "linkedin_url=https://www.linkedin.com/company/acme-robotics" \
  --data-urlencode "include=signals"
linkedin_url
A full company LinkedIn URL. Matched exactly once both URLs are normalized, so the host variant, a trailing slash or query parameters do not matter.
website
The website or domain, e.g. acme.pl or https://www.acme.pl/about. Only the host counts, without www.
include
signals adds a signals field: the 10 newest signals about the record that the key owner can see, the same page /api/v1/signals returns, with next_cursor for the rest.
JSON response
{
  "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
  "name": "Acme Robotics",
  "domain": "acme-robotics.example",
  "website_url": "https://acme-robotics.example",
  "linkedin_url": "https://www.linkedin.com/company/acme-robotics",
  "description": "Warehouse automation robots for European logistics.",
  "industry": "Automation Machinery Manufacturing",
  "employee_range": "51-200",
  "location": "Wrocław, Poland",
  "logo_url": "https://media.example.com/acme-robotics.png",
  "is_target": true,
  "signals": {
    "data": [
      {
        "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
        "scenario_id": "9a417d2e-6c3b-4f80-a195-7e2d4c6b8a01",
        "title": "Acme Robotics raises €18M to expand warehouse automation",
        "score": 97,
        "status": {
          "id": "3b7e2c9d-1a5f-4d68-b023-9c7e6a4f2d10",
          "name": "New",
          "type": "todo"
        },
        "assignee_id": null,
        "summary": "Acme Robotics announced a Series A round to grow its European operations.",
        "source_url": "https://news.example.com/acme-robotics-series-a",
        "image_url": "https://news.example.com/favicon.ico",
        "app_url": "https://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
        "received_at": "2026-09-01T08:14:00.000Z",
        "companies": [
          {
            "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
            "name": "Acme Robotics",
            "website_url": "https://acme-robotics.example",
            "linkedin_url": null,
            "description": "",
            "is_target": true
          }
        ],
        "favorite": false
      }
    ],
    "next_cursor": null
  }
}

Get a company’s timeline

GET/api/v1/companies/{id}/timeline

Every source that mentions the company: news, articles, other mentions, LinkedIn posts, comments, reactions, reposts, job posts and signals. The same timeline as the company profile in the app. occurred_at is when ZYNT found the source; sort and period use it too. One URL comes once, however often it was found; case and a trailing slash do not matter. When your organization has a signal from the source that is not archived, signal holds the highest-scored one with its id, score, scenario and app_url, its link in the ZYNT app; otherwise it is null. evidence, source.platform and signal.scenario can be null. An unknown id returns 404 not_found; a known id with nothing that matches the filters returns an empty page.

Bash
curl --get "https://app.getzynt.com/api/v1/companies/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49/timeline" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "kind=news" \
  --data-urlencode "period=90"
id
A company id from a signal, or from /api/v1/companies/lookup or /search.
kind
Only items of one kind: article, news, mention, linkedin_post, comment, reaction, repost, job_post or signal.
relation
Only items where the company is the author, the subject, or only mentioned: author, subject or mentioned.
period
Only items ZYNT found in the last 7, 30, 90 or 365 days, or all. Defaults to all.
search
Case-insensitive match in the source text, evidence, URL and signal title.
sort
newest or oldest first. Defaults to newest.
cursor
The next_cursor of the previous page. Omit it on the first request.
limit
How many items to return, from 1 to 100; 25 when you leave it out. To read more than a few, ask for 100: one page of 100 is one request instead of four.
JSON response
{
  "data": [
    {
      "id": "5b8e2f14-7a3c-4d91-b6e0-2c4f8a1d9e73",
      "kind": "news",
      "title": "Acme Robotics opens a second plant in Gdańsk",
      "occurred_at": "2026-09-24T08:30:00.000Z",
      "relation": "subject",
      "evidence": "Acme Robotics will open a second plant in Gdańsk next spring.",
      "source": {
        "label": "example.com",
        "platform": null,
        "url": "https://example.com/news/acme-gdansk-plant"
      },
      "signal": {
        "id": "0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d",
        "score": 82,
        "scenario": "Manufacturing expansion",
        "app_url": "https://app.getzynt.com/signals?signalId=0f2c1e7a-3b4d-4f6a-8c9e-1d2f3a4b5c6d"
      }
    }
  ],
  "next_cursor": null
}

List a company’s employees

GET/api/v1/companies/{id}/employees

The people ZYNT knows who work at the company now, by last name, as the Employees section of the company in the app. People at a company merged into this one count too. title, linkedin_url and profile_image_url can be null. is_target is true when the person is on your team’s watchlist (the default people list in Audiences). total counts them all. An unknown id returns 404 not_found.

Bash
curl --get "https://app.getzynt.com/api/v1/companies/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49/employees" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "limit=100"
id
A company id from a signal, or from /api/v1/companies/lookup or /search.
cursor
The next_cursor of the previous page. Omit it on the first request.
limit
How many people to return, from 1 to 100; 25 when you leave it out. To read more than a few, ask for 100: one page of 100 is one request instead of four.
JSON response
{
  "data": [
    {
      "id": "2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816",
      "full_name": "Anna Nowak",
      "title": "Head of Operations",
      "linkedin_url": "https://www.linkedin.com/in/anna-nowak",
      "profile_image_url": "https://media.example.com/anna.png",
      "is_target": true
    },
    {
      "id": "5b8d2f61-3c9e-4a17-8e40-d1f6a2c7b935",
      "full_name": "Piotr Zieliński",
      "title": "CTO",
      "linkedin_url": "https://www.linkedin.com/in/piotr-zielinski",
      "profile_image_url": null,
      "is_target": false
    }
  ],
  "total": 2,
  "next_cursor": null
}

List a company’s relationships

GET/api/v1/companies/{id}/relationships

The companies and people ZYNT found tied to the company in news, posts and profiles, as the Relationships section of the company in the app: one record each, strongest first unless sort says otherwise. relationship is the strongest tie and other_relationships the other ties of the same section: a record with a business tie lists only business ties. direction is outgoing when this company acquired, founded or invested in the other, incoming when the other did, and null for ties without a direction. status says whether the person and the company are tied by a job ZYNT can confirm from a work history, now (current) or before (former), whatever the tie; it is unconfirmed otherwise and for two companies or two people. details holds what ZYNT read about the tie, such as a role or a deal value. evidence holds the quotes and their sources; occurred_at and confidence can be null. is_target is true when the record is on your team’s watchlist. ZYNT reads at most 500 facts, business ones and the newest first, and folds them into records; when there were more, truncated is true and total counts only what was read. An unknown id returns 404 not_found.

Bash
curl --get "https://app.getzynt.com/api/v1/companies/7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49/relationships" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "section=business" \
  --data-urlencode "limit=100"
id
A company id from a signal, or from /api/v1/companies/lookup or /search.
type
Only companies or only people: company or person. Both when left out.
section
business: ties such as works at, founded, investment or partner. possible: only mentioned together, reposted or attended the same event. Both when left out.
label
Only records with this tie, as relationship or other_relationships writes it, in any case: Works at, Founded, Board, Acquired, Investment, Partner, Supplier, Competitor, Collaborated, Organiser, Mentioned together, Reposted, Attended, or another type in its own words.
search
Case-insensitive match in the name, subtitle, ties and evidence quotes.
sort
strongest (founders and employers first, mentions last), recent (newest evidence first) or mentions (most evidence first). Defaults to strongest.
cursor
The next_cursor of the previous page. Omit it on the first request. Send the same filters and limit with it.
limit
How many related records to return, from 1 to 100; 25 when you leave it out. To read more than a few, ask for 100: one page of 100 is one request instead of four.
JSON response
{
  "data": [
    {
      "id": "2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816",
      "type": "person",
      "name": "Anna Nowak",
      "subtitle": "Head of Operations",
      "image_url": "https://media.example.com/anna.png",
      "is_target": true,
      "relationship": "Works at",
      "other_relationships": [],
      "section": "business",
      "direction": null,
      "status": "current",
      "last_confirmed_at": "2026-10-02T07:40:00.000Z",
      "details": [
        {
          "key": "role",
          "value": "Head of Operations"
        }
      ],
      "evidence": [
        {
          "quote": "Anna Nowak, Head of Operations at Acme Robotics, said the new site opens in March.",
          "source": "logistics-news.example",
          "url": "https://logistics-news.example/acme-robotics-opens-poznan-site",
          "occurred_at": "2026-10-02T07:40:00.000Z",
          "confidence": 0.92
        }
      ]
    },
    {
      "id": "9f3b6c2e-1d48-4a7f-b5e0-2c8d7a1f6e43",
      "type": "company",
      "name": "Nordwave Logistics",
      "subtitle": "Transportation, Logistics · 201-500",
      "image_url": "https://media.example.com/nordwave.png",
      "is_target": false,
      "relationship": "Partner",
      "other_relationships": [
        "Supplier"
      ],
      "section": "business",
      "direction": null,
      "status": "unconfirmed",
      "last_confirmed_at": "2026-10-02T07:40:00.000Z",
      "details": [],
      "evidence": [
        {
          "quote": "Acme Robotics and Nordwave Logistics will run the Poznań site together.",
          "source": "logistics-news.example",
          "url": "https://logistics-news.example/acme-robotics-opens-poznan-site",
          "occurred_at": "2026-10-02T07:40:00.000Z",
          "confidence": 0.92
        }
      ]
    }
  ],
  "total": 2,
  "truncated": false,
  "next_cursor": null
}

People

Add people

POST/api/v1/people

The app’s people import: puts up to 100 people on one of your lists and adds to ZYNT the ones it does not know yet, so ZYNT starts following them. outcome is created, existing, already_in_audience, invalid with the reason in issue (name_required, website_required, first_name_required, last_name_required, linkedin_required, invalid_linkedin, invalid_website or invalid_email), or failed. Without a list of that kind the answer is 404 and ZYNT adds nothing.

Bash
curl -X POST "https://app.getzynt.com/api/v1/people" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"people":[{"first_name":"Marta","last_name":"Wiśniewska","linkedin_url":"https://www.linkedin.com/in/marta-wisniewska-example","email":"marta@nordwave-logistics.example","title":"Head of Operations"}]}'
audience_id
A list of people from /api/v1/audiences. Leave it out for the team’s default list.
people
Each with first_name, last_name, linkedin_url and email, and optionally title. ZYNT matches people by LinkedIn and email.
JSON response
{
  "audience_id": "legacy-people",
  "results": [
    {
      "index": 0,
      "outcome": "existing",
      "id": "8b4f2e6a-1c9d-4a37-95e0-7d3c2b1a6f48",
      "name": "Marta Wiśniewska",
      "issue": null
    }
  ]
}

Read a person’s email and phone

GET/api/v1/people/{id}/contacts

The emails and phones your team already has for the person. Finding a new one uses credits, so the API does not do it: when your team has none, the answer is 404 and someone uses Find email or Find phone on the person in the app.

Bash
curl "https://app.getzynt.com/api/v1/people/8b4f2e6a-1c9d-4a37-95e0-7d3c2b1a6f48/contacts" \
  -H "Authorization: Bearer <your key>"
id
A person id from a signal, a lookup or a search.
JSON response
{
  "person_id": "8b4f2e6a-1c9d-4a37-95e0-7d3c2b1a6f48",
  "contacts": [
    {
      "channel": "email",
      "value": "marta@nordwave-logistics.example",
      "status": "valid",
      "source": "prospeo",
      "verified_at": "2026-10-21T09:12:00.000Z"
    }
  ]
}

Look up a person

GET/api/v1/people/lookup

Use this when you already know the person: send their LinkedIn URL and get the one person ZYNT knows by it, or 404. The person needs no recent activity, and lead search does not need to be on. ZYNT does not add a person it has never seen. Fields ZYNT does not know are null. is_target is true when the person is in one of your audiences. company is null for a person with no current company. To find new people, use search.

Bash
curl --get "https://app.getzynt.com/api/v1/people/lookup" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "linkedin_url=https://www.linkedin.com/in/anna-nowak"
linkedin_url
A full person LinkedIn URL. Matched exactly once both URLs are normalized, so the host variant, a trailing slash or query parameters do not matter.
include
signals adds a signals field: the 10 newest signals about the record that the key owner can see, the same page /api/v1/signals returns, with next_cursor for the rest.
JSON response
{
  "id": "2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816",
  "full_name": "Anna Nowak",
  "title": "Head of Operations",
  "headline": "Head of Operations at Acme Robotics",
  "location": "Wrocław, Poland",
  "linkedin_url": "https://www.linkedin.com/in/anna-nowak",
  "profile_image_url": "https://media.example.com/anna.png",
  "company": {
    "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
    "name": "Acme Robotics",
    "website_url": "https://acme-robotics.example",
    "linkedin_url": "https://www.linkedin.com/company/acme-robotics"
  },
  "is_target": true
}

Get a person’s timeline

GET/api/v1/people/{id}/timeline

Every source that mentions the person: news, articles, other mentions, LinkedIn posts, comments, reactions, reposts, job posts and signals. The same timeline as the person profile in the app. occurred_at is when ZYNT found the source; sort and period use it too. One URL comes once, however often it was found; case and a trailing slash do not matter. When your organization has a signal from the source that is not archived, signal holds the highest-scored one with its id, score, scenario and app_url, its link in the ZYNT app; otherwise it is null. evidence, source.platform and signal.scenario can be null. An unknown id returns 404 not_found; a known id with nothing that matches the filters returns an empty page.

Bash
curl --get "https://app.getzynt.com/api/v1/people/2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816/timeline" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "relation=author"
id
A person id from a signal, or from /api/v1/people/lookup or /search.
kind
Only items of one kind: article, news, mention, linkedin_post, comment, reaction, repost, job_post or signal.
relation
Only items where the person is the author, the subject, or only mentioned: author, subject or mentioned.
period
Only items ZYNT found in the last 7, 30, 90 or 365 days, or all. Defaults to all.
search
Case-insensitive match in the source text, evidence, URL and signal title.
sort
newest or oldest first. Defaults to newest.
cursor
The next_cursor of the previous page. Omit it on the first request.
limit
How many items to return, from 1 to 100; 25 when you leave it out. To read more than a few, ask for 100: one page of 100 is one request instead of four.
JSON response
{
  "data": [
    {
      "id": "8d1f4a27-2c6e-4b93-a5d0-7e3b9c1f6a48",
      "kind": "linkedin_post",
      "title": "Anna Nowak: We are hiring our first sales team in Germany",
      "occurred_at": "2026-09-22T14:05:00.000Z",
      "relation": "author",
      "evidence": "We are hiring our first sales team in Germany.",
      "source": {
        "label": "LinkedIn",
        "platform": null,
        "url": "https://www.linkedin.com/posts/anna-nowak_hiring-germany"
      },
      "signal": null
    }
  ],
  "next_cursor": null
}

List a person’s relationships

GET/api/v1/people/{id}/relationships

The companies and people ZYNT found tied to the person in news, posts and profiles, as the Relationships section of the person in the app: one record each, strongest first unless sort says otherwise. relationship is the strongest tie and other_relationships the other ties of the same section: a record with a business tie lists only business ties. direction is outgoing when this person acquired, founded or invested in the other, incoming when the other did, and null for ties without a direction. status says whether the person and the company are tied by a job ZYNT can confirm from a work history, now (current) or before (former), whatever the tie; it is unconfirmed otherwise and for two companies or two people. details holds what ZYNT read about the tie, such as a role or a deal value. evidence holds the quotes and their sources; occurred_at and confidence can be null. is_target is true when the record is on your team’s watchlist. ZYNT reads at most 500 facts, business ones and the newest first, and folds them into records; when there were more, truncated is true and total counts only what was read. An unknown id returns 404 not_found.

Bash
curl --get "https://app.getzynt.com/api/v1/people/2e9c4b17-6d3a-4f85-9b21-c7a0e5d3f816/relationships" \
  -H "Authorization: Bearer <your key>" \
  --data-urlencode "type=company"
id
A person id from a signal, or from /api/v1/people/lookup or /search, or a company’s employees.
type
Only companies or only people: company or person. Both when left out.
section
business: ties such as works at, founded, investment or partner. possible: only mentioned together, reposted or attended the same event. Both when left out.
label
Only records with this tie, as relationship or other_relationships writes it, in any case: Works at, Founded, Board, Acquired, Investment, Partner, Supplier, Competitor, Collaborated, Organiser, Mentioned together, Reposted, Attended, or another type in its own words.
search
Case-insensitive match in the name, subtitle, ties and evidence quotes.
sort
strongest (founders and employers first, mentions last), recent (newest evidence first) or mentions (most evidence first). Defaults to strongest.
cursor
The next_cursor of the previous page. Omit it on the first request. Send the same filters and limit with it.
limit
How many related records to return, from 1 to 100; 25 when you leave it out. To read more than a few, ask for 100: one page of 100 is one request instead of four.
JSON response
{
  "data": [
    {
      "id": "7c5a1e3b-9d2f-4a60-b817-3e6c8d0f2a49",
      "type": "company",
      "name": "Acme Robotics",
      "subtitle": "Automation Machinery Manufacturing · 51-200",
      "image_url": "https://media.example.com/acme-robotics.png",
      "is_target": true,
      "relationship": "Works at",
      "other_relationships": [],
      "section": "business",
      "direction": null,
      "status": "current",
      "last_confirmed_at": "2026-10-02T07:40:00.000Z",
      "details": [
        {
          "key": "role",
          "value": "Head of Operations"
        }
      ],
      "evidence": [
        {
          "quote": "Anna Nowak, Head of Operations at Acme Robotics, said the new site opens in March.",
          "source": "logistics-news.example",
          "url": "https://logistics-news.example/acme-robotics-opens-poznan-site",
          "occurred_at": "2026-10-02T07:40:00.000Z",
          "confidence": 0.92
        }
      ]
    }
  ],
  "total": 1,
  "truncated": false,
  "next_cursor": null
}

Setup

Read the setup

GET/api/v1/setup

For a script or AI agent that sets ZYNT up for the user. It returns the setup chat the key’s user has open: their sign-up at /start, or a scenario they add in Settings → Business. zynt_said holds what ZYNT said since the last answer, its question last; answers lists what the setup takes now, each with kind and what it means; suggestions are answers the user could tap; next says the one thing to do now. step runs company (website, what they sell, LinkedIn, phone), customers (questions about who buys, signals to rate, the list of signals), summary (what ZYNT understood, for the user to confirm), connect (companies to follow, tools only the user connects, colleagues to invite) and done. signal shows when a signal waits for a rating, signal_list when the list of signals waits, summary on the summary, companies_audience_id on the companies step. knows is what ZYNT knows, one line a topic; topics_left counts the required topics still open. With no setup open, 409 no_open_setup says why, as for the notes.

Bash
curl "https://app.getzynt.com/api/v1/setup" \
  -H "Authorization: Bearer <your key>"
JSON response
{
  "revision": 7,
  "step": "customers",
  "zynt_said": [
    "Which markets do you sell to? Name the countries in the order you go after them."
  ],
  "answers": [
    {
      "kind": "text",
      "means": "The answer to ZYNT’s question, in the user’s words."
    },
    {
      "kind": "skip",
      "means": "The user does not know; ZYNT asks something else."
    }
  ],
  "suggestions": [
    "Poland",
    "Germany",
    "Czechia"
  ],
  "knows": [
    {
      "topic": "Offer",
      "text": "Route planning software for mid-size carriers"
    }
  ],
  "topics_left": 4,
  "setup_url": "https://app.getzynt.com/start",
  "next": "Answer ZYNT with one of answers. Use what you know from the user’s files and notes; ask the user only what you cannot find. Then read the next question in the reply."
}

Answer the setup

POST/api/v1/setup/answer

Answers the setup for the user, as they would in the app, and returns the setup after the answer with its next question. The app shows the answer as sent by their AI agent, and updates while the user watches. A yes on the summary confirms what ZYNT understood and starts the watching: show the user the summary and wait for their yes first. An answer the setup does not take now is 400 unknown_answer, with the kinds it takes in allowed; a setup that moved on since you read it, as when the user answered in the app, is 409 setup_changed: read it again. The website answer takes up to a minute, because ZYNT reads the site and looks for the first signals.

Bash
curl -X POST "https://app.getzynt.com/api/v1/setup/answer" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"revision":7,"answer":{"kind":"text","text":"Poland first, then Germany"}}'
revision
The revision from the setup you read. The answer goes to the question you saw, never to a newer one.
answer
One of the answers the setup lists now, by kind: text {text}, yes, no, skip, finish, rate {useful, why}, signals {signals: ids from signal_list, competitors}, invite {emails, up to 10}.
JSON response
{
  "revision": 7,
  "step": "customers",
  "zynt_said": [
    "Which markets do you sell to? Name the countries in the order you go after them."
  ],
  "answers": [
    {
      "kind": "text",
      "means": "The answer to ZYNT’s question, in the user’s words."
    },
    {
      "kind": "skip",
      "means": "The user does not know; ZYNT asks something else."
    }
  ],
  "suggestions": [
    "Poland",
    "Germany",
    "Czechia"
  ],
  "knows": [
    {
      "topic": "Offer",
      "text": "Route planning software for mid-size carriers"
    }
  ],
  "topics_left": 4,
  "setup_url": "https://app.getzynt.com/start",
  "next": "Answer ZYNT with one of answers. Use what you know from the user’s files and notes; ask the user only what you cannot find. Then read the next question in the reply."
}

Send business notes to the setup

POST/api/v1/setup/context

For an AI agent that knows the user’s business, such as one running GTM Brain. It sends the files once, and the user does not type the same again in the setup chat. The files go to the setup the key’s user has open: their sign-up at /start, or a scenario they add in Settings → Business. With none open, or once the setup shows its summary for the user to check, 409 no_open_setup: its message says what state the setup is in, its hint what to tell the user, and reason names the case (no_setup, discarded, changing_brain, setup_over, connecting_tools, summary_shown, workspace_open, new_chat, chat_busy). One setup reads 20 files in all; files past that answer 429 setup_file_limit before anything is read. ZYNT reads each file once and adds the facts it states as guesses, each with the words it rests on; a fact whose words are not in the file is dropped. Current customers become companies to exclude. The user confirms the guesses on the setup’s summary, in the app at setup_url or through POST /api/v1/setup/answer once they agree. ZYNT keeps the files and no endpoint returns their text. facts counts the guesses added, not those ZYNT already held; unread counts the files ZYNT could not read, kept all the same. When it reads none, nothing is kept and the answer is 503: send them again. Reading takes up to a minute.

Bash
curl -X POST "https://app.getzynt.com/api/v1/setup/context" \
  -H "Authorization: Bearer <your key>" \
  -H "Content-Type: application/json" \
  -d '{"files":[{"name":"context.md","path":"brain/contexts/icp/context.md","content":"## Who buys\n- Heads of logistics at mid-size carriers (customer interviews)\n\n## Markets\n- Poland first, then Germany (strategy.md)"}]}'
files
1 to 10 files. Each has name (what the file is, such as strategy.md, up to 200 characters), path (optional: where it lives in the brain or the agent’s memory) and content (its text, 1 to 30000 characters). Send strategy and customer documents, context summaries and the customer list; never passwords, keys, personal emails, phone numbers or copied conversations.
JSON response
{
  "files": 1,
  "facts": 3,
  "unread": 0,
  "topics": [
    "buyers",
    "markets"
  ],
  "setup_url": "https://app.getzynt.com/start"
}

Your key

Check your API key

GET/api/v1/health

Checks the key and its user. Send the same Authorization header as for the other endpoints.

Bash
curl "https://app.getzynt.com/api/v1/health" \
  -H "Authorization: Bearer <your key>"
JSON response
{
  "status": "ok"
}
ZYNT API · v1.0.0