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 Technologies

MX Technologies taggings API

The taggings API from MX Technologies — 2 operation(s) for taggings.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 5 operations across 2 paths, and defines 8 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.

5 operations 2 paths 8 schemas 1 DELETE2 GET1 POST1 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
Contact
MX Platform API
Resource Areas
1

Authentication & Security 2

MX Technologies taggings 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 5

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

taggings 5
GET
/users/{user_guid}/taggings
List taggings
listTaggings 3 params → 200
POST
/users/{user_guid}/taggings
Create tagging
createTagging 1 param body → 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

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are TaggingResponse (5 properties), PaginationResponse (4 properties), TaggingsResponseBody (2 properties), TaggingCreateRequest (2 properties). Each schema is shown below with its type and property counts.

TaggingUpdateRequestBody
object
1 property
TaggingResponse
object
5 properties
TaggingUpdateRequest
object
1 property 1 required
TaggingResponseBody
object
1 property
TaggingCreateRequestBody
object
1 property
TaggingCreateRequest
object
2 properties 2 required
TaggingsResponseBody
object
2 properties
PaginationResponse
object
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mx-technologies-taggings-api-openapi.yml Raw ↑

Other APIs MX Technologies publishes across the network.

MX Atrium API
AE Profile APIs.io
MX SSO API
AE Profile APIs.io
MX Data Access API
AE Profile APIs.io
MX Batch API
AE Profile APIs.io
MX Reporting API
AE Profile APIs.io
MX Technologies accounts API
AE Profile APIs.io
MX Technologies ach return API
AE Profile APIs.io
MX Technologies budgets API
AE Profile APIs.io
MX Technologies categories API
AE Profile APIs.io
MX Technologies goals API
AE Profile APIs.io
MX Technologies insights API
AE Profile APIs.io
MX Technologies institutions API
AE Profile APIs.io
#Taggings
← Back to M APIs
API Details
ID
mx-technologies:mx-technologies-taggings-api
Base URL
https://api.mx.com
Docs
https://docs.mx.com/api-reference/platform-api/overview/
Provider
MX Technologies
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-technologies-taggings-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mx-technologies-taggings-api"

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 Technologies taggings 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.