Documentation
Limits and security
The connection is deliberately narrow. What follows is the whole surface: what a token may do, how often it may do it, and the doors that stay shut whatever you ask for.
Token scopes
| Scope | What it allows |
|---|---|
| Read | Reads pages, drafts, statistics and inbox. Changes nothing. |
| Write | Everything above, plus editing the draft: blocks and appearance. |
| Publish | Everything above, plus publishing. Give it only to a token you trust with a live page. |
A token can also be tied to specific pages. A call against a page outside its list comes back rejected, whatever its scope.
How often
Every token allows 60 calls a minute, plus a quota per day that comes from your plan. Going over the minute cap answers with a limit error and clears on its own inside that minute. Going over the daily quota stops the calls until the counter rolls over, and your panel shows how much of today is already spent. A JSON-RPC batch takes up to 20 messages.
A token also carries an expiry date, between one day and one year, and stops resolving the moment it passes. You can hold up to ten live tokens at a time.
What each plan includes
| Plan | Weight per day |
|---|---|
| No plan | Not included |
| Standard | 1,000 |
| Business | 10,000 |
| Studio | 10,000 |
| During the trial | 200 |
What counts is weight, not turns: a read costs one and a write costs five. During the trial the ceiling is lower whatever your plan says, the same way it is for messages.
What stays outside
- Billing, subscriptions and anything that moves money.
- Roles, permissions and verification.
- Deleting your account or your data.
- Replying to the people who write to you.
- Any page that is not yours.
None of this is held back by a check that could be argued with. There is simply no tool for it, so there is nothing to ask for.
Every write is recorded together with the token that made it, which is what tells a change made by an assistant apart from one you made in the editor. Revoking a token cuts it off on the next call.