API access
Authentication
Log in at squeevio.com and open API access in the sidebar (/api-tokens). Name the token, pick its permissions, and copy the secret — it is shown exactly once.
Every request authenticates with:
Authorization: Bearer skz_...A revoked, expired, or scope-missing token gets 401; a token missing the right scope gets 403. Check the response body's error field.
Scopes
| Scope | Grants |
|---|---|
| orbio_read | Read Circlio groups, contacts, call goals, avatars |
| orbio_write | The above, plus writing groups and parsing an import list |
| read_mood | Read mood check-ins |
| read_gratitude | Read gratitude entries |
| read_urge | Read the urge log |
| read_tool_use | Read tool-use history |
| read_all | All of the read_* scopes above at once (does not include orbio_write — a read-only token can never write). |
orbio_read/orbio_write are deliberately their own pair, not folded into read_all — a token minted for a Circlio integration never unlocks mood/gratitude/urge data, and vice versa.
Squeevio — read endpoints
Four read-only endpoints, each accepting an optional ?days=N query param (default 30, max 365):
GET https://api.squeevio.com/api/v1/mood?days=30
GET https://api.squeevio.com/api/v1/gratitude?days=30
GET https://api.squeevio.com/api/v1/urge?days=30
GET https://api.squeevio.com/api/v1/tool-use?days=30{"ok": true, "entries": [...], "days": 30}Circlio — full management
Circlio (contact groups and call goals) exposes full read/write through the same tokens — see Circlio and its own dedicated API documentation with the full set of request examples.
Managing tokens
Creating or revoking a token needs a real logged-in session, not a personal token — minting/revoking is deliberately not itself delegable to another token.
GET /panel/api/me/tokens
POST /panel/api/me/tokens
DELETE /panel/api/me/tokens/<id>Questions about the API? support@squeevio.com