tbltap

Topics

Developer docs

Partner integration reference for tbltap APIs, hosted menu links, table context, webhooks, payments, status codes, rate limits, POS, and delivery connections.

Start here

Find the right first guide

Guided setup

Start with us next to you.

Enter your email here, confirm the PIN, and the app opens the restaurant setup guide.

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.

Most likely questions

Quick answers

Can developers use production APIs today?

Only through an approved partner process. Public docs should not imply open self-serve production access until credentialing and certification are available.

What is the no-credential path?

Use hosted tbltap menu, QR, NFC, and table-tag links when an integration only needs to open the guest-facing experience.

Where are response and error examples?

Open /docs/developers and use the endpoint reference, status-code table, rate-limit section, and tbltap-developer-api-spec JSON block.

Guides

Helpful guides

EveryoneUpdated Jul 13, 2026

Build with tbltap

Developer-facing API reference for partner APIs, hosted menu links, table context, order handoff, payments, webhooks, status codes, rate limits, and POS or delivery connections.

Read
No public documents match that filter.Try searching for terms, privacy, payments, or support.
Was this helpful?