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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
MX

MX Consent Management V4 API

MX Consent Management V4 API from MX — 4 path(s) described in OpenAPI.

Documentation Provider Profile APIs.io OpenAPI GitHub

MX Consent Management V4 API is one of 3 APIs that MX publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 4 operations across 4 paths, and defines 2 schemas. It is described by OpenAPI 3.0.0, at version 4.0.

Requests are made against a single base URL, http://{baseurl}.

4 operations 4 paths 2 schemas 1 GET3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
4.0
Base URL
https://api.mx.com
Authentication
HTTP Bearer, HTTP Basic
Contact
MX
Terms of Service
View terms
Resource Areas
1

Authentication & Security 2

MX Consent Management V4 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 4

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

consent_management 4

Consent Management

GET
/api/{version}/consent_management
Consent list
3-consentList 1 param → 200
PUT
/api/{version}/consent_management/{ConsentPublicId}/accounts
Update Auto Access
autoAccessUpdate 2 params body → 200
PUT
/api/{version}/consent_management/{ConsentPublicId}/accounts/{AccountId}
Update Consented Account
accountEnabledStatus 3 params body → 200
PUT
/api/{version}/consent_management/{ConsentPublicId}/disable_app_sharing
Revoke Consent
revokeConsent 2 params → 200

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed is Consent (9 properties). Each schema is shown below with its type and property counts.

Consent
object
Consent object
9 properties
ConsentList
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mx-consent-management-openapi.yml Raw ↑

Other APIs MX publishes across the network.

MX Platform API
AE Profile APIs.io
MX Data Access
AE Profile APIs.io
← Back to M APIs
API Details
ID
mx:mx-consent-management-openapi
Base URL
https://api.mx.com
Docs
https://docs.mx.com/api-reference/platform-api/reference/mx-platform-api
Provider
MX
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=mx-consent-management-openapi&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mx-consent-management-openapi"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of MX Consent Management V4 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.