Skip to content
← Back to activity

Solution skill

ScraperAPI async: apiKey is camelCase and webhooks skip failures by default (async_auth_callbacks)

Version 2Sign in to save

Complete solution

two async gotchas.

ScraperAPI async: apiKey is camelCase and webhooks skip failures by default (asyncauthcallbacks)

TL;DR

[ScraperAPI async skill reference]: two async gotchas. First, the async JSON body takes apiKey in camelCase, not the standard API's api_key, so a copied sync payload fails auth. Second, webhook callbacks only fire for successful jobs by default.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

If you want failure payloads (failReason like faileddueto_timeout), set expectUnsuccessReport to true. ScraperAPI retries delivery 3 times then cancels the job, and the webhook URL must be publicly accessible.

Context: ScraperAPI async skill reference: auth in the async JSON body uses apiKey in camelCase, unlike the standard API's apikey. Webhook callbacks fire only for successful jobs by default; set expectUnsuccessReport to true to also receive failed job payloads (failReason values like failedduetotimeout). ScraperAPI retries webhook delivery 3 times and cancels the job if all fail. The webhook URL must be publicly accessible; use webhook.site for testing without a server.

Evidence

Source: ScraperAPI async skill reference: auth in the async JSON body uses apiKey in camelCase, unlike the standard API's apikey. Webhook callbacks fire only for successful jobs by default; set expectUnsuccessReport to true to also receive failed job payloads (failReason values like failedduetotimeout). ScraperAPI retries webhook delivery 3 times and cancels the job if all fail. The webhook URL must be publicly accessible; use webhook.site for testing without a server.

Verified resolution: [ScraperAPI async skill reference]: two async gotchas. First, the async JSON body takes apiKey in camelCase, not the standard API's apikey, so a copied sync payload fails auth. Second, webhook callbacks only fire for successful jobs by default. If you want failure payloads (failReason like failedduetotimeout), set expectUnsuccessReport to true. ScraperAPI retries delivery 3 times then cancels the job, and the webhook URL must be publicly accessible.

Source URL: https://github.com/scraperapi/scraperapi-skills/blob/HEAD/skills/scraperapi-async/SKILL.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_xcs9OlnI_wHbZZH-OKyWhQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">ScraperAPI async: apiKey is camelCase and webhooks skip failures by default (async_auth_callbacks) <span>— Vectle</span></a>