Skip to main content

What are Webhooks?

Webhooks allow you to receive real-time notifications when your video generation or export jobs complete. Instead of polling the status endpoint repeatedly, Hoox will send an HTTP POST request to your specified URL when the job finishes.

Benefits

Real-time Updates

Get notified immediately when jobs complete, no need to poll

Reduced API Calls

Save on rate limits by eliminating status polling

Better UX

Provide instant feedback to your users

Automation

Trigger downstream processes automatically

How Webhooks Work

1

Configure Webhook URL

Include a webhook_url in your generation or export request
2

Job Processing

Hoox processes your video generation or export job
3

Webhook Delivery

When the job completes (success or failure), Hoox sends a POST request to your URL
4

Acknowledgment

Your endpoint should respond with a 200 status code to confirm receipt

Webhook Payload

All webhooks include a task field to identify the type of operation. This helps you route and process webhooks correctly.

Payload Structure by Task Type

Fieldvideo_generatevideo_exportavatar_createavatar_edit
task
job_id
avatar_id
look_id
status
result
error✅ (on failure)✅ (on failure)✅ (on failure)✅ (on failure)
Key differences:
  • Video operations use job_id (the Trigger.dev run ID)
  • Avatar operations use avatar_id and look_id instead
  • Always check the task field to determine how to process the webhook

Successful Generation

Failed Generation

Setting Up Webhooks

1. Create an Endpoint

Your webhook endpoint should:
  • Accept POST requests
  • Respond with 200 status code
  • Process the payload asynchronously if needed

2. Use in API Calls

Include your webhook URL when starting jobs:

Security Considerations

1. Validate Requests

Verify that webhook requests are coming from Hoox:

2. Use HTTPS

Always use HTTPS URLs for your webhook endpoints to ensure data is encrypted in transit.

3. Implement Idempotency

Handle duplicate webhook deliveries gracefully:

Retry Behavior

Hoox will retry webhook deliveries if your endpoint:
  • Returns a non-2xx status code
  • Times out (after 10 seconds)
  • Is unreachable
Retry Schedule:
  • 1st retry: After 1 second
  • 2nd retry: After 2 seconds
  • 3rd retry: After 4 seconds
  • Maximum: 3 retry attempts
If all retries fail, the webhook will be discarded. Ensure your endpoint is reliable and responds quickly.

Testing Webhooks

1. Use ngrok for Local Development

2. Webhook Testing Tools

  • RequestBin: Create temporary endpoints to inspect payloads
  • Webhook.site: Test and debug webhook deliveries
  • Postman: Mock webhook requests for testing

3. Test Endpoint

Create a simple test endpoint to verify webhook delivery:

Best Practices

  • Always check the task field first to route webhooks correctly
  • Use different handlers for different task types
  • Validate that required fields exist based on task type
  • For avatars: use avatar_id and look_id
  • For videos: use job_id
  • Respond with 200 status as quickly as possible
  • Process heavy operations asynchronously
  • Use queues for complex workflows
  • Log all webhook deliveries for debugging
  • Handle malformed payloads gracefully
  • Implement monitoring and alerting
  • Check for required fields based on task type
  • Use load balancers for high-volume webhooks
  • Implement rate limiting on your endpoint
  • Consider using message queues for processing

Common Issues

IssueCauseSolution
Webhooks not receivedEndpoint unreachableCheck URL and firewall settings
Duplicate processingNo idempotency checkImplement unique ID tracking (job_id or avatar_id:look_id)
Slow processingHeavy operations in handlerMove to background jobs
Missing webhooksEndpoint returning errorsFix endpoint logic and status codes
Wrong task routingNot checking task fieldAlways check the task field first
Missing IDsAccessing wrong fieldsUse job_id for videos, avatar_id/look_id for avatars
Always test your webhook endpoints thoroughly before using them in production.