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 spending plan API

The spending plan API from MX Technologies — 9 operation(s) for spending plan.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 15 operations across 9 paths, and defines 10 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.

15 operations 9 paths 10 schemas 3 DELETE9 GET2 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 spending plan 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 15

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

spending plan 15
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/current
Read current spending plan iteration
readCurrentSpendingPlanIteration 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), SpendingPlanResponse (5 properties). Each schema is shown below with its type and property counts.

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

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

mx-technologies-spending-plan-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
#Spending Plan
← Back to M APIs
API Details
ID
mx-technologies:mx-technologies-spending-plan-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-spending-plan-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/mx-technologies-spending-plan-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 spending plan 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.