Get started
Build on your workspace.
Connect your tools to Squario with a versioned JSON API. Discover the schema, read data and make changes with your app permissions.
One API, your workspace
The REST API uses HTTPS and JSON. API keys belong to one member in one workspace. Your base URL already ends in /functions/v1/public-api/v1; copy it from Settings → API and append the endpoint path used in these guides. The documentation lives at /docs, alongside the Squario website.
- Authenticate with
Authorization: Bearer <API_KEY>. - Read a list in
datawith pagination information inmeta. - Read or write one record in a
dataobject. - Use
X-Request-Idto trace a request.
Permissions travel with the key
Every operation acts as the member who created the key. Workspace membership, resource permissions and field restrictions are checked on the server. A key’s read/write access, resource allowlist and IP allowlist can narrow that access. They cannot expand it.
REST API or MCP
Both connections use the same resource action core. Choose REST for an integration that you control, or MCP to connect an AI client with the member’s consent.
| Connection | Credential | Best fit | Usage |
|---|---|---|---|
| REST API | Member API key | Server integrations, imports and synchronisation | Monthly API request allowance |
| MCP | OAuth 2.1 grant | Remote AI clients and assistants | Workspace AI credits |
Start with a read
Make a request to /me, discover the resources your key covers, then describe the resource you need. Its live schema includes your workspace’s custom fields. The endpoint reference documents every route and its request and response schemas.