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 Accounts API

The accounts API from MX Technologies — 13 operation(s) for accounts.

MX Technologies Accounts 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 Account. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and 1 JSON Schema.

This API exposes 18 operations across 13 paths, and defines 20 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.

18 operations 13 paths 20 schemas 1 DELETE12 GET3 POST2 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 Accounts 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 18

Across 13 paths, the API surfaces 18 operations — 1 DELETE, 12 GET, 3 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Accounts 18
GET
/users/{user_guid}/accounts
List accounts
listUserAccounts 6 params → 200
POST
/users/{user_guid}/accounts
Create manual account
createManualAccount 1 param body → 200
GET
/users/{user_guid}/accounts/{account_guid}
Read account
readAccount 2 params → 200
DELETE
/users/{user_guid}/accounts/{account_guid}
Delete manual account
deleteManualAccount 3 params → 204
GET
/users/{user_guid}/accounts/{account_guid}/account_numbers
List account numbers by account
listAccountNumbersByAccount 4 params → 200
GET
/users/{user_guid}/members/{member_guid}/account_numbers
List account numbers by member
listAccountNumbersByMember 4 params → 200
GET
/users/{user_guid}/members/{member_guid}/account_owners
List account owners by member
listAccountOwnersByMember 4 params → 200
GET
/users/{user_guid}/members/{member_guid}/accounts
List accounts by member
listMemberAccounts 5 params → 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_identifier}/accounts
List accounts
getUsersByUserIdentifierAccounts 8 params → 200
POST
/users/{user_identifier}/accounts
Create manual account
postUsersByUserIdentifierAccounts 2 params body → 200
GET
/users/{user_identifier}/accounts/{account_identifier}/account_numbers
List account numbers by account
getUsersByUserIdentifierAccountsByAccountIdentifierAccountNumbers 5 params → 200
POST
/users/{user_guid}/accounts/merge
Merge accounts
mergeAccounts 2 params body → 200
GET
/users/{user_identifier}/members/{member_identifier}/account_owners
List account owners by member
getUsersByUserIdentifierMembersByMemberIdentifierAccountOwners 5 params → 200
GET
/users/{user_identifier}/members/{member_identifier}/accounts
List member accounts
getUsersByUserIdentifierMembersByMemberIdentifierAccounts 6 params → 200
GET
/users/{user_identifier}/members/{member_identifier}/accounts/{account_identifier}
Read member account
getUsersByUserIdentifierMembersByMemberIdentifierAccountsByAccountIdentifier 4 params → 200
PUT
/users/{user_identifier}/members/{member_identifier}/accounts/{account_identifier}
Update account by member
putUsersByUserIdentifierMembersByMemberIdentifierAccountsByAccountIdentifier 4 params body → 200

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are AccountResponse (123 properties), AccountResponse_2 (58 properties), AccountUpdateRequest (21 properties), AccountCreateRequest_2 (21 properties). Each schema is shown below with its type and property counts.

AccountUpdateRequest
object
21 properties
AccountResponse
object
123 properties
AccountNumberResponse
object
12 properties
AccountOwnersResponseBody
object
2 properties
AccountOwnerResponse
object
14 properties
AccountCreateRequestBody
object
1 property
AccountResponseBody
object
1 property
AccountCreateRequest
object
21 properties 2 required
AccountNumbersResponseBody
object
2 properties
AccountUpdateRequestBody
object
1 property
PaginationResponse
object
4 properties
AccountsResponseBody
object
2 properties
AccountUpdateRequest_2
object
21 properties
AccountResponse_2
object
58 properties
AccountNumberResponse_2
object
12 properties
AccountOwnerResponse_2
object
14 properties
AccountsMergeRequestBody
object
1 property
AccountCreateRequest_2
object
21 properties 2 required
AccountsMergeRequest
object
1 property 1 required
PaginationResponse_2
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mx-technologies-accounts-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 ach return API
MX Technologies Budgets API
MX Technologies Categories API
MX Technologies Goals API
MX Technologies Insights API
MX Technologies Institutions API
MX Technologies investment holdings API
Where this information came from

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