LidmeoDevelopers

Test mode

A fictitious account to try everything: simulated sends, acceptances and replies within minutes, nothing ever leaves.

Every Lidmeo account has a test account, created on first use. A lid_test_… key, or an OAuth connection where the user chose Test account when connecting, works on it. The same code then runs live: only the key changes.

What it holds

Sample prospects at every status (planned or awaiting approval, invitation sent, invitation accepted, message sent, replied, imported prospects), their conversations, a sample campaign, CRM stages (including "RDV pris", set on a prospect), a reminder for today, the "Prospects chauds" list and fictitious contact details. The test account follows your real account's send mode (automatic or manual).

What happens there

Nothing leaves for LinkedIn or by e-mail: a simulator brings what you send to life. Sample prospects themselves stay at their stage.

  • An approved invitation is accepted a few minutes later by about six prospects out of ten.
  • In automatic mode, the first message leaves a minute later; in manual mode, it waits for your approval.
  • About four contacted prospects out of ten reply, a few minutes later.
  • The outcome is the same on every try, for a given account and prospect: a test that passes always passes.
  • Each step sets the same dates as live: events are recorded the same way, with livemode: false.

To skip the wait, force an acceptance or a reply on a prospect at the right stage:

curl https://api.lidmeo.com/v1/test/simulate \
  -H "Authorization: Bearer $LIDMEO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "prospect": "pros_…", "event": "reply" }'

event is invitation_accepted (an invited prospect) or reply (a contacted prospect).

What differs from live

  • Account objects carry livemode: false. API objects carry no link to the Lidmeo screen; in an AI assistant, these links are null in test mode, because the screen only shows the real account.
  • account always designates your real account; in test mode, its test account answers.
  • Contact lookups return fictitious values (.example domain, numbers reserved for fiction) and use no credits.
  • Proposed follow-ups are a sample text, with the contact's first name.
  • Copilote is simulated: its reads return a sample space (agent, replies, goals, calendar), "Tester l'agent" returns a fixed sample reply, and every write or send answers 409 action_refused (reason: test_mode) without saving anything.
  • "Do not contact", approvals and refusals follow the same rules as live.
  • Rate limits have their own counters, and the event journal is separate.
  • The test account's webhook endpoints are managed through the API (webhooks:manage); Lidmeo's Assistant IA et intégrations (AI assistant and integrations) page shows the live ones.

Resetting

curl -X POST https://api.lidmeo.com/v1/test/reset \
  -H "Authorization: Bearer $LIDMEO_API_KEY"

Everything you did in test is erased (added prospects, conversations, lists, notes, stages, "Do not contact", imports), then the samples come back. One reset at a time: meanwhile, another one answers 409 test_reset_in_progress. The same button exists in Lidmeo, on the Assistant IA et intégrations page, Pour les développeurs (for developers), Compte de test (test account) section.

The /v1/test/… operations only exist in test mode: with a live key, they answer 400 test_mode_only.

On this page