Login (may challenge)
POST
https://myagentmail.com/linkedin/sessionsFor agents View as Markdown
Begin a LinkedIn login on behalf of the customer using their email +
password. Returns { ok: true, sessionId } on direct success, or
{ challenge: true, challengeId, challengeType } if LinkedIn requires
a PIN (email/SMS) or mobile-app approval. Follow up with
/sessions/verify (PIN) or /sessions/poll (mobile approval).
Request body
Content-Type: application/json
emailrequired string | format: email |
passwordrequired string | format: password |
labelstring | Optional friendly label for this session. |
Responses
200application/jsonEither a successful login or a challenge requirement.
object | object
401Invalid email/password.
402LinkedIn module not subscribed.
403Session limit reached.
Authentication
Send your API key in the X-API-Key header (or Authorization: Bearer <key>). Any prefix accepted by this endpoint — tk_, wk_, ak_, or sa_ — is documented in the key prefix table.