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 Platform

MX Platform Spending_plans API

The Spending_plans API from MX Platform — 8 operation(s) for spending_plans.

Documentation Provider Profile APIs.io OpenAPI GitHub

MX Platform Spending_plans API is one of 55 APIs that MX Platform publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Spending_plans. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 14 operations across 8 paths, and defines 10 schemas. It is described by OpenAPI 3.0.0, at version 0.1.0.

Requests are made against 2 base URLs: https://api.mx.com, https://int-api.mx.com.

14 operations 8 paths 10 schemas 3 DELETE8 GET2 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
0.1.0
Base URL
https://api.mx.com
Authentication
HTTP Basic
Contact
MX Platform API
Resource Areas
1

Authentication & Security 1

MX Platform Spending_plans API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

Paths & Operations 14

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

Spending_plans 14
POST
/users/{user_guid}/spending_plans/{spending_plan_guid}/iterations/current/iteration_items
Create spending plan iteration item
createSpendingPlanIterationItem 2 params body → 200
GET
/users/{user_guid}/spending_plans/{spending_plan_guid}/iterations/current/iteration_items
List spending plan iteration items
listSpendingPlanIterationItems 4 params → 200
POST
/users/{user_guid}/spending_plans
Create spending plan
createSpendingPlan 1 param → 200
GET
/users/{user_guid}/spending_plans
List spending plans
listSpendingPlans 3 params → 200
DELETE
/users/{user_guid}/spending_plans/{spending_plan_guid}/spending_plan_accounts/{spending_plan_account_guid}
Delete spending plan account
deleteSpendingPlanAccount 3 params → 204
GET
/users/{user_guid}/spending_plans/{spending_plan_guid}/spending_plan_accounts/{spending_plan_account_guid}
Read spending plan account
readSpendingPlanAccount 5 params → 200
DELETE
/users/{user_guid}/spending_plans/{spending_plan_guid}/iterations/current/iteration_items/{iteration_item_guid}
Delete spending plan iteration item
deleteSpendingPlanIterationItem 3 params → 204
GET
/users/{user_guid}/spending_plans/{spending_plan_guid}/iterations/current/iteration_items/{iteration_item_guid}
Read a spending plan iteration item
readSpendingPlanIterationItem 5 params → 200
PUT
/users/{user_guid}/spending_plans/{spending_plan_guid}/iterations/current/iteration_items/{iteration_item_guid}
Update a spending plan iteration item
updateSpendingPlanIterationItem 3 params body → 200
DELETE
/users/{user_guid}/spending_plans/{spending_plan_guid}
Delete spending plan
deleteSpendingPlan 2 params → 204
GET
/users/{user_guid}/spending_plans/{spending_plan_guid}
Read a spending plan for a user
readSpendingPlanUser 4 params → 200
GET
/users/{user_guid}/spending_plans/{spending_plan_guid}/spending_plan_accounts
List spending plan accounts
listSpendingPlanAccounts 4 params → 200
GET
/users/{user_guid}/spending_plans/{spending_plan_guid}/iterations
List spending plan iterations
listSpendingPlanIterations 4 params → 200
GET
/users/{user_guid}/spending_plans/{spending_plan_guid}/iterations/{iteration_number}
Read a spending plan iteration
readSpendingPlanIteration 5 params → 200

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are SpendingPlanIterationItemResponse (12 properties), SpendingPlanIterationResponse (8 properties), SpendingPlanAccountResponse (7 properties), SpendingPlanIterationItemCreateRequestBody (5 properties). Each schema is shown below with its type and property counts.

SpendingPlanAccountResponse
object
7 properties
SpendingPlanIterationsResponse
object
2 properties
SpendingPlanIterationItemsResponseBody
object
2 properties
SpendingPlanIterationItemCreateRequestBody
object
5 properties 1 required
PaginationResponse
object
4 properties
SpendingPlansResponseBody
object
2 properties
SpendingPlanIterationResponse
object
8 properties
SpendingPlanIterationItemResponse
object
12 properties
SpendingPlanAccountsResponse
object
2 properties
SpendingPlanResponse
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mx-platform-spending-plans-api-openapi.yml Raw ↑

Other APIs MX Platform publishes across the network.

MX Platform Account_numbers API
AE Profile APIs.io
MX Platform Account_owners API
AE Profile APIs.io
MX Platform Accounts API
AE Profile APIs.io
MX Platform Aggregate API
AE Profile APIs.io
MX Platform Budgets API
AE Profile APIs.io
MX Platform Categories API
AE Profile APIs.io
MX Platform Challenges API
AE Profile APIs.io
MX Platform Check_balance API
AE Profile APIs.io
MX Platform Connect_widget_url API
AE Profile APIs.io
MX Platform Credentials API
AE Profile APIs.io
MX Platform Credit_card_product_guid API
AE Profile APIs.io
MX Platform Current API
AE Profile APIs.io
#Spending_plans
← Back to M APIs
API Details
ID
mx-platform:mx-platform-spending-plans-api
Base URL
https://api.mx.com
Docs
https://docs.mx.com/
Provider
MX Platform
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-platform-spending-plans-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mx-platform-spending-plans-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 Platform Spending_plans 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.