DEVELOPERS / A DIRECT WAY IN
Use HTTP and JSON to build on AutoTable. Start with one container, make a request, and connect your preferred client.
START HERE
Go from a small orders definition to a first read and write request.
THE ROUTES
Understand the base URL, schemaName, record IDs, and operation patterns.
THE BOUNDARY
Keep credentials server-side and test the route policy your project actually needs.
JAVASCRIPT EXAMPLE
Replace the origin, tenant, and project with your deployment values. Use an authorized server-side token when the route requires authentication.
const base = "https://YOUR_API_HOST/api/v1/YOUR_TENANT/YOUR_PROJECT";
const response = await fetch(
`${base}/dynamic/page?schemaName=orders&page=1&limit=20`,
{
headers: { Authorization: `Bearer ${process.env.AUTOTABLE_TOKEN}` },
},
);
if (!response.ok) throw new Error(`AutoTable: ${response.status}`);
const page = await response.json();
console.log(page.items);Run authenticated examples on a server. Browser applications should use an appropriate user session or a server endpoint; never ship a privileged project token in a public bundle.
A SMALL VOCABULARY
The same concepts carry from your first request to a connected application.
CONTAINER
A named schema with typed fields, validation, and configured operations.
TENANT + PROJECT
The namespace in the API path that identifies the target project.
SCHEMANAME
The query parameter that chooses which container an operation uses.
WORKFLOW
Triggered or manually invoked logic with configured conditions and steps.
PIPELINE
A saved transformation that returns data in the shape your application needs.
VISUAL DOCUMENT
An editable tree of supported Ozmishow nodes used to compose a section.
LESS DISTANCE BETWEEN IDEA AND PRODUCT
Define the data. Connect the logic. Build the experience.
A connected foundation for the things you want to build.