Skip to main content
GET
Read transaction by account

Authorizations

Authorization
string
header
required

To authenticate with the Platform API, include your Base64-encoded client_id and api_key in the Authorization header of every request:

Headers

Accept-Version
string
default:v20260929
required

MX Platform API version.

Example:

"v20260929"

Path Parameters

user_identifier
string
required

Use either the user id you defined or the MX-defined user guid. See Assigning Resource IDs.

member_identifier
string
required

Use either the member id you defined or the MX-defined member guid. See Assigning Resource IDs.

account_identifier
string
required

Use either the account id you defined or the MX-defined account guid. See Assigning Resource IDs.

transaction_identifier
string
required

Use either the transaction id you defined or the MX-defined transaction guid. See Assigning Resource IDs.

Query Parameters

includes
enum<string>[]

Enrich transaction responses with additional metadata. Pass one or more values as an array to selectively include data.

Accepted values: category, counterparties, merchant, repeating_transaction.

Example: ?includes[]=category&includes[]=merchant

Any other value, or a comma-separated string, returns a 400 error.

Available options:
category,
counterparties,
merchant,
repeating_transaction

Response

200 - application/json

OK

transaction
object

Extended transaction response. The category, counterparties, merchant, and repeating_transaction objects are only present when requested via the includes[] query parameter. When included but no data exists, the value is null.