REFERENCE / DYNAMIC REST ROUTES

A consistent shape for every container.

The project path chooses the context. schemaName chooses the model. The HTTP method and route choose the operation.

REQUEST ANATOMY

Read one URL. Understand the pattern.

https://YOUR_API_HOST/api/v1/{tenantSlug}/{projectSlug}/dynamic/page
  ?schemaName=orders&page=1&limit=20

Part	Meaning
YOUR_API_HOST	The origin of your AutoTable deployment
tenantSlug / projectSlug	The namespace for your project
dynamic	The schema-driven route group
page	The paginated-list operation
schemaName=orders	The target container
page / limit	Pagination parameters

Route availability, validation, authentication, and authorization follow the target container configuration.

RECORD OPERATIONS

The record lifecycle.

POST   /dynamic?schemaName=orders
GET    /dynamic/page?schemaName=orders&page=1&limit=20
GET    /dynamic/{recordId}?schemaName=orders
PATCH  /dynamic/{recordId}?schemaName=orders
DELETE /dynamic/{recordId}?schemaName=orders

POST creates a record. PATCH changes supplied fields. The record ID is the saved _id, not the orderNumber field.

PATCH /dynamic/{recordId}?schemaName=orders
Content-Type: application/json
Authorization: Bearer YOUR_TOKEN

{ "status": "paid" }

QUERIES & EXECUTION

Beyond a single record.

AutoTable also provides search, filtering, bulk operations, and saved logic routes. The configured container determines which operations are active.

Need	Route pattern
Paginated records	GET /dynamic/page?schemaName=orders
Text search	GET /dynamic/search?schemaName=orders
Typed filters	GET /dynamic/filter?schemaName=orders
Bulk creation	POST /dynamic/multiple?schemaName=orders
Manual workflow	POST /dynamic/workflow/{name}?schemaName=orders

Search/filter parameters and workflow payloads depend on the operation and saved definition. Inspect those definitions in Tenant Panel instead of assuming a common payload.

RESPONSES & ERRORS

Handle the boundary.

Check the HTTP status before reading an operation result. Create operations return an envelope with data; paginated list routes return items and pagination information.

Situation	What to check
Invalid payload	Field types, required fields, enums, validation response
Authentication failure	Session/token validity and route authentication setting
Authorization failure	Configured role requirements for the operation
Missing data or route	Tenant, project, schemaName, record ID, and route availability

Validate and handle error responses in your client. Never assume a non-success response has the same shape as a successful list.

▦ AutoTable