Scrapfly's webhook feature is ideal for managing long-running scrape tasks asynchronously. When webhook is specified through the webhook_name parameter, Scrapfly will call your HTTP endpoint with the scrape response as soon as the scrape is done.

To start using webhooks first one must be created using webhook web interface.

webhook management page

Then the webhook scrape parameter can be used with the created webhook's name (e.g. webhook_name=example) to enable webhook callbacks per scrape request basis.

The body sent to your endpoint is the same as a regular API scrape response, plus webhook information in the context part.

The webhook execution information can be found in the webhook tab of each scrape log page in the monitoring dashboard:

webhook status report on monitoring log page
Webhook Queue Size

The webhook queue size indicates the maximum number of queued webhooks that can be scheduled. After the scraping process is completed and your application is notified, the queue size is reduced. This allows you to schedule additional scrapes beyond the concurrency limit of your subscription. The scheduler will handle this and ensure that your concurrency limit is met.

500 500 2,000 5,000 10,000

See in Your Dashboard


Webhooks are scoped per scrapfly projects and environments. Make sure to create a webhook for each of your project and environment (test/live).


Webhook can be used for multiple purpose, in context of Scraper API, to assert you received a scrape, you must check the header X-Scrapfly-Webhook-Resource-Type and check the value is scrape

To enable webhook callbacks, all you need to do is specify the webhook_name parameter in your scrape requests. Then, Scrapfly will immediately return a promise response and call your webhook endpoint as soon as the scrape is done.

Note that your webhook has to be configured to respond to 2xx response code for webhook to be considered a success. The 3xx redirect responses will be followed and response codes 4xx and 5xx are considered failures and will be retried as per the retry policy.

The below examples assume you have a webhook named example registered. You can create a webhook named "example" via the web dashboard.
var options = {
  method: "GET",

try {
  const response = await fetch("https://api.scrapfly.io/scrape?webhook_name=example&key=__API_KEY__&url=https%3A%2F%2Fhttpbin.dev%2Fhtml", options);
  if (!response.ok) {
    throw new Error(`HTTP error! status: ${response.status}`);
  const data = await response.json();
} catch (error) {

Example Of Response


When you enqueue a scrape, you receive a unique job uuid response.context.job.uuid, when your webhook will be notified, you will retrieve the processed job id on the response header X-Scrapfly-Webhook-Job-Id or inside the response (same structure as enqueue request response.context.job.uuid) to reconcile it in your system and track it.

Retry Policy

Webhook callbacks are retried if Scrapfly can't notify the endpoint specified in your webhook settings based on this retry policy:

  • 30 seconds
  • 1 minute
  • 5 minutes
  • 30 minutes
  • 1 hour
  • 1 day
If we failed to reach your application more than 100 times in a row, the system automatically disables it, and you will be notified. You can re-enable it from the UI at any point after.


Useful tools to develop locally :


Webhooks are signed using HMAC (Hash-based Message Authentication Code) with the SHA-256 algorithm to ensure the integrity of the webhook content and verify its authenticity. This mechanism helps prevent tampering and ensures that webhook payloads are from trusted sources.

HMAC Overview

HMAC is a cryptographic technique that combines a secret key with a hash function (in this case, SHA-256) to produce a fixed-size hash value known as the HMAC digest. This digest is unique to both the original message and the secret key, providing a secure way to verify the integrity and authenticity of the message.

Signature in HTTP Header

When sending a webhook request, a signature is generated using HMAC-SHA256 and included in the HTTP header X-Scrapfly-Webhook-Signature. This signature is computed based on the webhook payload and a secret key known only to the sender and receiver.

Verification Process

Upon receiving a webhook request, the receiver extracts the payload and computes its own HMAC-SHA256 signature using the same secret key. It then compares this computed signature with the signature provided in the X-Scrapfly-Webhook-Signature header. If the two signatures match, it indicates that the payload has not been tampered with and originates from the expected sender.

Security Considerations

  • Keep Secret Key Secure: The secret key used for HMAC computation should be kept confidential and not exposed publicly.
  • Use HTTPS: Webhook communication should be conducted over HTTPS to ensure data privacy and integrity during transit.
  • Regular Key Rotation: Periodically rotate the secret key used for HMAC computation to enhance security.


Following headers are added :

  • X-Scrapfly-Webhook-Env : Related environment where webhook is triggered
  • X-Scrapfly-Webhook-Project : Related project name
  • X-Scrapfly-Webhook-Signature HMAC SHA-256 Integrity Signature
  • X-Scrapfly-Webhook-Name Name of the webhook
  • X-Scrapfly-Webhook-Resource-Type Resource type
  • X-Scrapfly-Webhook-Job-Id Unique Job Identifier given in the enqueue call

All related errors are listed below. You can see the full description and example of the error response on Errors section of the documentation.

No additional fee applied on usage.