logo
Improvedasync-api

Async API webhook retries, 410 for unavailable results, reference refresh

View as Markdown

Webhooks that return 404 or 410 now get one re-check an hour later instead of fast retries, Get Task can return 410 Gone, and the Async API reference now lists every field the API returns.

Webhooks that return 404 or 410

When your webhook endpoint answers 404 or 410, the Async API no longer burns through the normal retry ladder. The webhook gets one more attempt about an hour later, so an endpoint that is briefly gone during a redeploy still gets its results. If it still answers 404 or 410, the webhook is marked failed. Other failures (timeouts, connection errors, 5xx) are retried as before.

The full delivery rules are now documented under webhook delivery.

410 Gone on Get Task

In rare cases a task still exists but its stored content can no longer be read. Get Task now returns 410 Gone with Task response content is no longer available. for these tasks. Retrying will not bring the content back, so create a new job for that URL. Results are still kept for 3 days after the job is created.

Reference refresh

The Async API reference now matches what the API actually returns and accepts:

  • Task responses list WebhookURL, WebhookStatus, WebhookRequestTime and TraceID.
  • The create-job schema documents the Plugin field, the 1000-target limit and the Timeout / RetryTimeout ranges.
  • List Jobs documents the status, start_from, start_to and sort query parameters in the API schema.

Plugin jobs also gained new keys and stricter up-front validation. See the plugin reference for details.

On this page