Integration surfaces
tbltap developer docs separate no-code hosted links from credentialed partner APIs, then show concrete response examples, status codes, and rate-limit behavior for the partner path.
- Hosted public menu, QR, NFC, and table-tag links can be shared without API credentials.
- Partner APIs require approved scopes, sandbox credentials, webhook signing, and production certification.
- Reference sections document 200 success responses, 4xx/5xx failures, 429 rate-limit headers, and stable error envelopes.
- Operational integrations must preserve payment, fulfillment, customer-data, and media-safety contracts.