Voice agents + real inventory
ElevenLabs integration API
Give each restaurant’s AI phone agent a scoped key to check dates, see real tables, make reservations, and stay synchronized.
Authentication
Create a key in Dashboard → Restaurant → Integration. Send it as a Bearer token with every request.
Authorization: Bearer tr_your_restaurant_key Content-Type: application/json Base URL: https://tableres.com/api/v1
Restaurant details
GET /restaurant
Available dates
GET /availability/dates?party_size=2&days=30
Returns only dates with at least one genuinely available table and service slot.
Available times and tables
GET /availability?date=2026-11-20&party_size=2 GET /tables?date=2026-11-20&party_size=2 GET /tables?starts_at=2026-11-20T19:00:00.000Z&party_size=2
Create a booking
POST /reservations
{
"guest_name": "Alex Morgan",
"guest_email": "alex@example.com",
"guest_phone": "+1 555 0100",
"party_size": 2,
"starts_at": "2026-11-20T19:00:00.000Z",
"notes": "Window seat if available"
}Use the exact starts_at returned by availability. The booking write re-checks inventory atomically; if another channel took the last table, the API returns an error instead of double-booking.
View, cancel, and synchronize
GET /reservations/{confirmation_code}
DELETE /reservations/{confirmation_code}
GET /reservations?since=2026-11-19T00:00:00.000Z&limit=100For sync, save next_since after every successful response and pass it as since on the next poll. The response includes new and changed reservations, cancellations, guest details, assigned table labels, and timestamps.
ElevenLabs tool setup
Create server tools/webhooks in your ElevenLabs agent for each operation above. Use a separate secret per restaurant and never put the key in the agent’s spoken prompt or client-side code. Map the tool responses to natural language: available dates → offer dates; slots → offer times; booking confirmation → read back the restaurant, time, party size, and confirmation code.