REST API - Moneda Docs

The Moneda REST API provides standard HTTP endpoints that mirror the functionality of the MCP tools. If you prefer working with REST over MCP, or need to integrate Moneda into a backend service, the REST API is for you.

What is the REST API?

The REST API covers everything available through MCP plus a few REST-only operations (sessions, sub-account reads). Anything you can do with an AI assistant you can also do with a simple HTTP request.

The REST API uses the same OAuth 2.0 tokens as MCP, so you don’t need separate credentials.

Base URL

All API requests are made to:

https://rest.moneda.com/v1

api.moneda.com is not the REST API. It’s a legacy compatibility host that serves a small subset of these routes and publishes no OpenAPI spec. Point integrations at rest.moneda.com.

Key features

Standard HTTP — Use any language or HTTP client. No MCP SDK required.
Same authentication — OAuth 2.0 Bearer tokens from the MCP auth flow work directly.
OpenAPI spec — Machine-readable spec at /v1/openapi.json for code generation.
Interactive docs — Swagger UI at /v1/docs for exploring and testing endpoints.
JSON responses — All responses are returned in JSON format.

Quick example

curl -X GET https://rest.moneda.com/v1/balances \
  -H "Authorization: Bearer YOUR_TOKEN"

{
  "balances": [
    { "currency": "USD", "balance": "1250.00" },
    { "currency": "EUR", "balance": "830.50" }
  ]
}

Versioning and deprecation

The API is versioned in the URL path. The current major version is v1, and every endpoint lives under https://rest.moneda.com/v1. Backward-compatible changes ship within v1, without notice. Build your client to tolerate them:

new endpoints
new optional request parameters
new fields in responses
new values in an existing enum, such as a new transaction type or status

Breaking changes ship as a new major version. Removing or renaming an endpoint, a parameter or a response field, making an optional parameter required, or changing the meaning of an existing field never happens inside v1. Such a change is released under a new path (/v2), and /v1 keeps running alongside it. A check in our release pipeline blocks any change that removes a v1 endpoint. Deprecation is signalled in the response. When an endpoint or a whole version is scheduled for removal, every response from it carries:

Header	Standard	Meaning
`Deprecation`	RFC 9745	The date the endpoint was deprecated, for example `@1893456000`
`Sunset`	RFC 8594	The date after which the endpoint stops responding
`Link`	RFC 9745	A `rel="deprecation"` link to the migration guide

Deprecation: @1893456000
Sunset: Mon, 01 Jul 2030 00:00:00 GMT
Link: <https://docs.moneda.com/api/overview#versioning-and-deprecation>; rel="deprecation"; type="text/html"

The values above are an illustration. Deprecated operations are also marked deprecated: true in the OpenAPI spec and listed on this page. Nothing in v1 is deprecated today.

Rate limits

Requests are limited per IP address, 60 per minute by default. Every response reports the current state, so a client can slow down before it is refused. See Rate limits for the headers.

What’s next?

Authentication

Learn how to authenticate your API requests.

API Endpoints

Browse the complete list of REST endpoints by domain.

OpenAPI Spec

Use the OpenAPI spec to generate client SDKs.

CLI Tool

Prefer the command line? Try the Moneda CLI.

​What is the REST API?

​Base URL

​Key features

​Quick example

​Versioning and deprecation

​Rate limits

​What’s next?

Authentication

API Endpoints

OpenAPI Spec

CLI Tool

What is the REST API?

Base URL

Key features

Quick example

Versioning and deprecation

Rate limits

What’s next?