Introduction

Relvo’s public API lets you report usage, look up customers, and integrate billing events into your own systems. It is a customer-facing, token-authenticated REST API — separate from the internal API the Relvo dashboard itself uses.

Base URL

All paths below are relative to your Relvo environment’s host:

Environment	Base URL
Production	https://app.relvoerp.com
Development	your environment’s Cloud Run URL (ask your Relvo contact)

A single domain serves both the dashboard and the API — there is no separate api. subdomain.

What’s in this reference

The API Reference tab is generated directly from Relvo’s backend — every endpoint, request/response shape, and required scope comes straight from the same route metadata that authorizes each request, not from hand-written documentation that can quietly fall behind. It’s rebuilt and published as part of every release, so it reflects the version of the API currently deployed to production.

Only operations explicitly marked for public documentation appear here. Internal application endpoints and inbound provider integrations (used internally for Chilean/LATAM fiscal document issuance) are never exposed.

Start with Authentication to get a token, then Idempotency if you’re writing (not just reading) through the API. The complete endpoint contract lives in the API Reference.

If you are connecting an AI agent rather than writing an integration by hand, MCP server is the shorter path — it exposes invoice lookups and the operations task queue over the Model Context Protocol, with no client to write.