Resume a paused, scheduled or failed scraper
Restarts a scraper that is:
paused(by you, or automatically when credits ran out);planified: it starts now instead of atplannedStart;- in
errorwithINVALID_COOKIEorRATE_LIMIT, once its LinkedIn account is valid again (refresh it first withPUT /linkedin-scrappers/authes/{id}, or reconnect the campaign account for a classic search).
Other error codes are final: create a new scraper. A segmented extraction restarts with its remaining chunks. For Sales Navigator, a RATE_LIMIT stop is retried automatically about 12 hours later.
Checks: an active subscription or remaining credits; no other running scraper on the same account.
Known issues: the running scraper check can refuse the resume with You already have a running scrap as soon as any other scraper of the workspace is running, even on another account. An unknown id is reported as This scrap is in invalid state (or as the running scraper message), not as not found.
Authorization
apiKey Your 48 character API key, sent as is (a Bearer prefix is tolerated). Create it at https://v3.emelia.io/settings/api.
In: header
Path Parameters
Scrapper id (_id returned by POST /linkedin-scrappers or GET /linkedin-scrappers). 24 hexadecimal characters.
^[0-9a-fA-F]{24}$Response Body
application/json
application/json
application/json
application/json
curl -X PUT "https://example.com/linkedin-scrappers/66f1a2b3c4d5e6f7a8b9c0d1/resume" \ -H "Authorization: YOUR_API_KEY"{ "success": true}