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

MX Technologies Transactions API

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

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 32 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

25 operations 19 paths 32 schemas 4 DELETE12 GET6 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.mx.com
Authentication
HTTP Bearer, HTTP Basic
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
postUsersByUserIdentifierMembersByMemberIdentifierExtendHistory 3 params → 202
GET
/users/{user_identifier}/members/{member_identifier}/transactions
List transactions by member
getUsersByUserIdentifierMembersByMemberIdentifierTransactions 14 params → 200
GET
/users/{user_identifier}/tags/{tag_guid}/transactions
List transactions by tag
getUsersByUserIdentifierTagsByTagGuidTransactions 12 params → 200
GET
/users/{user_identifier}/transactions
List transactions
getUsersByUserIdentifierTransactions 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
putUsersByUserIdentifierMembersByMemberIdentifierAccountsByAccountIdentifierTransactionsByTransactionIdentifier 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 32

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

TransactionResponseBody
object
1 property
RepeatingTransactionsResponseBody
object
1 property
SplitTransactionRequest
object
4 properties 1 required
EnhanceTransactionsResponseBody
object
1 property
TransactionsResponseBodyIncludes
object
2 properties
EnhanceTransactionResponse
object
23 properties
TransactionUpdateRequest
object
4 properties
TransactionCreateRequestBody
object
1 property
RepeatingTransactionResponse
object
12 properties
EnhanceTransactionsRequest
object
7 properties 2 required
TransactionUpdateRequestBody
object
1 property
MemberResponseBody
object
1 property
TransactionIncludesResponse
object
PaginationResponse
object
4 properties
TransactionCreateResponseBody
object
44 properties
TransactionResponse
object
44 properties
EnhanceTransactionsRequestBody
object
1 property
SplitTransactionsResponseBody
object
1 property
TransactionCreateRequest
object
12 properties 4 required
SplitTransactionRequestBody
object
1 property 1 required
MemberResponse
object
23 properties
SplitTransactionRequest_2
object
4 properties 1 required
EnhanceTransactionResponse_2
object
25 properties
TransactionUpdateRequest_2
object
1 property 1 required
RepeatingTransactionResponse_2
object
12 properties
EnhanceTransactionsRequest_2
object
7 properties 2 required
TransactionIncludesResponse_2
object
PaginationResponse_2
object
4 properties
TransactionCreateResponseBody_2
object
44 properties
TransactionResponse_2
object
44 properties
TransactionCreateRequest_2
object
12 properties 4 required
MemberResponse_2
object
23 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
MX SSO API
MX Data Access API
MX Batch API
MX Reporting API
MX Technologies Accounts API
MX Technologies ach return API
MX Technologies Budgets API
MX Technologies Categories API
MX Technologies Goals API
MX Technologies Insights API
MX Technologies Institutions API
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.