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 Platform Mx_platform API

The Mx_platform API from MX Platform — 22 operation(s) for mx_platform.

MX Platform Mx_platform API is one of 55 APIs that MX Platform publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Mx_platform. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 43 operations across 22 paths, and defines 60 schemas. It is described by OpenAPI 3.0.0, at version 0.1.0.

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

43 operations 22 paths 60 schemas 10 DELETE20 GET2 POST11 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
0.1.0
Base URL
https://api.mx.com
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

MX Platform Mx_platform API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 43

Across 22 paths, the API surfaces 43 operations — 10 DELETE, 20 GET, 2 POST, 11 PUT. Each is listed below with its method, path, parameters, and response codes.

Mx_platform 43
POST
/authorization_code
Request an authorization code.
requestAuthorizationCode body → 200
GET
/categories/{category_guid}
Read a default category
readDefaultCategory 1 param → 200
GET
/institutions
List institutions
listInstitutions 7 params → 200
GET
/managed_institutions
List managed institutions
listManagedInstitutions 2 params → 200
GET
/merchants/{merchant_guid}
Read merchant
readMerchant 1 param → 200
POST
/payment_processor_authorization_code
(Deprecated) Request an authorization code.
deprecatedRequestPaymentProcessorAuthorizationCode body → 200
DELETE
/users/{user_guid}
Delete user
deleteUser 1 param → 204
GET
/users/{user_guid}
Read user
readUser 1 param → 200
PUT
/users/{user_guid}
Update user
updateUser 1 param body → 200
DELETE
/users/{user_guid}/accounts/{account_guid}
Delete manual account
deleteManualAccount 2 params → 204
GET
/users/{user_guid}/accounts/{account_guid}
Read account
readAccount 2 params → 200
DELETE
/users/{user_guid}/categories/{category_guid}
Delete category
deleteCategory 2 params → 204
GET
/users/{user_guid}/categories/{category_guid}
Read a custom category
readCategory 2 params → 200
PUT
/users/{user_guid}/categories/{category_guid}
Update category
updateCategory 2 params body → 200
GET
/users/{user_guid}/holdings/{holding_guid}
Read holding
readHolding 2 params → 200
DELETE
/users/{user_guid}/managed_members/{member_guid}
Delete managed member
deleteManagedMember 2 params → 204
GET
/users/{user_guid}/managed_members/{member_guid}
Read managed member
readManagedMember 2 params → 200
PUT
/users/{user_guid}/managed_members/{member_guid}
Update managed member
updateManagedMember 2 params body → 200
DELETE
/users/{user_guid}/managed_members/{member_guid}/accounts/{account_guid}
Delete managed account
deleteManagedAccount 3 params → 204
GET
/users/{user_guid}/managed_members/{member_guid}/accounts/{account_guid}
Read managed account
readManagedAccount 3 params → 200
PUT
/users/{user_guid}/managed_members/{member_guid}/accounts/{account_guid}
Update managed account
updateManagedAccount 3 params body → 200
DELETE
/users/{user_guid}/managed_members/{member_guid}/accounts/{account_guid}/transactions/{transaction_guid}
Delete managed transaction
deleteManagedTransaction 4 params → 204
GET
/users/{user_guid}/managed_members/{member_guid}/accounts/{account_guid}/transactions/{transaction_guid}
Read managed transaction
readManagedTransaction 4 params → 200
PUT
/users/{user_guid}/managed_members/{member_guid}/accounts/{account_guid}/transactions/{transaction_guid}
Update managed transaction
updateManagedTransaction 4 params body → 200
DELETE
/users/{user_guid}/members/{member_guid}
Delete member
deleteMember 2 params → 204
GET
/users/{user_guid}/members/{member_guid}
Read member
readMember 2 params → 200
PUT
/users/{user_guid}/members/{member_guid}
Update member
updateMember 2 params body → 200
GET
/users/{user_guid}/members/{member_guid}/accounts/{account_guid}
Read account by member
readAccountByMember 3 params → 200
PUT
/users/{user_guid}/members/{member_guid}/accounts/{account_guid}
Update account by member
updateAccountByMember 3 params body → 200
GET
/users/{user_guid}/members/{member_guid}/rewards/{reward_guid}
Read Reward
readRewards 3 params → 200
GET
/users/{user_guid}/members/{member_guid}/statements/{statement_guid}
Read statement by member
readStatementByMember 3 params → 200
GET
/users/{user_guid}/members/{member_guid}/tax_documents/{tax_document_guid}
Read a Tax Document
readTaxDocument 3 params → 200
DELETE
/users/{user_guid}/taggings/{tagging_guid}
Delete tagging
deleteTagging 2 params → 204
GET
/users/{user_guid}/taggings/{tagging_guid}
Read tagging
readTagging 2 params → 200
PUT
/users/{user_guid}/taggings/{tagging_guid}
Update tagging
updateTagging 2 params body → 200
DELETE
/users/{user_guid}/tags/{tag_guid}
Delete tag
deleteTag 2 params → 204
GET
/users/{user_guid}/tags/{tag_guid}
Read tag
readTag 2 params → 200
PUT
/users/{user_guid}/tags/{tag_guid}
Update tag
updateTag 2 params body → 200
DELETE
/users/{user_guid}/transaction_rules/{transaction_rule_guid}
Delete transaction rule
deleteTransactionRule 2 params → 204
GET
/users/{user_guid}/transaction_rules/{transaction_rule_guid}
Read transaction rule
readTransactionRule 2 params → 200
PUT
/users/{user_guid}/transaction_rules/{transaction_rule_guid}
Update transactionrule
updateTransactionRule 2 params body → 200
GET
/users/{user_guid}/transactions/{transaction_guid}
Read transaction
readTransaction 2 params → 200
PUT
/users/{user_guid}/transactions/{transaction_guid}
Update transaction
updateTransaction 2 params body → 200

Schemas 60

The contract defines 60 schemas that model the data the API accepts and returns. The most detailed are AccountResponse (59 properties), TransactionResponse (43 properties), ManagedAccountUpdateRequest (31 properties), AccountUpdateRequest (21 properties). Each schema is shown below with its type and property counts.

AuthorizationCodeRequest
object
1 property
StatementResponse
object
8 properties
TransactionUpdateRequest
object
1 property 1 required
CategoryUpdateRequestBody
object
1 property
ManagedAccountUpdateRequestBody
object
1 property
PaginationResponse
object
4 properties
ManagedMemberUpdateRequestBody
object
1 property
HoldingResponseBody
object
1 property
InstitutionResponse
object
15 properties
TaxDocumentResponse
object
10 properties
CredentialRequest
object
2 properties
AuthorizationCodeResponseBody
object
1 property
TransactionRuleUpdateRequest
object
3 properties
CategoryResponseBody
object
1 property
UserResponseBody
object
1 property
RewardResponse
object
11 properties
MemberUpdateRequestBody
object
1 property
ManagedMemberUpdateRequest
object
3 properties
AuthorizationCodeResponse
object
1 property
UserResponse
object
5 properties
ManagedAccountUpdateRequest
object
31 properties
MerchantResponseBody
object
1 property
AuthorizationCodeRequestBody
object
1 property
TaggingUpdateRequestBody
object
1 property
TransactionUpdateRequestBody
object
1 property
StatementResponseBody
object
1 property
TransactionRuleUpdateRequestBody
object
1 property
AccountUpdateRequestBody
object
1 property
TransactionRuleResponse
object
7 properties
AccountResponse
object
59 properties
MerchantResponse
object
6 properties
MemberUpdateRequest
object
5 properties
ManagedTransactionUpdateRequest
object
20 properties
InstitutionsResponseBody
object
2 properties
RewardResponseBody
object
1 property
TagUpdateRequestBody
object
1 property
TransactionRuleResponseBody
object
1 property
HoldingResponse
object
19 properties
TaxDocumentResponseBody
object
1 property
TransactionResponse
object
43 properties
PaymentProcessorAuthorizationCodeRequestBody
object
1 property
ManagedTransactionUpdateRequestBody
object
1 property
MemberResponse
object
19 properties
AccountResponseBody
object
1 property
TaggingResponse
object
5 properties
PaymentProcessorAuthorizationCodeResponseBody
object
1 property
CategoryUpdateRequest
object
2 properties
CategoryResponse
object
8 properties
TagUpdateRequest
object
1 property 1 required
MemberResponseBody
object
1 property
TaggingUpdateRequest
object
1 property 1 required
TagResponseBody
object
1 property
PaymentProcessorAuthorizationCodeRequest
object
3 properties
AccountUpdateRequest
object
21 properties
TaggingResponseBody
object
1 property
UserUpdateRequest
object
4 properties
PaymentProcessorAuthorizationCodeResponse
object
1 property
TagResponse
object
3 properties
TransactionResponseBody
object
1 property
UserUpdateRequestBody
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mx-platform-mx-platform-api-openapi.yml Raw ↑

Other APIs MX Platform publishes across the network.

MX Platform Account_numbers API
MX Platform Account_owners API
MX Platform Accounts API
MX Platform Aggregate API
MX Platform Budgets API
MX Platform Categories API
MX Platform Challenges API
MX Platform Check_balance API
MX Platform Connect_widget_url API
MX Platform Credentials API
MX Platform Credit_card_product_guid API
MX Platform Current API
Where this information came from

This is an independent, third-party profile of MX Platform Mx_platform 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.