Home
Bulk Jobs

event_bulk_job_success

The Bulk Job Success event occurs when every record of a bulk job was processed.

Request

We send events to your webhook's URL with POST and a JSON body. Events are batched: a request can carry several events of this type. See Receiving Webhooks for batch sizes and retries, and Webhook Event Signatures to verify the request.

Headers

HeaderDescription
x-zinrelo-signatureThe HMAC-SHA512 hex digest of <request body>:<nonce>, computed with the webhook's secret key. See Webhook Event Signatures.
nonceThe Unix time, in milliseconds, at which the request was signed. It's part of the signed message.

Payload

FieldTypeDescription
request_idstringA unique identifier of this webhook request.
total_countintegerThe number of events in the batch (events).
created_datestringWhen the webhook request was created, as MM/DD/YYYY HH:MM:SS.
eventsarray of objectThe events in this batch.
events[].idstringThe unique identifier of the event. Use it to detect events you already processed.
events[].event_typestringThe type of event. One of event_bulk_job_success.
events[].dataobjectThe event's data.
events[].data.job_infoobjectThe result of a bulk job.
events[].data.job_info.job_idstringThe identifier of the bulk job.
events[].data.job_info.schema_slugstringThe schema the job's records were written to.
events[].data.job_info.actionstringWhat the job did with its records. One of create.
events[].data.job_info.payload_typestringHow the job's records were sent. One of json, csv, url.
events[].data.job_info.result_file_urls (optional)array of stringLinks to the files listing the result of each row (index, id and error) of csv and url jobs. Empty for json jobs, whose results are returned by the job itself.
events[].data.job_info.statusstringsuccess when every record was processed, failure when at least one record had an error. One of success, failure.
events[].data.job_info.started_atstring (date-time)When the job started, in ISO 8601.
events[].data.job_info.completed_atstring (date-time)When the job completed, in ISO 8601.

Example

{
  "request_id": "6a0f2c1e4f8f0345970b6d96",
  "total_count": 1,
  "events": [
    {
      "id": "6a0f2c1e4f8f0345970b6d99",
      "event_type": "event_bulk_job_success",
      "data": {
        "job_info": {
          "job_id": "6f1c2b7e-3f5a-4c1d-9b2e-0a8d7c6e5f41",
          "schema_slug": "purchases",
          "action": "create",
          "payload_type": "csv",
          "result_file_urls": [
            "https://example.com/jobs/6f1c2b7e/results_1.csv"
          ],
          "status": "success",
          "started_at": "2026-07-17T12:00:00+00:00",
          "completed_at": "2026-07-17T12:00:05+00:00"
        }
      }
    }
  ],
  "created_date": "07/17/2026 12:00:05"
}

Responses

StatusDescription
200Acknowledges receipt of the events. Return 200 as soon as you receive the request and process the events afterwards, so the request doesn't time out.
OtherAny status code other than 200 is a failure: the request is sent again every 5 minutes until your endpoint returns 200 or the maximum number of attempts (5 by default) is reached. Your Customer Success Manager can change these settings.