Resources

1. Navigate to Endpoints in the dashboard.
2. Click Create resource to open the creation wizard. Define a Resource (e.g. todos) and add typed fields.
3. Optionally paste seed records to populate initial data on creation, or add them later.
4. Five live CRUD endpoints are automatically generated inside a dedicated resource folder under your root path (e.g. /todos).

Generated endpoints are instantly active. If you already have a manual endpoint exactly duplicating a generated route (same method and path), the manual route will take precedence.

For a resource with slug todos:

Every success returns a { data } envelope (lists add meta); every failure returns { error: { code, message, details? } }. Records carry an integer id (sequential per resource), createdAt, and updatedAt. PUT/POST rejects unknown, immutable, and invalid fields. DELETE is permanent.

# Create
curl -X POST "https://<your-slug>.<host>/todos" \
  -H "Content-Type: application/json" \
  -d '{"title":"Buy milk","done":false}'

# Response: 201
{ "data": { "id": 1, "title": "Buy milk", "done": false,
            "createdAt": "2026-07-01T09:00:00.000Z",
            "updatedAt": "2026-07-01T09:00:00.000Z" } }

// JavaScript
const res = await fetch("https://<your-slug>.<host>/todos", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({ title: "Buy milk", done: false }),
});
const { data } = await res.json();

• page (default 1) and limit (default 20, max 100).
• sort = one declared field; order = asc | desc (stable id tie-break).
• Equality: filter[field]=value.
• Operators: filter[field][gt|gte|lt|lte|ne]=value, cast by the field's declared type.
• Only declared fields are filterable/sortable; unknown fields → validation_error.

Responses include meta = { page, limit, total, totalPages } and an X-Total-Count header.

curl "https://<your-slug>.<host>/todos?\
page=1&limit=20&sort=createdAt&order=desc&\
filter[done]=false&filter[priority][gte]=3"

Seed records give a resource starting data with stable integer IDs. Seeds reserve the low IDs, so the first created record continues from max(seed id) + 1.

Reset (accessible in the UI) deletes all live records for a resource, restores its seed records, and rewinds the ID counter. You can trigger a reset from the resource folder's context menu (the **...** menu in the endpoints tree) or by clicking **Reset to initial data** inside the **Data** tab of any generated endpoint.

CORS defaults to allow-all (*). You can configure individual CORS settings per generated endpoint in the editor's authentication settings. Preflight (OPTIONS) requests are handled automatically.

• 25 resources per workspace, 50 fields per resource.
• 10,000 live records per workspace.
• 64 KiB per record.
• At the record cap, create returns 409 quota_exceeded — no silent purge.
• Abuse limits on generated reads/writes return 429 when exceeded.

{ "error": { "code": "validation_error",
             "message": "Unknown field: colour",
             "details": { "field": "colour" } } }

Mark a field sensitive to keep its values out of the Request History (Inspector). Sensitive values are redacted from both the logged request and response bodies; the served response is unchanged. Redaction only protects your Inspector logs — it does not encrypt or hide data from API callers.