API keys

The API (application programming interface) lets your own programs fetch datool.ru data: CRMs, spreadsheets, dashboards, AI assistants. To call the API, a program needs a key — a long secret string it sends with every request. On the “API keys” tab you issue and revoke keys, see the API plan and request usage, and the organization's webhooks. How to write the requests themselves — see the API section.

Where to find it

hi.datool.ru/api-keys/ — the “API keys” tab of the account. It's visible to all members of the organization: anyone can issue their own key.

Keys, the request limit and webhooks belong to the current organization — the one selected in the switcher to the right of the account heading.

Summary strip: plan and usage

Summary strip: API plan, keys, requests this period and buttons

“API plan” and the tier badge: API.Max Test (free and with no end date: channel cards and statistics for 30 days), API.Max Start, Growth, Profi, Corporate, or access included in the Business subscription. Below — the end date of the plan and whether auto-renewal is on.
Keys — how many active keys there are and how many the plan allows.
“Requests this period” — how much of the limit is used, a bar and a percentage, and the date it renews. The period is 30 days from the plan payment, not a calendar month; unused requests don't carry over. For a custom-contract plan, only the number is shown.
Per second — how many requests per second the plan allows.
In packs — the remainder of purchased request packs and their term (if any).

Buttons: “API plans” (the page max.datool.ru/api/), “Buy requests” — a pack of +100,000 requests for 990 ₽ for 30 days (“Subscriptions, packs and company details”) — and “Create key”, which scrolls to the form.

Plan	Requests per period	Per second	Keys
API.Max Test	1,000	1	1
API.Max Start	100,000	5	2
API.Max Growth	300,000	10	5
API.Max Profi	1.5 million	20	20
MAX Business without an API plan	10,000	5	2
API.Max Corporate	by contract	by contract	by contract

A regular request uses 1 unit, a post search — 5; the “who am I” request (/v1/me/) and reference lists are free. Details — “Limits”.

For now, usage is only counted

API plans go on sale together with the data methods. Until then, request, rate and key limits don't restrict anything — the account shows them for reference (with a note that the limit will apply once API plans are on sale), and usage is simply counted.

Keys table

Columns:

Key — name, mask (dtk_0bfc23a7_•••••••• — the beginning of the key that lets you recognise it) and a “read and write” badge if it has that permission;
“Created by” — the email of the member who issued the key;
“Created” — the date;
“Last used” — when the key last came with a request (or “not used yet”);
“Requests this period” — this key's usage;
“Status” — “Active” or revoked on DATE;
“Revoke” — any member can revoke their own key; others' keys — the owner and administrators.

Revocation is confirmed in a dialog: the key stops working immediately and can't be restored — you'll need a new one. Revoked keys stay in the table as greyed-out rows for history.

New key

“Key name” (up to 80 characters) — to tell keys apart: “analytics server”, “department reports”.
“Read and write” — tick it if the key will manage webhooks (create and delete them through the API). Without it the key can only read data. The setting can't be changed later — you'd need a new key.
Click “Create key”.

A “Save the new key” block with the full key (it starts with dtk_) and a “Copy” button appears above the table. The full key is shown only once: after you leave the page you can't see it again, and the table keeps only the mask. Copy the key and store it somewhere safe — a password manager or your program's settings.

A key is a password

Anyone with the key can access data on behalf of your organization and use up its limit. Don't publish the key, don't send it in open chats and don't put it in code that others can see. If a key leaks, revoke it immediately and issue a new one.

If you already have as many keys as the plan allows (once limits apply), the “Create key” button is disabled with a hint to revoke an unneeded key or change the plan.

Webhooks

A webhook is an address on your server to which datool.ru itself sends new posts from selected channels — no need to keep polling the API. Webhooks are available from the API.Max Growth plan and are created through the API with a “Read and write” key (“Webhooks”). Here you see an overview:

Address, Channels (how many channels it tracks), Last delivery (and the error text, if any), Status — on, or off with the reason;
“Turn on” — re-enable a disabled webhook; “Delete” — notifications to this address stop immediately. The buttons are available to the owner and administrators.

If a webhook fails to deliver a single event for a whole day, it's turned off automatically and owners and administrators get an email.

How to connect

The key is sent in the header of every request: Authorization: Bearer dtk_…. The first request is GET https://api.datool.ru/v1/me/ (“who am I and what's open to me”): the response contains the organization, plan and remaining limit. The block's links: “API documentation”, how requests are counted, and connecting to an AI assistant (MCP).

Key rules

Keys belong to the organization, not the person: they use the organization's shared limit, and all members see them.
A member is removed from the organization (or leaves) — their keys for this organization are revoked.
A member's access is turned off, they're paused for lack of seats, or the organization is archived — their keys are suspended: the API answers that access is suspended, and when access returns, the keys work again.
The request limit is shared by the organization and used by the keys of all members. Above the limit the API returns a 429 error (quota exceeded), above the rate — 429 as well (too many requests).
The owner gets emails when 80 % and 100 % of the period's limit are used.