Data
MX Data APIs proxy MX Core Services through the Candescent API Gateway. This tag is for bulk data and logs—notably MX Logs transaction feeds (e.g. Avro downloads) and other MDX-aligned retrieval.
Core capabilities: Account aggregation, data enhancement (transactions and holdings pipelines), and integration with MX ecosystem hosts via ext_host.
For the full MX API surface, see MX Documentation.
End-user benefits
- View consolidated account and transaction context fed by MX data pipelines.
- Support operational and reporting flows that consume MX log streams.
Integration capabilities
- Pull MX Logs transaction creation events for an institution and date (Avro).
- Route requests through the gateway using
ext_host(e.g.api.mx.com,live.moneydesktop.com,sso.moneydesktop.com,logs.moneydesktop.com). - Use OAuth2 Bearer authentication and
Acceptnegotiation (including JSON, XML, AVRO where supported).
Required headers (MX gateway operations)
| Header | Description |
|---|---|
Authorization | Bearer token (OAuth2 authentication) |
ext_host | Target MX host for request routing |
correlationId | UUID to trace and correlate requests (documentation/mx-services.yaml) |
Accept | Content-type preference (e.g. application/vnd.mx.logs.v1+avro for log download) |
Error codes
| HTTP Status Code | Message |
|---|---|
| 400 | Bad Request — invalid parameters or malformed request. Typical JSON fields: error, message, optional errors[] (field, message) |
| 401 | Unauthorized — missing, invalid, or expired credentials. Typical JSON fields: error, message |
| 403 | Forbidden — authenticated but not authorized. Typical JSON fields: error, message |
| 404 | Not Found — resource missing or feature not enabled. Typical JSON fields: error, message (e.g. log download: institution may not be enabled for MX Logs, or ext_host / credentials misconfigured—"ClientReportingProfile does not exist" is called out in the log download operation description) |