> For the complete documentation index, see [llms.txt](https://inoswap.gitbook.io/guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://inoswap.gitbook.io/guide/partners-and-api-integration/api-reference-and-authentication.md).

# API Reference & Authentication

Endpoints, authentication model, and infrastructure access configuration.

## Authentication

All API requests require an API key provided after partner validation.

Authentication header:

`x-api-key: <YOUR_PARTNER_KEY>`

<mark style="color:$danger;">API keys must be stored securely on the server side and must never be exposed in frontend or mobile code. Keys are issued manually to ensure infrastructure stability and proper traffic management.</mark>

***

## Core Endpoints

The InoSwap Partner API provides the following endpoints:

* **POST /quote** — Returns optimised routing and execution payload
* **GET /tokens/top200** — Top supported tokens
* **GET /tokens/featured** — Curated token list
* **GET /tokens/search** — Token discovery
* **GET /live** — Service health check

The `/quote` endpoint is the core of the routing engine, delivering both optimisation results and transaction-ready data.

***

## Access & Rate Limits

API access is configured based on your integration profile and expected traffic volume. Staging and production environments are handled separately.

Higher throughput and custom rate limits are available for production partners with growing order flow. Infrastructure scaling is aligned with platform needs.

{% hint style="info" %}
Partner integration request form [**here**](https://docs.google.com/forms/d/e/1FAIpQLSeOIIL5KhCnDc7Di2OoRL1OgTy7CsocgEr5Byf1aFGbyEp3JA/viewform)
{% endhint %}