Meetcatcher API documentation

Meetcatcher has a REST API you can use to connect your leads and meetings to your own tools and custom solutions.

1Overview

The Meetcatcher API gives you access to your own leads and confirmed meetings, and lets you subscribe to events through webhooks (REST hooks). It is built mainly for automation integrations such as Zapier.

Current limitationWebhook subscriptions currently accept only Zapier URLs (https://hooks.zapier.com). All other endpoints work with any HTTP client.

2Base URL and format

https://server.sentiscrape.cz:38443/meetcatcher_PROD/api

Requests and responses use JSON in UTF-8.
Times use ISO 8601 in UTC, for example 2026-01-20T10:30:00Z.
Missing values are sent as null.

3Authentication

Generate your key in Meetcatcher under Profile → Integrations. The full key is shown only once, so store it safely.

Send the key with every request in the X-API-Key header.

curl -H "X-API-Key: mc_…" https://server.sentiscrape.cz:38443/meetcatcher_PROD/api/me

An invalid, revoked or missing key returns 401 with an empty body.
Generating a new key or revoking the current one invalidates the old key and removes all webhook subscriptions.

4Endpoints

EndpointPurposeSuccess

GET/api/meOwner of the key. Use it to test the connection.200 { "id", "name", "company" }

POST/api/hooksSubscribe to an event.201 { "id", "event" }

DELETE/api/hooks/{id}Remove a subscription. Unknown IDs are ignored.204

GET/api/leadsLast 20 leads, newest first.200 array of leads

GET/api/meetingsLast 20 confirmed meetings, newest first.200 array of meetings

POSTRequest body for /api/hooks

{
  "targetUrl": "https://hooks.zapier.com/hooks/standard/…",
  "event": "lead.created"
}

targetUrl: Required. Up to 512 characters. Only https://hooks.zapier.com URLs are accepted.
event: Required. lead.created or meeting.confirmed.

LimitEach user can have up to 20 subscriptions.

5Events (webhooks)

How we deliver

We send a POST to your targetUrl with a JSON body. The body is the same as one item from the matching list (/api/leads or /api/meetings).
Any 2xx response counts as success.
A 410 Gone response removes the subscription.
Timeouts are 3 seconds to connect and 5 seconds for the response.

What you can't rely onDelivery is best-effort and failed deliveries are not retried. The order of events is not guaranteed. Remove duplicates on your side using the id field.

lead.createdSent when Meetcatcher finds a new lead for you. The body is a Lead object.

meeting.confirmedSent when a meeting is confirmed. Both the organizer and the participant receive it, each from their own point of view. Use the role field to tell them apart.

6Objects

Returned by GET /api/leads and sent with the lead.created event.

id: integerUnique ID of the lead
foundAt: string (ISO 8601)When Meetcatcher found the lead
leadUrl: string (URL)Link to the lead in Meetcatcher
company: stringCompany name
contactFirstName: stringnullableFirst name of the contact
generalDescription: stringnullableShort description of the lead
matchScore: integernullableMatch score from 0 to 100
interestedInYou: stringnullableWhy they might be interested
helpsYou: stringnullableHow they could help you

Example lead

{
  "id": 1234,
  "foundAt": "2026-01-15T08:30:00Z",
  "leadUrl": "https://meetcatcher.com/app/leads/1234",
  "company": "Acme Inc.",
  "contactFirstName": "Jane",
  "generalDescription": "A company whose needs match what you offer.",
  "matchScore": 87,
  "interestedInYou": "Your services. They are looking for a partner with your expertise.",
  "helpsYou": "New contacts. They work with companies that could use your services."
}