LidmeoDevelopers

Webhooks

Receive your account's events on your server, signed, usually within a minute.

A webhook sends each event of your account (an accepted invitation, a reply, a stage set…) to an HTTPS address of your choice, as a POST, signed with the Standard Webhooks standard.

Creating an endpoint

In Lidmeo: Assistant IA et intégrations (AI assistant and integrations), Pour les développeurs (for developers), Webhooks section, Ajouter une adresse de réception (add an endpoint). Choose the events; the signing secret (whsec_…) is shown only once. The screen only shows the real account's endpoints.

Through the API, with the webhooks:manage scope:

curl https://api.lidmeo.com/v1/webhook_endpoints \
  -H "Authorization: Bearer $LIDMEO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/webhooks/lidmeo",
    "enabled_events": ["invitation.accepted", "prospect.replied"],
    "description": "To the CRM"
  }'
  • The address: HTTPS on port 443, a public domain name (never an IP address, localhost or an internal name), without credentials in it. A redirect is not followed.
  • The events: a list of types, or ["*"] for all. See the catalog.
  • The scopes of whoever creates the endpoint are frozen on it: without conversations:read, no subscription to message.* events; without contacts:read, prospects' contact details are removed from deliveries. An endpoint added in Lidmeo receives everything your account reads, contact details and message texts included; to restrict it, create it through the API with a key that has only the scopes you need.
  • Changing the address (url) of an existing endpoint needs every read scope frozen on it: otherwise 403 insufficient_scope, which names the missing ones.
  • An endpoint created by an OAuth connection lives with it: when the connection is revoked (or the person loses access), the endpoint is disabled with disabled_reason: "revoked" and stops receiving. It cannot be enabled again as is (409 conflict): only with a new URL, and it then belongs to whoever gave it.
  • disabled_reason says why an endpoint is disabled: manual (by you), failing (too many failures, see retries) or revoked.
  • An account has at most 16 endpoints. Those of the test account are created with a test key.

What you receive

POST /webhooks/lidmeo HTTP/1.1
Host: example.com
Content-Type: application/json
User-Agent: Lidmeo-Webhooks/1.0
webhook-id: evt_1Z8nR4yTu6Qe
webhook-timestamp: 1790845951
webhook-signature: v1,K5oZfzN95Z9UVu1EsfQmfVNQhnkZ2pj9o9NDN/H/pI4=
{
  "id": "evt_1Z8nR4yTu6Qe",
  "object": "event",
  "type": "invitation.accepted",
  "timestamp": "2026-10-01T09:12:31.000Z",
  "api_version": "2026-10-01",
  "livemode": true,
  "account": "acct_1J4kQ8sLr2Xw",
  "data": {
    "object": {
      "id": "pros_1Hq3ZtV9kWmA",
      "object": "prospect",
      "livemode": true,
      "account": "acct_1J4kQ8sLr2Xw",
      "campaign": "cmp_1T7pLx2Nq8Rv",
      "created_at": "2026-09-25T09:12:31.000Z",
      "updated_at": "2026-10-01T09:12:31.000Z",
      "origin": "lidmeo",
      "first_name": "Camille",
      "last_name": "Exemple",
      "full_name": "Camille Exemple",
      "headline": "Directrice commerciale chez Exemple SAS",
      "title": "Directrice commerciale",
      "company": { "name": "Exemple SAS", "size": "51-200", "industry": "Logiciels" },
      "location": { "label": "Lyon, Auvergne-Rhône-Alpes, France", "country": "FR", "department": "69" },
      "linkedin_url": "https://www.linkedin.com/in/camille-exemple",
      "photo_url": null,
      "why_him": null,
      "activity": null,
      "shared_connections_count": null,
      "pipeline_stage": "connected",
      "crm_stage": null,
      "reminder_on": null,
      "lists": [],
      "invitation": { "sent_at": "2026-09-26T09:12:31.000Z", "accepted_at": "2026-10-01T09:12:31.000Z" },
      "first_message_sent_at": null,
      "replied_at": null,
      "last_activity_at": "2026-10-01T09:12:31.000Z",
      "conversation": "conv_1Ab3Cd5Ef7Gh9Ij1Kl3Mn5o",
      "external_ids": {}
    }
  }
}
  • data.object: the object the event is about, as it was when the event was recorded (a prospect, a message, a campaign…).
  • data.previous_attributes: the previous values, when the event is a change (a stage removed, a campaign paused).
  • webhook-id is the event's id, the same on every attempt.

Most events are recorded within a minute of Lidmeo learning the fact; those of an action taken through the API, usually right after it. timestamp stays the time of the fact.

Lists, notes, "handled" and setting a reminder produce no event (only the reminder's day produces prospect.reminder_due): read the prospect again. prospect.updated only says that contact details were found, or that the prospect was linked to an object of your tools.

Answering

Answer a 2xx code within 15 seconds. Do the work afterwards (a queue, a background job): a long processing makes the delivery fail, and it is then retried. Any other code is a failure: see retries.

Before any processing, verify the signature: see verifying a signature.

Trying

To see the exact shape of a type, call POST /v1/webhook_endpoints/{id}/test with { "type": "…" }; Lidmeo's Envoyer un essai (send a test) button sends a prospect.created. Each test is a sample payload, with fictitious values, data.test: true and an evt_test_… id. A single attempt, outside the event journal. The result (code, duration, excerpt of the response) is in the returned delivery.

Catching up

Your account's event journal starts at its first API request or its first endpoint: nothing older is replayed. It keeps 30 days: GET /v1/events rereads what you might have missed, with the same objects as the webhooks, the most recent first. Read it back to the last id you processed, then process in reverse order.

On this page