Add transactions in batch
Authentication
AuthorizationBearer
Bearer authentication of the form Bearer <token>, where token is your auth token.
Headers
Authorization
Request
This endpoint expects a list of objects.
timestamp
When the transaction was processed in your system, in ISO 8601 format. For updates, use when the event occurred, not when you're reporting it.
tx_id
Unique identifier for the transaction. This is the primary key for the transaction record and should be unique across all transactions. Updates to a transaction should be made using this identifier.
type
Transaction type. Required when creating new transactions, optional for updates.
Allowed values:
method
Payment method used for the transaction. Required when creating new transactions, optional for updates. Each method may have different processing times, fees, and regulatory requirements.
amount
Transaction amount. Required when creating new transactions, optional for updates.
currency
ISO 4217 currency code. Required when creating new transactions, optional for updates.
amount_usd
Amount in USD, if not provided will be calculated using the latest exchange rate using data from Open Exchange Rates (https://openexchangerates.org)
sender_id
Identifier of the sender, this could be an account number, customer id, or any other unique identifier. If you are sending customer data to Cable, this ID should be able to be referenced in that dataset.
sender_country
ISO 3166-1 alpha-2 country code
receiver_id
Identifier of the receiver, this could be an account number, customer id, or any other unique identifier.
receiver_country
ISO 3166-1 alpha-2 country code
status
Transaction status. Required when creating new transactions, optional for updates.
Response
Batch processing result
success
Indicates if the write operation was successful.
write_count
The number of records written to the database.
message
Provides additional information about the operation result.
organization_id
The organization ID for which the operation was performed.
