TablelistPro Logo

Developers

POS Bulk Sync

2 min read

Sync POS spend into existing table reservations so CRM totals, close state, and reporting stay accurate in TablelistPro.

This guide is for POS and data integrators. In the API, table reservations are admission groups with type equal to TABLE.

Receipt sync endpoint

Use POST /2025-03/venues/{venueId}/admission-groups/bulk-receipts.

  • mode: append (default) adds new non-internal receipt lines.
  • mode: overwrite replaces non-internal receipt lines for each reservation in the request.

When multiple rows target the same reservation, rows are processed in request order. If closed is sent multiple times, the last value wins.

POS ticket sync endpoint

Use POST /2025-03/venues/{venueId}/admission-groups/bulk-pos-tickets.

  • mode: append adds tickets onto existing posTickets.
  • mode: overwrite replaces each reservation's full posTickets list with what you send.

spent is recalculated after both receipt and POS ticket sync updates.

Prerequisites

  • API key with access to the venue (x-tl-api-key)
  • venueId for the target venue
  • Existing table reservations in TablelistPro (these endpoints update existing rows)

Suggested sync flow

  1. List target reservations with GET /2025-03/venues/{venueId}/admission-groups.
  2. Build receipts or posTickets arrays from your POS export.
  3. Send rows in deterministic order when closed updates are involved.
  4. Handle partial success by checking the errors array and retrying failed indexes.

Related