Error codes
Every error code of the API, what it means and what to do.
Every error is an RFC 9457 problem (application/problem+json): type (this page's address), title, status, detail (French or English per Accept-Language), a STABLE code and the request_id. A program branches on code, never on the text.
account_required
HTTP 400 · Account required
An agency key must name the target account with the Lidmeo-Account header (see GET /v1/accounts).
What to do. An agency key or connection names the target account: add the Lidmeo-Account: acct_… header.
invalid_api_version
HTTP 400 · Invalid API version
The Lidmeo-Version header does not name a known version.
What to do. Send a known version in Lidmeo-Version (or none: the latest).
invalid_json
HTTP 400 · Invalid JSON
The request body is not valid JSON.
What to do. Send a valid JSON body, with Content-Type: application/json.
invalid_request
HTTP 400 · Invalid request
The request is not valid. Field details are in "errors".
What to do. Fix the request: errors says which field and why (unknown_parameter: a parameter the route does not know, never ignored).
test_mode_only
HTTP 400 · Test mode only
This action only exists in test mode (lid_test_… key).
What to do. This operation exists in test mode only: use a lid_test_… key.
api_key_expired
HTTP 401 · API key expired
This API key has expired. Create a new one from the "Assistant IA et intégrations" page (AI assistant and integrations), "Pour les développeurs" section (for developers).
What to do. Check the key or token (Authorization: Bearer … header).
api_key_revoked
HTTP 401 · API key revoked
This API key has been revoked. Create a new one from the "Assistant IA et intégrations" page (AI assistant and integrations), "Pour les développeurs" section (for developers).
What to do. Check the key or token (Authorization: Bearer … header).
invalid_api_key
HTTP 401 · Invalid API key
This API key does not exist or was copied incorrectly.
What to do. Check the key or token (Authorization: Bearer … header).
invalid_token
HTTP 401 · Invalid token
This token is no longer valid. Reconnect the application.
What to do. Check the key or token (Authorization: Bearer … header).
unauthorized
HTTP 401 · Unauthorized
Authentication required: send an API key or a token in the Authorization header (Bearer).
What to do. Check the key or token (Authorization: Bearer … header).
insufficient_credits
HTTP 402 · Insufficient credits
The credit balance is not enough: nothing was launched.
What to do. The balance does not cover the lookup (cost, balance, count): top up your credits in Lidmeo, then launch again.
account_not_found
HTTP 403 · Account not accessible
This account does not exist or does not belong to your agency.
What to do. The account named (Lidmeo-Account) does not belong to this key or agency: check its id.
forbidden
HTTP 403 · Forbidden
This action is not allowed on this account.
What to do. This action is not allowed for this key or person (for example a read-only account view).
insufficient_scope
HTTP 403 · Insufficient scope
This key or connection does not have the required permission.
What to do. Give the key or connection the missing scope (required_scopes field).
ip_not_allowed
HTTP 403 · IP address not allowed
This key does not accept requests from this IP address.
What to do. Call from an IP address allowed on the key, or widen the list in Lidmeo.
person_required
HTTP 403 · Person required
This action belongs to a person: it is done with an OAuth connection, or a key created by that person.
What to do. Read the detail and the code.
subscription_inactive
HTTP 403 · Subscription inactive
This account's subscription is no longer active.
What to do. The account's subscription is no longer active: nothing can be read or written until it resumes.
not_found
HTTP 404 · Not found
This object does not exist on this account.
What to do. Check the id: it does not exist on this account (or in this mode, live or test).
method_not_allowed
HTTP 405 · Method not allowed
This HTTP method does not exist on this resource.
What to do. The route exists with another method: the Allow header gives it.
action_refused
HTTP 409 · Action refused
Lidmeo refused this action in the account's current state: the exact reason is in "reason", what to do in "detail".
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
already_connected
HTTP 409 · Already connected
This person is already one of your connections: no invitation is sent.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
already_invited
HTTP 409 · Already invited
An invitation was already sent to this person.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
already_scheduled
HTTP 409 · Already scheduled
This message is already scheduled: it will leave on its own.
What to do. It is already on its way (requested at requested_at): do not ask again.
already_sent
HTTP 409 · Already sent
This message was already sent.
What to do. It already left: read the prospect or the conversation.
campaign_limit_reached
HTTP 409 · Campaign limit reached
The account's plan does not allow one more active campaign: pause one, or change plans.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
conflict
HTTP 409 · Conflict
The object's state does not allow this action.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
connection_cap_reached
HTTP 409 · Daily action limit of this key
This key or connection reached its daily limit of send actions: nothing was sent. Resume tomorrow, or from Lidmeo.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
contacts_campaign
HTTP 409 · Contacts campaign
This campaign is built from prospects the account already has (CRM or a file): it has no target.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
daily_cap_reached
HTTP 409 · Daily cap reached
Today's sending limit is reached: nothing was sent.
What to do. Today's limit is reached: nothing was sent. Retry at next_slot_at (the limit is in cap when it is specific to the API).
delivery_in_progress
HTTP 409 · Delivery in progress
This delivery is being sent right now. Retry in a moment.
What to do. This delivery is leaving right now: read it again in a moment.
duplicate
HTTP 409 · Duplicate
This person is already contacted through another prospect of the account: this one is set aside.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
email_conversation
HTTP 409 · E-mail conversation
This conversation takes place by e-mail: prepare the answer with POST /v1/prospects/{id}/drafts (channel "email"), then confirm it with POST /v1/previews/{id}/confirm.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
external_id_in_use
HTTP 409 · External id in use
This external id is already linked to another prospect of the account.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
followup_blocked
HTTP 409 · Follow-up not possible
The follow-up is no longer possible for this prospect (the reason is in "blocker").
What to do. The follow-up is no longer possible (blocker says why: reply, stage, already followed up…): read the prospect again.
idempotency_key_in_use
HTTP 409 · Idempotency key in use
A request with this Idempotency-Key is still in progress. Retry in a moment.
What to do. The first request with this key is still running: wait for its answer, then replay with the same key.
import_in_progress
HTTP 409 · Import in progress
An import is already running on this account. Retry in a moment.
What to do. Another import is running on this account: retry in a few seconds (the same idempotency key stays valid).
launch_required
HTTP 409 · Launch required
This campaign has never been launched: its first launch happens in Lidmeo, or from the AI connector on a confirmed preview. The API pauses and resumes campaigns that have already run.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
limit_reached
HTTP 409 · Limit reached
The account has reached the maximum for this object.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
linkedin_disconnected
HTTP 409 · LinkedIn disconnected
No LinkedIn account is connected: nothing can be sent.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
name_taken
HTTP 409 · Name taken
This name is already taken on this account.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
no_conversation
HTTP 409 · No conversation
No LinkedIn conversation with this prospect in Lidmeo: the message has to be sent from LinkedIn.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
no_message
HTTP 409 · No message
The first message is not written yet: pass the text.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
not_approvable
HTTP 409 · Not approvable
This prospect is not waiting for this approval (nothing waiting, campaign in automatic sending, or already approved for the next slot).
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
not_removable
HTTP 409 · Not removable
Only a prospect not contacted yet can be set aside (planned, awaiting approval, invitation accepted without a message), or an imported prospect; never while it is being sent.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
not_replied
HTTP 409 · Not a reply
This contact has not replied to you: a reply is only written to someone who wrote. Send a follow-up (kind "follow_up"), with its rules.
What to do. This contact did not reply: send a follow-up (kind: "follow_up"), with its rules.
not_sendable
HTTP 409 · Not sendable
This prospect cannot receive this send: it is set aside (the reason is in "reason").
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
preview_already_used
HTTP 409 · Preview already used
This preview was already confirmed: nothing was sent again. Read what was done before preparing a new one.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
preview_expired
HTTP 409 · Preview expired
This preview has expired (15 minutes): nothing was done. Prepare a new one.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
preview_other_connection
HTTP 409 · Preview of another connection
This preview was prepared by another key or connection: it can only be confirmed from that one.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
profile_unknown
HTTP 409 · Profile unknown
This prospect's LinkedIn profile is unknown: approve it from Lidmeo.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
prospecting_not_configured
HTTP 409 · Prospecting not configured
Prospecting is not set up on this account: nothing can be sent.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
send_in_progress
HTTP 409 · Send in progress
Another send of this account is in progress: nothing was sent. Retry in a moment.
What to do. Another send of this account is leaving right now: nothing was sent, retry in a moment (the same key stays valid).
sends_paused
HTTP 409 · Sends paused
The LinkedIn account's sends are paused to protect it: nothing was sent.
What to do. Lidmeo paused sends to protect the LinkedIn account: nothing was sent, resuming at resumes_at.
stage_not_available
HTTP 409 · Stage not available
A stage only applies to a prospect who already received a first message, or to an imported prospect.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
suppressed
HTTP 409 · Do not contact
This prospect is on your "do not contact" list: nothing is sent, the prospect is set aside.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
switch_offer_pending
HTTP 409 · Switch offer pending
This campaign has a pending offer to switch to the new search: decide it in Lidmeo before changing its target.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
test_reset_in_progress
HTTP 409 · Test reset in progress
The test account is being filled: retry in a moment.
What to do. The test account reset is running: retry in a moment.
webhook_endpoint_disabled
HTTP 409 · Webhook endpoint disabled
This webhook endpoint is disabled: enable it again (status: enabled) before sending anything to it.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
whatsapp_conversation
HTTP 409 · WhatsApp conversation
This conversation takes place on WhatsApp: prepare the answer with POST /v1/prospects/{id}/drafts (channel "whatsapp"), then confirm it with POST /v1/previews/{id}/confirm.
What to do. The current state does not allow it: read the object again, then decide. Do not retry in a loop.
idempotency_key_mismatch
HTTP 422 · Idempotency key reused
This Idempotency-Key was already used for a different request.
What to do. This key was used for a DIFFERENT request: take a new Idempotency-Key for a new operation.
rate_limited
HTTP 429 · Too many requests
Too many requests. Retry after the delay given by Retry-After.
What to do. Wait for the Retry-After delay (one second after a burst), then retry.
internal_error
HTTP 500 · Internal error
An unexpected error occurred. The request id lets support find it.
What to do. Nothing you can fix: retry later, with the same Idempotency-Key; if it lasts, give the request_id to support.
send_failed
HTTP 502 · Send failed
LinkedIn did not accept the send. Read the prospect again before any new attempt, never in a loop: the same Idempotency-Key replays this response without sending anything again.
What to do. Do not retry automatically (the SDKs do not): read the prospect again, check the LinkedIn account in Lidmeo, then try again later, once, with a new Idempotency-Key.
sends_disabled
HTTP 503 · Sends disabled
Sends through the API are temporarily switched off: nothing was sent. Retry later.
What to do. Sends through the API are switched off by Lidmeo for now: do not retry in a loop, reads stay open.
service_unavailable
HTTP 503 · Service unavailable
This service is temporarily unavailable. Retry in a few minutes.
What to do. A read failed on our side: retry with a growing delay. After a write, read the object again before retrying without an Idempotency-Key (applied says what was done).