Concepts
Organization
Section titled “Organization”The tenancy and billing boundary. You invite members (owner, admin, member), optionally use teams and permission groups, and create projects inside an org.
Project
Section titled “Project”The unit that hosts every product: data API, hosting, git, analytics, and so on. Every data-API URL includes the project ID:
https://api.tefily.com/api/p/{projectId}/{tableName}Collection (schema)
Section titled “Collection (schema)”A named table you define in Kallax. Metadata (name, fields, endpoints, rules) lives in the platform database. Documents live in MongoDB. The collection name in the URL is the table name, for example posts.
Every document includes system fields you do not add yourself:
| Field | Type | Meaning |
|---|---|---|
_id |
string | Document id |
_createdAt |
datetime | Created at |
_updatedAt |
datetime | Last update |
Endpoint
Section titled “Endpoint”A generated HTTP method on a collection: list, get, create, update, delete, plus file methods upload, download, fileDelete. Disabled endpoints return an error even if the caller is authenticated.
Access rule
Section titled “Access rule”A sequential allow/deny check on an endpoint. Typical pattern: requireAuth, then userFieldCompare so each user only sees their own rows. Platform JWTs, personal access tokens, and service tokens bypass rules on the data API.
See Access rules.
Dual APIs
Section titled “Dual APIs”| Prefix | Who calls it | Typical credential |
|---|---|---|
/api/... |
Console, admin SDK, MCP | Platform JWT or kfx_… |
/api/p/:projectId/... |
Your apps | Project JWT, or kfxs_… on a server |
The admin SDK talks to /api/.... The client SDKs talk to /api/p/....