Skip to main content

Event Types

Use this page to map webhook event names to job outcomes.

bulkfill.export_job.completed​

Doqlo sends this event when the export job reaches completed.

What the payload includes:

  • event
  • event_id
  • occurred_at
  • job_id
  • status
  • idempotency_key
  • request_id
  • reused_result
  • optional delivery_id
  • download_url
  • download_expires_at

Use it when you need to start download or downstream processing after a successful export.

completed means a ZIP artifact exists. It does not mean every requested row produced a perfect PDF. A completed job can still include partial or failed rows in manifest.json.

bulkfill.export_job.failed​

Doqlo sends this event when the export job reaches failed.

What the payload includes:

  • event
  • event_id
  • occurred_at
  • job_id
  • status
  • idempotency_key
  • request_id
  • reused_result
  • error_code
  • error_message
  • optional error_details when the failure class is threshold_failed

Use it when you need to log a terminal failure, retry from your own system, or route the job for investigation.

Threshold-failed jobs do not include download_url because no ZIP artifact is delivered.

Relationship To Job States​

  • queued and processing do not emit webhook events.
  • Only terminal states emit webhooks.
  • Webhook mode does not create a different state machine. It only changes how terminal results are delivered.