Lavu · Schema
Table
A floor layout table from the tables table.
RestaurantPoint-of-SalePaymentsInventoryMenu Management
Properties
| Name | Type | Description |
|---|---|---|
| id | string | Table layout identifier. |
| loc_id | string | Location identifier. |
| coord_x | string | Pipe-delimited X coordinates of each table on the floor layout. |
| coord_y | string | Pipe-delimited Y coordinates of each table on the floor layout. |
| shapes | string | Pipe-delimited shape of each table (e.g. square, circle). |
| widths | string | Pipe-delimited widths of each table. |
| heights | string | Pipe-delimited heights of each table. |
| names | string | Pipe-delimited display names of each table (e.g. Booth 1, Table 5). |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"title": "Table",
"description": "A floor layout table from the tables table.",
"$id": "https://raw.githubusercontent.com/api-evangelist/lavu/refs/heads/main/json-schema/poslavu-api-table-schema.json",
"type": "object",
"properties": {
"id": {
"type": "string",
"description": "Table layout identifier.",
"example": "3"
},
"loc_id": {
"type": "string",
"description": "Location identifier.",
"example": "9"
},
"coord_x": {
"type": "string",
"description": "Pipe-delimited X coordinates of each table on the floor layout.",
"example": "138|258|372"
},
"coord_y": {
"type": "string",
"description": "Pipe-delimited Y coordinates of each table on the floor layout.",
"example": "82|82|82"
},
"shapes": {
"type": "string",
"description": "Pipe-delimited shape of each table (e.g. square, circle).",
"example": "square|square|circle"
},
"widths": {
"type": "string",
"description": "Pipe-delimited widths of each table.",
"example": "74|70|70"
},
"heights": {
"type": "string",
"description": "Pipe-delimited heights of each table.",
"example": "69|70|70"
},
"names": {
"type": "string",
"description": "Pipe-delimited display names of each table (e.g. Booth 1, Table 5).",
"example": "Booth 1|Booth 2|Table 1"
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/poslavu-api-table"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.