Amazi API
Overview
Connect your server or automation to Amazi with API v1.
Base URL
The Amazi API base URL is https://api.amazi.ai/v1. Send requests over HTTPS. The reference pages show full paths such as /v1/plans; append those paths to https://api.amazi.ai without an extra /api prefix or a second /v1.
Interactive reference
Open the API v1 reference to inspect endpoints, parameters and response schemas, or download the OpenAPI JSON. Both are readable without signing in and contain only the external /v1 API.
To try project chat requests, choose Authorize → userApiTokenBearer and enter your personal API token. Public data reads need no token. Try it out sends real requests: creating chats or sending messages changes your project and may use credits. Swagger keeps the token only until you reload the page.
Choose a resource
| Guide | What you can do | Authentication |
|---|---|---|
| Authentication | Create and revoke personal API tokens | Your account session manages tokens |
| Project chats | List, create, rename, archive and restore chats; read and send messages | Personal API token |
| Public data | Read plans, legal documents, banners and the questionnaire | None |
Project chat requests use your current account permissions and normal credit rules. Sending a message returns after acceptance; follow its queue and history to see the result.
First request
Read the plan catalog without a token:
curl --fail --silent --show-error https://api.amazi.ai/v1/plans -H 'Accept-Language: en'
To send a message, first create a token, then follow the project chat example. Token management uses /auth/api-tokens on the API origin, outside /v1.
Availability and retries
During an Amazi API update, requests can return HTTP 503 with code SYSTEM_MAINTENANCE and a Retry-After header in seconds. Wait before retrying; keep the same retry key when resubmitting a message. Published project addresses remain available, but project features that call Amazi's API may also need to wait.
The previous /public/... catalog URLs have moved to /v1/... and return HTTP 404. Use the paths in Public data.
For services connected inside a project, see Integrations and environment, GitHub synchronization and Amazi AI Gateway.