GET /api/v1/public/menu/items
Reads tenant-scoped menu items with explicit limit and cursor parameters. Requires public.read plus menu.read.
API Reference.
Implemented public API endpoints, scopes, pagination and error boundaries for Limvero integrations.
Public claim boundary
Limvero public pages describe implemented product capabilities and marked roadmap items honestly. Certification, fiscal, payment, marketplace, uptime and customer-logo claims appear only when those facts are real and documented.Implemented endpoints
The public reference describes only endpoints that are implemented and guarded by scoped API keys.
GET /api/v1/public/orders
Reads tenant-scoped order lists with bounded filters and cursor pagination. Requires public.read plus orders.read.
Request rules
Integrations should be bounded, tenant-scoped and explicit about pagination and error handling.
Cursor pagination
List clients must send an explicit limit, process the current page and continue only while pagination.hasMore is true using pagination.nextPageToken as the next cursor.
Tenant boundary
API keys are scoped to one tenant. Public endpoints do not allow a key to read another restaurant tenant.
Scope boundary
Every declared endpoint scope is required. A read endpoint does not accept a key that has only one of the required scopes.
Error model
400 means validation failure, 401 invalid key, 403 missing scope, 404 outside tenant boundary and 429 rate limit exceeded.
Provider boundary
Write-heavy delivery, acquiring, fiscal and marketplace sync are provider-specific integration projects until implemented.
No production try-it
Public pages do not expose a live production OpenAPI try-it console. Use customer-approved credentials only in controlled environments.
API keys use the production prefix format in examples, but examples are non-secret placeholders and must not be copied as real credentials.
Plan a clean restaurant rollout.
Talk through locations, POS devices, kitchen workflow, menu migration, API needs and security review before launch.