QUICKSTART / BUILD THE FIRST VERTICAL SLICE
Build an orders example from a container to a working request, then connect a workflow and an interface.
01 / PROJECT & MODEL
In your Tenant Panel instance, choose the tenant and project where the application belongs. Create a container named orders with the following fields.
| Field | Type | Suggested configuration |
|---|---|---|
| orderNumber | string | Required and unique |
| status | string | Enum: draft, paid, shipped |
| total | float | Required |
These are proposed fields for this guide. Save the container before using its dynamic routes.
02 / ACCESS POLICY
Review the container route settings. Enable only the operations the application needs. Configure authentication and authorized roles separately for reads and writes.
For a private application, require authentication on record routes and configure the expected project roles. Test using the intended user session. Keep privileged credentials out of frontend code.
03 / FIRST WRITE
Run this on your own machine with your deployment values and an authorized token. The example uses shell environment variables; it does not contain a live credential.
export AUTOTABLE_BASE="https://YOUR_API_HOST/api/v1/YOUR_TENANT/YOUR_PROJECT"
# Set AUTOTABLE_TOKEN securely in your shell.
curl --fail-with-body "$AUTOTABLE_BASE/dynamic?schemaName=orders" \
-X POST \
-H "Content-Type: application/json" \
-H "Authorization: Bearer $AUTOTABLE_TOKEN" \
--data '{"orderNumber":"A-1042","status":"draft","total":184.5}'A successful create returns the saved record in data, including its _id. Save that ID when reading or updating the record.
04 / FIRST READ
curl --fail-with-body \
"$AUTOTABLE_BASE/dynamic/page?schemaName=orders&page=1&limit=20" \
-H "Authorization: Bearer $AUTOTABLE_TOKEN"{
"items": [{
"_id": "YOUR_RECORD_ID",
"orderNumber": "A-1042",
"status": "draft",
"total": 184.5
}],
"totalItems": 1,
"totalPages": 1,
"currentPage": 1
}Illustrative response. Record IDs and pagination totals depend on the data in your project.
05 / LOGIC & INTERFACE
Add an after_create workflow to orders in Tenant Panel. Begin with a simple condition and one supported action, then inspect its execution result with test data.
Connect the record route to your own frontend, or use Ozmishow to compose a page with connected content. Check reads, writes, access rules, and the workflow together before expanding the model.
A connected foundation for the things you want to build.