Connect a LinkedIn account for scraping (session cookies)
Connects a LinkedIn account for Sales Navigator scraping by sending the cookies of a browser session where the user is logged in to LinkedIn and Sales Navigator. No password is involved. The Emelia browser extension does this for you; use this route to automate it.
li_at is required. Strongly recommended: li_a (Sales Navigator session), ua (user agent of the browser the cookies come from), additionnalsCookie (the other linkedin.com cookies, as objects { name, value, domain }), viewport (that browser window size) and country (ISO alpha-2 code: Emelia browses LinkedIn through a proxy located in this country; default the workspace country, then FR).
Returns authId, to use in authes of POST /linkedin-scrappers. The same li_at cannot be registered twice. When a session expires, update the existing account with PUT /linkedin-scrappers/authes/{id} instead of creating a new one.
Emelia stores these cookies and refreshes them after each scraping session. There is currently no API route to remove a connected scraping account.
Pitfalls: jsessionid is accepted but ignored (send JSESSIONID inside additionnalsCookie). Cookies sent as "name=value" strings are accepted but not used by the Sales Navigator scraper: send objects. Fields not described here are reserved for Emelia apps; any other field is rejected.
Request
- Base URL: https://api.emelia.io
- URL: https://api.emelia.io/linkedin-scrappers/authes
- Auth: API key in header Authorization
Request body
Response
Account connected.
Changes
No recorded changes to this operation across all 1 revision of this API.