Documentation/Connecting/Your own panel/What the panel does, and what you do·5 / 9

What the panel does, and what you do

The panel is a mechanism, not a ready-made cabinet. We do not decide your service's business tasks and do not bend to them: a storefront, a client's own cabinet, a CRM — you build them, by hand or together with an AI.

What you get

The console
The veli command on the panel's server: put the panel in place, add nodes by IP, make clients, issue tokens and webhooks. Nothing has to be opened in a browser.
The API
The same actions over HTTPS: clients, nodes, groups, traffic, events. The schema openapi.json is what an AI or a programmer builds a client from, in any language.
Webhooks
The panel reports events by itself: a client was added, a term is about to end, traffic is running out, a node went silent. Your server gets a signed request and does its own part.
MCP for an AI
The same API as tools for Claude and other agents: “who expires this week”, “extend everyone tagged vip”. The rights come with the token.

What the panel does

Everything that has to do with access to the VPN — reliably, with no work from you.

  • Keeps the clients: term, devices, speed, traffic limit, a note and your tags.
  • Gives each one a single link to all your servers and a plain subscription page with the buttons for the apps.
  • Hands the list of clients to the nodes: a new client works on every node within half a minute.
  • Counts traffic and devices, keeps the log of actions, holds removed clients in the trash for 30 days.
  • Reports events by webhooks and a feed and answers an AI agent over MCP.

What you do

Everything that depends on your business stays with you; the panel does not interfere.

  • Prices and payment — Your price list, the payment system, refunds, taxes. The panel knows only days, devices and traffic — prices and payment are on your side.
  • The storefront and the client's cabinet — A site or an app where a person pays, sees the term and takes their link.
  • Your way of working — Who on your team may change what, which emails and messages go to clients, which reports you need.
  • Support and records — A CRM, requests, the history of talks. A client is tied to your system by an external ID: an order number or a user's ID in your system.

A token

Make a token with the rights and term you need — for a site, a CRM or an AI agent — and keep it so that a leak costs nothing.

  1. Make the token in the console

    On the panel's server, as root: veli token add <name> --rights read|clients|all. Only the console makes tokens and webhooks — not another token and not an API call.

  2. Name, rights, term

    The name — who uses it, say cabinet. The rights — read, clients or all (below). The term is optional: --days 90, from 1 to 3650 days; without --days the token has no end.

  3. Copy the token

    The console prints the token once: copy it into your system's settings. Lost it? Revoke it and make a new one.

A token for 90 days — on the panel's server
veli token add cabinet --rights clients --days 90
The tokens list and revoking by name
veli token list
veli token revoke cabinet
Read only
--rights read. Look at clients without their links, nodes, traffic, the event feed. Changes nothing
Clients
--rights clients. Look at everything, clients' links too, and keep the clients: add, extend, turn off and on, change the link, unbind a device, change many at once. Not delete
All
--rights all. All the panel can do: delete clients, keep nodes and groups. But the tokens and the webhooks — only the console makes them
  • The API's address is the panel's address, the secret path and /api/. veli token add prints it under the token itself (and so does the panel's install). The path is like a password: keep it next to the token, not in an open repository.
  • The token goes in the Authorization: Bearer veli_… header — from your servers. The panel does not answer a script on a page in a browser.
  • Tokens and webhooks are not made through the API, not even by an “All” token: a leaked token cannot breed more of itself. Only the console makes them.

Limits

  • 300 requests a minute per token. Each answer carries RateLimit-Limit, RateLimit-Remaining — how many are left in this minute — and RateLimit-Reset — in how many seconds the minute starts anew.
  • Over the limit — 429 wait and Retry-After: 60. Wait that many seconds and repeat the same request; for a POST — with the same repeat key.

The first request

Check the token: GET me answers with its name, rights and term, and the headers tell how many requests are left in this minute.

On your server
VELI=https://panel.example.com/Zq7mT2xP4vLc9wRbE5nK/api
VELI_TOKEN=veli_…
curl -si "$VELI/me" \
  -H "Authorization: Bearer $VELI_TOKEN"
Answer
HTTP/1.1 200 OK
content-type: application/json
ratelimit-limit: 300
ratelimit-remaining: 299
ratelimit-reset: 41

{"name": "cabinet", "token": true, "rights": "clients", "until": 0, "api": 1}