How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
MX Technologies

MX Technologies transactions API

The transactions API from MX Technologies — 19 operation(s) for transactions.

Documentation Provider Profile APIs.io OpenAPI GitHub

MX Technologies transactions API is one of 31 APIs that MX Technologies publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 1 JSON Schema.

This API exposes 25 operations across 19 paths, and defines 21 schemas. It is described by OpenAPI 3.0.0, at version 20111101.

Requests are made against 2 base URLs: https://int-api.mx.com, https://api.mx.com.

25 operations 19 paths 21 schemas 4 DELETE12 GET6 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
20111101
Base URL
https://api.mx.com
Authentication
HTTP Bearer, HTTP Basic
Contact
MX Platform API
Resource Areas
1

Authentication & Security 2

MX Technologies transactions API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 25

Across 19 paths, the API surfaces 25 operations — 4 DELETE, 12 GET, 6 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

transactions 25
POST
/transactions/enhance
Enhance transactions
enhanceTransactions body → 200
POST
/users/{user_guid}/accounts/{account_guid}/transactions
Create manual transaction
createManualTransaction 2 params body → 200
GET
/users/{user_guid}/accounts/{account_guid}/transactions
List transactions by account
listTransactionsByAccount 15 params → 200
PUT
/users/{user_guid}/members/{member_guid}/accounts/{account_guid}/transactions/{transaction_guid}
Update Transaction by Account
updateTransactionByAccount 4 params body → 200
POST
/users/{user_guid}/members/{member_guid}/extend_history
Extend history
extendHistory 2 params → 202
GET
/users/{user_guid}/members/{member_guid}/transactions
List transactions by member
listTransactionsByMember 15 params → 200
GET
/users/{user_guid}/tags/{tag_guid}/transactions
List transactions by tag
listTransactionsByTag 16 params → 200
DELETE
/users/{user_guid}/transaction_rules/{transaction_rule_guid}
Delete transaction rule
deleteTransactionRule 2 params → 204
GET
/users/{user_guid}/transactions
List transactions
listTransactions 15 params → 200
GET
/users/{user_guid}/transactions/{transaction_guid}
Read transaction
readTransaction 3 params → 200
PUT
/users/{user_guid}/transactions/{transaction_guid}
Update transaction
updateTransaction 2 params body → 200
DELETE
/users/{user_guid}/transactions/{transaction_guid}
Delete manual transactions
deleteManualTransactions 2 params → 204
GET
/users/{user_guid}/repeating_transactions
List Repeating Transactions
repeatingTransactions 1 param → 200
GET
/users/{user_guid}/repeating_transactions/{repeating_transaction_guid}
Get a Repeating Transaction
specificRepeatingTransaction 2 params → 200
DELETE
/users/{user_guid}/transactions/{transaction_guid}/split
Delete split transactions
deleteSplitTransactions 2 params → 204
POST
/users/{user_guid}/transactions/{transaction_guid}/split
Create split transactions
createSplitTransactions 2 params body → 200
GET
/users/{user_guid}/members/{member_guid}/accounts/{account_guid}/transactions
List transactions by account per member
listTransactionsByAccountPerMember 13 params → 200
POST
/users/{user_identifier}/members/{member_identifier}/extend_history
Extend history
extendHistory 3 params → 202
GET
/users/{user_identifier}/members/{member_identifier}/transactions
List transactions by member
listTransactionsByMember 14 params → 200
GET
/users/{user_identifier}/tags/{tag_guid}/transactions
List transactions by tag
listTransactionsByTag 12 params → 200
GET
/users/{user_identifier}/transactions
List transactions
listTransactions 12 params → 200
GET
/users/{user_identifier}/members/{member_identifier}/accounts/{account_identifier}/transactions/{transaction_identifier}
Read transaction by account
readTransactionByAccount 7 params → 200
PUT
/users/{user_identifier}/members/{member_identifier}/accounts/{account_identifier}/transactions/{transaction_identifier}
Update transaction
updateTransactionByAccount 6 params body → 200
DELETE
/users/{user_identifier}/members/{member_identifier}/accounts/{account_identifier}/transactions/{transaction_identifier}/split
Delete split transactions by account
deleteSplitTransactionByAccount 5 params → 204
POST
/users/{user_identifier}/members/{member_identifier}/accounts/{account_identifier}/transactions/{transaction_identifier}/split
Create split transactions by account
createSplitTransactionsByAccount 5 params body → 200

Schemas 21

The contract defines 21 schemas that model the data the API accepts and returns. The most detailed are TransactionCreateResponseBody (44 properties), TransactionResponse (44 properties), EnhanceTransactionResponse (23 properties), MemberResponse (23 properties). Each schema is shown below with its type and property counts.

TransactionCreateRequestBody
object
1 property
SplitTransactionRequestBody
object
1 property 1 required
EnhanceTransactionsRequestBody
object
1 property
TransactionCreateRequest
object
12 properties 4 required
TransactionResponseBody
object
1 property
PaginationResponse
object
4 properties
EnhanceTransactionsRequest
object
7 properties 2 required
TransactionUpdateRequest
object
4 properties
TransactionIncludesResponse
object
TransactionCreateResponseBody
object
44 properties
EnhanceTransactionsResponseBody
object
1 property
TransactionsResponseBodyIncludes
object
2 properties
MemberResponse
object
23 properties
TransactionResponse
object
44 properties
MemberResponseBody
object
1 property
SplitTransactionRequest
object
4 properties 1 required
TransactionUpdateRequestBody
object
1 property
EnhanceTransactionResponse
object
23 properties
SplitTransactionsResponseBody
object
1 property
RepeatingTransactionsResponseBody
object
1 property
RepeatingTransactionResponse
object
12 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mx-technologies-transactions-api-openapi.yml Raw ↑

Other APIs MX Technologies publishes across the network.

MX Atrium API
AE Profile APIs.io
MX SSO API
AE Profile APIs.io
MX Data Access API
AE Profile APIs.io
MX Batch API
AE Profile APIs.io
MX Reporting API
AE Profile APIs.io
MX Technologies accounts API
AE Profile APIs.io
MX Technologies ach return API
AE Profile APIs.io
MX Technologies budgets API
AE Profile APIs.io
MX Technologies categories API
AE Profile APIs.io
MX Technologies goals API
AE Profile APIs.io
MX Technologies insights API
AE Profile APIs.io
MX Technologies institutions API
AE Profile APIs.io
#Transaction
← Back to M APIs
API Details
ID
mx-technologies:mx-technologies-transactions-api
Base URL
https://api.mx.com
Docs
https://docs.mx.com/api-reference/platform-api/overview/
Provider
MX Technologies
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=mx-technologies-transactions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mx-technologies-transactions-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of MX Technologies transactions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.