---
title: "Overview — Anis Developers"
description: "How the Anis Partner API works — your application, its keys, signed calls, verified answers and safe orders."
url: https://developers.anis.ly/docs/overview/
language: en
---

> Every page of this documentation: https://developers.anis.ly/llms.txt

# Overview

The Anis Partner API lets your own system buy Anis cards and hand them to your customers: read your wallets and the catalogue, place orders, and read the card codes you bought. This page explains how it fits together before the guides go into detail.

## Who is who

- **Your application** — what Anis staff create for you. It has **permissions** (which calls it may make), the **networks** it may call from, optional **limits**, and the **wallets** it may use.
- **Your Anis business account** — the account the wallets belong to. Purchases are paid from its wallets.
- **Your key** — a key pair you create yourself. The private half never leaves your side; Anis only ever sees the public half. An application can have its key replaced without changing anything else.

## Every call is signed, every answer is verified

There is no API key to send. Instead:

1. **You sign every request** with your private key. Anis checks the signature, and refuses anything it cannot verify, before it looks at what you asked for.
2. **Anis signs every answer** with its own key. Your client checks that signature and throws the answer away if it does not verify — so a forged or altered answer is never acted on.

The signing is exact to the byte, which is why we provide [SDKs](https://developers.anis.ly/sdks.md) that do it for you. If you write your own client, the [signing](https://developers.anis.ly/docs/signing-requests.md) and [verifying](https://developers.anis.ly/docs/verifying-answers.md) guides give every rule.

## What you can do

| Area | Calls |
| --- | --- |
| Your application | Read your profile and current permissions |
| Wallets | List your wallets and their balances |
| Catalogue | Browse categories, subcategories and the cards a wallet can buy, priced for that wallet |
| Orders | Place an order, resume one whose outcome you did not receive, read where an order stands |
| Owned cards | List bought cards, and reveal the codes of one card or a whole invoice |
| Diagnostics | Check your signature: Anis reports exactly what it saw |

The [API reference](https://developers.anis.ly/reference.md) lists every call with its permission, fields and refusals.

## Orders cannot be bought twice by accident

You choose an **operation id** for each order and keep it. Sending the same id again never buys twice: it resumes the same order and returns its real outcome. That is what makes it safe to retry after a timeout. See [Orders and recovery](https://developers.anis.ly/docs/orders-and-recovery.md).

## One address, nothing else to configure

Anis gives you the address to call. Each Anis deployment is a fully separate copy — its own address, keys and data — so there is no “environment” setting anywhere: which one you talk to is decided by the address alone, and a key enrolled with one means nothing to another.

> **Getting access**
>
> Anis staff create your application, set its permissions, networks and limits, and send you an invitation to enrol your first key. Start with [Enrol a key](https://developers.anis.ly/docs/enrol-a-key.md).