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

## 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 failed_due_to_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 api_key. Webhook callbacks fire only for successful jobs by default; set expectUnsuccessReport to true to also receive failed job payloads (failReason values like failed_due_to_timeout). 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.
