When creating tasks, you can provide aDocumentation Index
Fetch the complete documentation index at: https://docs.unifically.com/llms.txt
Use this file to discover all available pages before exploring further.
callback_url to receive webhook notifications when the task completes or fails. This avoids polling and lets you integrate with your backend asynchronously.
Enabling Callbacks
Passcallback_url at the top level of your request (outside the input object):
Optional webhook URL. When provided, the API sends a POST request to this URL when the task completes or fails.
Webhook Payload Format
The API sends a POST request to yourcallback_url with a JSON body. The payload structure depends on whether the task succeeded or failed.
Success Payload
When the task completes successfully:data object contains the output URL(s) based on the task type:
| Task Type | Output Field | Description |
|---|---|---|
| Video | video_url | URL to the generated video |
| Image | image_url | URL to the generated image |
| Audio | audio_url | URL to the generated audio |
image_urls or audio_urls as arrays.
Failure Payload
When the task fails:| Field | Type | Description |
|---|---|---|
task_id | string | The task ID |
status | string | "failed" |
error_message | string | Human-readable error description |
Request Details
- Method: POST
- Content-Type:
application/json - Body: JSON payload as shown above
Best Practices
- Respond quickly — Return a 2xx status code within a few seconds to acknowledge receipt. Process the payload asynchronously if needed.
- Verify webhook origin — Use HTTPS and consider validating requests (e.g., via a shared secret or signature if supported in the future).
- Handle duplicates — The same webhook may be delivered more than once; use
task_idto deduplicate. - Validate URLs — Ensure your callback URL is publicly accessible and accepts POST requests.
