Enrich multiple transactions - POST
Last updated
Was this helpful?
Last updated
Was this helpful?
Searches for an array of merchants. This endpoint is typically used for transaction list views. You send in multiple transactions at once in a single request.
Start with our guide on how to use MRS to enrich raw transaction data.
This endpoint returns a JSON object containing the following properties, as well as an array of enriched transactions. Each transaction must have a unique id property, which is used to identify the transaction in the response.
The id only has to be unique for this request, and can be any string. You could use the numeric index of the transaction in the transaction array, generate a unique UUID then and there for each transaction, etc
If you wish to submit crowdsourcing reports, this id is required, as it is used to identify the transaction within the request. The other parameters for each transaction are the same as the individual /v3/merchant request above.
List requests are recommended to contain 25 or less elements. Requests with higher amounts can be supported. Very long lists might have an impact on response times. Please contact us with any questions on this.
An optional array of response fields that will be force returned from our internal sources. This is useful if you want to cache fields such as the name or website during an extended call. Allowed values are: name, website, img, category, categories
["name","website"]
A JSON object containing one property per transaction enriched.
The keys of this object are the ID that was provided, previously passed in as the "id"
property in each transaction array element.
The value of this property is the array of merchants that were found when searching for that specific transaction