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 managed data API

The managed data API from MX Technologies — 7 operation(s) for managed data.

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

This API exposes 16 operations across 7 paths, and defines 24 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.

16 operations 7 paths 24 schemas 3 DELETE7 GET3 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
Resource Areas
1

Authentication & Security 2

MX Technologies managed data 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 16

Across 7 paths, the API surfaces 16 operations — 3 DELETE, 7 GET, 3 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

managed data 16
GET
/managed_institutions
List managed institutions
listManagedInstitutions 2 params → 200
GET
/users/{user_guid}/managed_members
List managed members
listManagedMembers 3 params → 200
POST
/users/{user_guid}/managed_members
Create managed member
createManagedMember 1 param body → 202
DELETE
/users/{user_guid}/managed_members/{member_guid}
Delete managed member
deleteManagedMember 3 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
GET
/users/{user_guid}/managed_members/{member_guid}/accounts
List managed accounts
listManagedAccounts 4 params → 200
POST
/users/{user_guid}/managed_members/{member_guid}/accounts
Create managed account
createManagedAccount 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
GET
/users/{user_guid}/managed_members/{member_guid}/accounts/{account_guid}/transactions
List managed transactions
listManagedTransactions 7 params → 200
POST
/users/{user_guid}/managed_members/{member_guid}/accounts/{account_guid}/transactions
Create managed transaction
createManagedTransaction 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

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are AccountResponse (123 properties), TransactionResponse (44 properties), ManagedAccountUpdateRequest (31 properties), ManagedAccountCreateRequest (31 properties). Each schema is shown below with its type and property counts.

ManagedMemberCreateRequest
object
4 properties 1 required
ManagedMemberCreateRequestBody
object
1 property
TransactionResponseBody
object
1 property
ManagedTransactionCreateRequestBody
object
1 property
PaginationResponse
object
4 properties
ManagedAccountUpdateRequestBody
object
1 property
AccountResponse
object
123 properties
ManagedAccountCreateRequestBody
object
1 property
ManagedTransactionUpdateRequestBody
object
1 property
MemberResponse
object
23 properties
AccountResponseBody
object
1 property
MembersResponseBody
object
2 properties
ManagedAccountCreateRequest
object
31 properties 4 required
TransactionResponse
object
44 properties
ManagedMemberUpdateRequestBody
object
1 property
ManagedMemberUpdateRequest
object
3 properties
InstitutionsResponseBody
object
2 properties
MemberResponseBody
object
1 property
TransactionsResponseBody
object
2 properties
ManagedAccountUpdateRequest
object
31 properties
InstitutionResponse
object
18 properties
ManagedTransactionUpdateRequest
object
20 properties
ManagedTransactionCreateRequest
object
20 properties 6 required
AccountsResponseBody
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mx-technologies-managed-data-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 managed data 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.