> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.solvimon.com/platform-guides/for-developers/introduction/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.solvimon.com/_mcp/server. # Introduction for developers This section covers everything you need to integrate with Solvimon: authentication, error handling, idempotency, webhooks, and HTTP conventions. > **Tip** > > First time integrating? Get an API key ([Authentication](/platform-guides/for-developers/authentication)), then follow the [API quickstart](/platform-guides/getting-started/onboarding-and-tutorials/api-quickstart) to make your first request against the test environment. --- ## The four APIs Solvimon exposes four separate APIs. Most integrations use all four. | API | Base path | What it's for | | --------------------- | --------- | ----------------------------------------------------------- | | **Configuration API** | `/v1/` | Create and manage meters, products, pricing plans, features | | **Identity API** | `/v1/` | Create and manage customers, subscriptions | | **Transaction API** | `/v1/` | Invoices, payments, credit notes | | **Event API** | `/v1/` | Ingest usage events | Full endpoint reference is in the [API Docs](/api-docs) tab. ## Environments | Environment | API base URL | Desk URL | | -------------- | ---------------------------------------------------------------------- | ---------------------------------------------------------------- | | **Test** | [https://test.api.solvimon.com/v1/](https://test.api.solvimon.com/v1/) | [https://test.desk.solvimon.com](https://test.desk.solvimon.com) | | **Production** | [https://api.solvimon.com/v1/](https://api.solvimon.com/v1/) | [https://desk.solvimon.com](https://desk.solvimon.com) | Test and production are fully isolated. Test keys will not work against the production endpoint and vice versa. Data created in one environment never appears in the other. ## Request conventions Every request requires: * `Content-Type: application/json` * `X-API-KEY: ` – see [Authentication](/platform-guides/for-developers/authentication) * HTTPS – plain HTTP requests are rejected Every response includes an `X-REQUEST-ID` header. Save this value when debugging; it's required when contacting support about a specific request. --- ## Start here #### [Authentication](/platform-guides/for-developers/authentication) Create an API key and use it to authenticate requests in each environment. #### [Local development setup](/platform-guides/for-developers/local-development) Configure your local environment to make API calls and receive webhooks during development. #### [Errors](/platform-guides/for-developers/api) HTTP response codes, error payloads, and what each error code means. #### [Troubleshooting](/platform-guides/for-developers/troubleshooting) Common errors during integration and how to resolve them. ## Build a robust integration #### [Idempotency](/platform-guides/for-developers/idempotency) Safely retry requests without risking duplicate operations. #### [Webhooks](/platform-guides/for-developers/webhooks) Receive real-time notifications when resources change, with at-least-once delivery. #### [API timeouts](/platform-guides/for-developers/api-1) Recommended client-side timeout settings for resilient API calls. #### [Developing for Solvimon](/platform-guides/for-developers/developing-for-solvimon) Build your integration with AI coding agents: llms.txt, the Solvimon skill, and the Solvimon MCP server with its full tool reference. ## API conventions #### [Query parameters](/platform-guides/for-developers/query-parameters) Filter, order, and paginate list responses. #### [Expanding responses](/platform-guides/for-developers/expanding-responses) Request related objects inline instead of fetching them by ID. #### [Timestamp formatting](/platform-guides/for-developers/time-stamp-formatting) ISO 8601 requirements for timestamps, especially when ingesting events. #### [Locale](/platform-guides/for-developers/locale) Supported locales for customer-facing documents and communication.