12 posts tagged with "TM Trx Batch Upload"

The Batch Upload API is now subject to per-tenant rate limits.

The previously deprecated failed_transaction_modification_ids and progress_percentage fields are no longer returned in the batch status response.

The progress_percentage field in the batch status response has been marked as deprecated and will be removed in a future version.

The failed_transaction_modification_ids field in the batch status response has been marked as deprecated and will be removed in a future version.

Transactions with non-unique modification IDs within a batch are marked accordingly in the validation results file, and those transactions are rejected.

reject_on_invalid configuration flag moved to request body.

Each batch must contain only unique transaction modification IDs. If duplicate transaction modification IDs are detected, the entire batch will be rejected, regardless of the reject_on_invalid flag is set to either true or false.

Added support for unknown entity type in transaction.

Added requirement for If-None-Match header in endpoint request, to ensure rejecting conflicting uploads under the same url.

• POST /api/transactions/batch/generate-upload-url

Improved the Transaction Batch documentation and OpenAPI specification to better reflect request/response formats and to improve generated API reference rendering.