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

The members API from MX Technologies — 20 operation(s) for members.

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

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

26 operations 20 paths 23 schemas 2 DELETE10 GET10 POST4 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 members 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 26

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

members 26
GET
/users/{user_guid}/members
List members
listMembers 4 params → 200
POST
/users/{user_guid}/members
Create member
createMember 2 params body → 200202
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 3 params body → 200
POST
/users/{user_guid}/members/{member_guid}/aggregate
Aggregate member
aggregateMember 5 params → 202
GET
/users/{user_guid}/members/{member_guid}/challenges
List member challenges
listMemberChallenges 4 params → 200
POST
/users/{user_guid}/members/{member_guid}/check_balance
Check balances
checkBalances 2 params → 202
GET
/users/{user_guid}/members/{member_guid}/credentials
List member credentials
listMemberCredentials 4 params → 200
POST
/users/{user_guid}/members/{member_guid}/identify
Identify member
identifyMember 2 params → 202
PUT
/users/{user_guid}/members/{member_guid}/resume
Resume aggregation
resumeAggregation 2 params body → 202
GET
/users/{user_guid}/members/{member_guid}/status
Read member status
readMemberStatus 2 params → 200
POST
/users/{user_guid}/members/{member_guid}/verify
Verify member
verifyMember 3 params → 200
GET
/users/{user_identifier}/members
List members
listMembers 5 params → 200
POST
/users/{user_identifier}/members
Create member
createMember 3 params body → 200202
DELETE
/users/{user_identifier}/members/{member_identifier}
Delete member
deleteMember 3 params → 204
GET
/users/{user_identifier}/members/{member_identifier}
Read member
readMember 3 params → 200
PUT
/users/{user_identifier}/members/{member_identifier}
Update member
updateMember 4 params body → 200
POST
/users/{user_identifier}/members/{member_identifier}/aggregate
Aggregate member
aggregateMember 4 params → 202
GET
/users/{user_identifier}/members/{member_identifier}/challenges
List member challenges
listMemberChallenges 5 params → 200
POST
/users/{user_identifier}/members/{member_identifier}/check_balance
Check balances
checkBalances 3 params → 202
GET
/users/{user_identifier}/members/{member_identifier}/credentials
List member credentials
listMemberCredentials 5 params → 200
POST
/users/{user_identifier}/members/{member_identifier}/identify
Identify member
identifyMember 3 params → 202
PUT
/users/{user_identifier}/members/{member_identifier}/resume
Resume aggregation
resumeAggregation 3 params body → 202
GET
/users/{user_identifier}/members/{member_identifier}/status
Read member status
readMemberStatus 3 params → 200
POST
/users/{user_identifier}/members/{member_identifier}/verify
Verify member
verifyMember 4 params → 200

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are MemberResponse (23 properties), MemberStatusResponse (10 properties), MemberCreateRequest (8 properties), MemberCreateRequest_2 (7 properties). Each schema is shown below with its type and property counts.

MemberUpdateRequestBody
object
1 property
MemberCreateRequest
object
8 properties 2 required
MemberCreateRequest_2
object
7 properties 2 required
SupportedProducts
string
ImageOptionResponse
object
4 properties
PaginationResponse
object
4 properties
MemberResumeRequest
object
1 property
MemberResponse
object
23 properties
MemberStatusResponse
object
10 properties
OptionResponse
object
3 properties
CredentialRequest
object
2 properties
MembersResponseBody
object
2 properties
CredentialsResponseBody
object
2 properties
MemberCreateRequestBody_2
object
6 properties
MemberCreateRequestBody
object
5 properties
MemberResumeRequestBody
object
1 property
MemberUpdateRequest
object
6 properties
MemberResponseBody
object
1 property
DataRequest
object
Contains a products array that specifies the products you want to aggregate.
1 property 1 required
CredentialResponse
object
6 properties
ChallengesResponseBody
object
2 properties
ChallengeResponse
object
7 properties
MemberStatusResponseBody
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mx-technologies-members-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 members 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.