Webhook events for task run completions
parallel-beta:
webhook-2025-08-12
header when using the Task API. Parameter | Type | Required | Description |
---|---|---|---|
url | string | Yes | Your webhook endpoint URL. Can be any domain. |
event_types | array[string] | Yes | Currently only ["task_run.status"] is supported. |
task_run.status
event on task run completions.
When a task run finishes, either with a success or a failure, we will send a
POST
request to your configured webhook endpoint.
webhook-id
: Unique identifier for each webhook eventwebhook-timestamp
: Unix timestamp in secondswebhook-signature
: One or more versioned signatures, e.g. v1,<base64 signature> v1,<base64 signature>
webhook-signature
header can include multiple entries separated by spaces; you should check each entry
until you find one which matches the signature generated by your webhook secret.
Under normal circumstances there will only be one signature in the webhook-signature
header, but there may be multiple if you rotate your webhook secret without immediately
expiring the old secrets.
timestamp
: ISO 8601 timestamp of when the event occurredtype
: Event type (currently only task_run.status
is supported)data
: Event-specific payload. For the ‘task_run.status’ event, it is the complete Task Run objectv1,<base64 signature>
where <base64 signature>
is computed over the payload below.
<webhook-id>
: The value of the webhook-id
header<webhook-timestamp>
: The value of the webhook-timestamp
header<payload>
: The exact JSON body of the webhook requestwebhook-signature
header uses space-delimited signatures; check each signature until one matches.
Here’s how ou may verify the signature: