API Reference
Endpoints, authentication and payloads for the Auron API.
Auron's REST API is described by a single, always-current OpenAPI document rather than a hand-maintained reference. The document is generated directly from the same API definitions the server itself runs against, so it can't drift out of sync with what's actually deployed.
Where to find it
| URL | |
|---|---|
| Base URL | https://app.useauron.ai/api |
| Interactive docs | https://app.useauron.ai/api/api-docs |
| OpenAPI document | https://app.useauron.ai/api/v1/openapi.json |
Endpoints are mounted under /v1/* on the base URL, one path per resource, following standard REST conventions. The interactive docs render the same OpenAPI document, so you can browse every endpoint and its request and response shapes in the browser.
Authentication
Every request needs a bearer token issued through Auron's OAuth2 flow. See Auron as a Headless Backend for how to obtain one, whether that's a user-authorized token or a client-credentials grant for a service.
Exploring it without reading raw JSON
If you'd rather explore than read the spec directly, an MCP client like Auron in Claude can search and describe the same API conversationally, useful for finding the right endpoint before you write code against it.
Scopes
What a token can reach is limited by its granted OAuth2 scopes. Read and write are typically separated per resource, so a token can be issued for exactly the access a given integration needs.