LidmeoDevelopers

Support

Getting help fast: what to send us, and what never to send.

Write to contact@lidmeo.com. From Lidmeo, the Support bubble ("Équipe" tab) also puts you in touch with the team.

For a quick answer

  • The Request-Id of the response that surprises you (Request-Id header, or request_id in an error): it leads us straight to the request.
  • The account (acct_…, returned by GET /v1/me) and the mode, live or test.
  • The time of the request, and the operation (POST /v1/prospects/{id}/approve_invitation…).
  • For a webhook: the endpoint's id (whe_…) and the delivery's (whd_…).

Never send

No API key, no token, no webhook secret: nobody at Lidmeo will ask you for them. If one of them has circulated, revoke or change it in Lidmeo, on the "Assistant IA et intégrations" (AI assistant and integrations) page.

When the service has a problem

A 503 service_unavailable response says the platform is temporarily unavailable. Most often nothing was done; but a write in several steps (PATCH /v1/prospects/{id}) may have been partly applied, and applied says what was. After a write, read the object again before retrying: a 503 response is not kept under the Idempotency-Key, the same key does the action again. The SDKs retry on their own. Pending webhooks leave when service resumes, on their schedule.

An idea, something missing

An operation you miss, an event that would help your integration: write to us, with what you are trying to do. The documentation and the API evolve with your needs.

On this page