Create Transactions in Bulk (Beta)
POST/partner/transactions/_bulk
Important notes:
- Do not submit authorizations as purchases.
- The amount for a Purchase transaction should not include cashback if it was part of the transaction.
- Transactions must be uploaded within 7 days of when they take place.
- Triple leverages these fields to generate rewards on the transaction
- card_bin
- card_last_4
- processor_mid
- processor_mid_type
- merchant_address.postal_code
- merchant_address.country_subdivision_code
- merchant_category_code
Note: Triple will make every effort to match transactions with any information that is submitted. However, without the above fields, we make no guarantee that a transaction will be matched and/or submitted for a cardholder reward or marketing fee.
This endpoint provides significant performance advantages, over POSTing single transactions, when creating large numbers of transactions. The behavior of the two endpoints is nearly the same except for some minor differences in how errors are handled.
You should check the result_type
of the response to handle errors for
individual items. If the top-level request returns a Client Error response
(response codes 400-499), no transactions from the batch were created.
This endpoint is currently rate limited at 100 requests per minute.
Request
Responses
- 201
- 400
- 403
- 409
- 415
- 422
- 429
- 500
- 501
- 503
Transactions Bulk Result
TripleBadRequestError
TripleNotAuthenticatedError
TripleIntegrityError
TripleUnsupportedMediaType
TripleUnprocessableEntity
TripleTooManyRequests
Response Headers
The minimum number of seconds to wait before retrying the request.
Request limit per minute.
The number of requests left for the time window.
The time at which the rate limit resets, specified in UTC epoch time (in seconds).
TripleInternalServerError
TripleNotImplementedError
TripleServiceUnavailable