> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mansa.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> What the API is, how it behaves, and how to get started

## Overview

The **Mansa API** is organized around **REST**. It uses predictable, resource-oriented URLs under a versioned base path, accepts **JSON** request bodies (file uploads use `multipart/form-data`), returns **JSON** responses, and relies on standard HTTP verbs and status codes.

* **Base path:** `/api/v1`
* **Content types:** `application/json` (default), `multipart/form-data` for proofs
* **Authentication:** `x-api-key` + `authorization: Bearer <JWT>`
* **Errors:** JSON error envelope with stable fields (`type`, `code`, `message`, …)

See the dedicated guides for **[Versioning](./versioning)**, **[Errors](./errors)**, **[Pagination](./pagination)**, **[Request IDs](./request-ids)**, and **[Metadata](./metadata)**.

***

## Environments

We separate the access for live and non-live traffic:

* **Production:** `https://api.mansa.xyz`

* **Sandbox:** `https://sandbox-api.mansa.xyz`

Sandbox don’t move real funds.

***

## Conventions

* **Versioning:** Path-based majors (for breaking changes) and SemVer in the spec for minor/patch updates. See **[Versioning](./versioning)**.
* **Idempotency:** Send a client-generated `client_request_id` on writes to safely retry the same operation. See **[Request IDs](./request-ids)**.
* **Pagination:** Page-based via `limit` and `page`, with `data.meta` reporting `limit`, `page`, and `total`. See **[Pagination](./pagination)**.
* **No bulk updates:** Each request operates on a single object or action.

***

## Quick glance

```http theme={null}
GET https://api.mansa.xyz/api/v2/liquidity/corridors?status=ACTIVE&limit=25&page=1
authorization: Bearer <token>
x-api-key: <key>
Accept: application/json
```