Authentication
API keys for your programs, OAuth for applications acting on behalf of a user.
Every request carries a token in the Authorization header:
Authorization: Bearer lid_live_…Two kinds of tokens: an API key, for your own programs, and an OAuth token, for an application acting on behalf of a Lidmeo user (an AI assistant, a third-party tool).
API keys
| Prefix | Gives access to |
|---|---|
lid_live_… | your account, live |
lid_test_… | your account's test account (nothing ever leaves) |
lid_org_live_… | all the accounts of an agency, live |
lid_org_test_… | an agency's test accounts |
Creating a key: Lidmeo, Assistant IA et intégrations (AI assistant and integrations) page of the Réglages menu, Pour les développeurs (for developers), Clés d'API (API keys) section, Créer une clé (create a key). Choose a name, the Données (Data): Votre compte (réel) (your account, live) or Le compte de test (fictif, rien ne part vers LinkedIn) (the test account, fictitious, nothing leaves for LinkedIn), and the scopes, then Créer la clé (create the key). The key is shown only once: Lidmeo keeps only a fingerprint and cannot give it back to you. An account has at most 20 active keys.
Scopes: a new key gets every scope except the right to send (sends:write), which you tick deliberately. Give each key only the scopes it needs. The list: scopes.
Revoking: the key's Révoquer (revoke) button, in Assistant IA et intégrations, Pour les développeurs. It stops working right away. An exposed key (published in a repository, pasted in a message) must be revoked, then replaced.
Agency keys cannot be created yet from the "Assistant IA et intégrations" page. Until then, an agency gives access to all its accounts through an OAuth connection: see agencies.
A key lives on a server
Never put a key in a web page, a mobile app or a code repository: whoever reads it acts on your account. Keep it in an environment variable or a secret store.
OAuth
For an application acting on behalf of Lidmeo users: each user signs in to Lidmeo, chooses the account and the scopes, and your application receives a token in their name. This is the path Claude, ChatGPT and automation tools take.
| Discovery (RFC 8414) | https://hub.lidmeo.com/.well-known/oauth-authorization-server |
| Authorization | https://hub.lidmeo.com/oauth/authorize |
| Tokens | https://hub.lidmeo.com/oauth/token |
| Dynamic registration (RFC 7591) | https://hub.lidmeo.com/oauth/register |
| Revocation (RFC 7009) | https://hub.lidmeo.com/oauth/revoke |
- Authorization code with PKCE (
code_challenge_method=S256), mandatory, confidential clients included. - The resource (RFC 8707):
resource=https://api.lidmeo.comfor the API (the default),https://mcp.lidmeo.com/mcpfor the AI connector. A token is only valid for its resource. - Scopes: the same as for keys, in
scope, separated by spaces. Withoutscope, all are proposed, and the user unticks what they refuse. - Lifetimes: the access token lasts one hour. It comes with a refresh token, valid 60 days, which changes on every use (rotation). Two simultaneous refreshes get the same successor; an already used refresh token that comes back later is taken for a theft and brings the whole connection down.
- Revocation: revoking a token, access or refresh, cuts the whole connection. The user must then connect again.
- The client's identity: a metadata document published at an HTTPS address (your
client_idis then that address), or dynamic registration.
A refused token gets 401 with the WWW-Authenticate header, which points to the protected resource metadata (RFC 9728); a missing scope, 403 with error="insufficient_scope".
The user sees each connected application in Lidmeo, on the Assistant IA et intégrations (AI assistant and integrations) page, Applications connectées (Connected applications) section, and can disconnect it at any time: its tokens are cut within a minute.
Refusals
| Code | When |
|---|---|
401 unauthorized | no token |
401 invalid_api_key | unknown or mistyped key |
401 api_key_revoked, 401 api_key_expired | revoked or expired key |
401 invalid_token | unknown, expired or revoked OAuth token |
403 insufficient_scope | missing scope (required_scopes names it) |
403 subscription_inactive | the account's subscription is stopped |
The detail of each code: errors.