This endpoint should be used to ingest customer transactions into the Bud Platform.
By default, this endpoint is synchronous but can be easily switched to asynchronous using the 'X-Disable-Synchronous' header. Please refer to the following guide to ensure you set up First Party Ingestion correctly for your organisation based on your use case.
We accept a maximum of 1.000 transactions. If this threshold is not respected, a 400 error is returned.
We support the ingestion of transactions for multiple customers as part of the same request.
The detailed location enrichment response is an additional addon, otherwise only tokens are returned (read more about this in the location guide).
An ingestion request with an empty transaction list and provided transaction windows will be treated as a request to clear persisted transactions in the specified windows.
Note:
The enrichment values returned in the synchronous response of this endpoint may differ from those returned when fetching the ingested data from Retrieve Transactions V2.
The synchronous response provides an initial enrichment based solely on the submitted transaction data. During asynchronous ingestion, the data is re-enriched using the customer's existing transaction history and additional enrichment services, producing a more accurate and comprehensive result.