Home
Imports

event_transaction_import_success

The Transaction Import Success event occurs when every row of a transaction import (batch) file 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_transaction_import_success.
events[].dataobjectThe event's data.
events[].data.file_infoobjectThe result of processing an import file.
events[].data.file_info.file_namestringThe name of the imported file.
events[].data.file_info.statusstringsuccess when every row was imported, failure when at least one row had an error. One of success, failure.
events[].data.file_info.total_countintegerThe number of rows in the file.
events[].data.file_info.success_countintegerThe number of rows imported successfully.
events[].data.file_info.error_countintegerThe number of rows that couldn't be imported.
events[].data.file_info.inserted_count (optional)integerMember imports only. The number of members created.
events[].data.file_info.updated_count (optional)integerMember imports only. The number of members updated.
events[].data.file_info.erroneous_file_url (optional)string or nullA link to a file listing the rows that couldn't be imported and why, null when there were none.
events[].data.file_info.processed_atstringWhen the file finished processing, in UTC, as MM/DD/YYYY HH:MM:SS.

Example

{
  "request_id": "6a0f2c1e4f8f0345970b6d96",
  "total_count": 1,
  "events": [
    {
      "id": "6a0f2c1e4f8f0345970b6d99",
      "event_type": "event_transaction_import_success",
      "data": {
        "file_info": {
          "file_name": "transactions_20260101.csv",
          "status": "success",
          "total_count": 250,
          "success_count": 250,
          "error_count": 0,
          "erroneous_file_url": null,
          "processed_at": "01/01/2026 10:15:00"
        }
      }
    }
  ],
  "created_date": "01/01/2026 10:15:01"
}

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.