Overview
Two ways in, both scoped to your company: its events, guests, leads, Day-of status and business totals.
Plain JSON over HTTPS for your own code, scripts, Make and n8n.
REST referenceA signed POST when a lead comes in, a guest replies, an event is booked, a song is requested or feedback arrives.
Webhook guide| What | URL | Auth |
|---|---|---|
| REST API | https://app.tablescape.vip/api/v1/... | Authorization: Bearer <key> |
| OpenAPI spec | https://app.tablescape.vip/api/v1/openapi.json | None |
Quick start
- Sign in at app.tablescape.vip as a company owner or admin.
- Open the Team page and find the Integrations card. Create a key under API keys, give it a label you’ll recognize (for example “Zapier”) and choose Read only or Read and add.
- Copy the key. It looks like
tsk_followed by 64 letters and numbers, and it’s shown once. Tablescape keeps only a hash, so store it somewhere safe. - Make your first call:
curl https://app.tablescape.vip/api/v1/me \
-H "Authorization: Bearer tsk_your_key"
{
"company": { "name": "Rosewood Events", "slug": "rosewood" },
"key": { "label": "Zapier", "scope": "read" },
"today": "2026-10-22"
}
Read and write keys
| A key can | Read (default) | Write |
|---|---|---|
| Read events, guests, leads, Day-of status and totals | Yes | Yes |
| Log a new lead or mark a lead handled | No | Yes |
| Add guests or record an RSVP | No | Yes |
| Delete anything | No | No |
A company can have up to 20 active keys. Use one key per tool, so you can revoke one without breaking the others.
REST API
JSON over HTTPS. Send your key in the Authorization header on every call.
Base URL: https://app.tablescape.vip/api/v1. Dates are YYYY-MM-DD. Errors come back as {"error": {"code", "message"}} with the HTTP status (see Errors and limits). Success is HTTP 200, except POST /inquiries (201) and the two POST routes under an event (202), so treat any 2xx status as success.
All routes
| Method and path | Key | What it does |
|---|---|---|
GET /api/v1/me | Read | Your company and this key (example) |
GET /api/v1/events | Read | List events |
GET /api/v1/events/{id} | Read | Get one event |
GET /api/v1/events/{id}/guests | Read | List guests |
POST /api/v1/events/{id}/guests | Write | Add guests |
POST /api/v1/events/{id}/rsvp | Write | Record an RSVP |
GET /api/v1/events/{id}/day-of | Read | Day-of status |
GET /api/v1/inquiries | Read | List inquiries |
POST /api/v1/inquiries | Write | Log a new inquiry |
PATCH /api/v1/inquiries/{id} | Write | Mark an inquiry handled |
GET /api/v1/summary | Read | Business summary |
GET /api/v1/openapi.json | None | OpenAPI 3.1 spec |
GET/api/v1/eventslist_events
Without from or to, upcoming events come first (soonest first), then past events (newest first). With a date range, events are in date order. Undated events come last and archived events are left out. total is how many events match.
| Query | Values |
|---|---|
status | inquiry, proposal, booked, completed, hold or cancelled |
from, to | Dates, YYYY-MM-DD |
q | Text to search for, such as a name or venue |
limit | 1 to 100, default 25 |
curl "https://app.tablescape.vip/api/v1/events?status=booked&from=2026-10-01&to=2026-10-31" \
-H "Authorization: Bearer tsk_your_key"
{
"events": [
{
"id": "emgx4k2q8a7d3kf",
"name": "Rosa's Quinceañera",
"date": "2026-10-24",
"venue": "Rosewood Hall",
"status": "booked",
"type": "quince",
"guests": 180,
"tables": 18,
"budget": 18500,
"client_name": "Maria Lopez",
"balance_due": 4200,
"next_payment": { "label": "Final payment", "due": "2026-10-17", "amount": 4200 }
},
{
"id": "emh1c7w3n5tq2bx",
"name": "Chen and Park Wedding",
"date": "2026-10-31",
"venue": "Juniper Gardens",
"status": "booked",
"type": "wedding",
"guests": 140,
"tables": 15,
"budget": 32000,
"client_name": "Grace Chen",
"balance_due": 8650,
"next_payment": { "label": "Final payment", "due": "2026-10-24", "amount": 8650 }
}
],
"total": 2
}
GET/api/v1/events/{id}get_event
One event in full. meals counts the guests who haven’t declined. links.website is the event website (until 60 days after the event). links.staff is the Day-of staff link, which can check guests in, so only write keys get it (until 7 days after the event). Client links, guest codes and vendor codes are never returned.
curl https://app.tablescape.vip/api/v1/events/emgx4k2q8a7d3kf \
-H "Authorization: Bearer tsk_your_key"
{
"id": "emgx4k2q8a7d3kf",
"name": "Rosa's Quinceañera",
"date": "2026-10-24",
"venue": "Rosewood Hall",
"status": "booked",
"type": "quince",
"theme": "Rose gold princess",
"client": { "name": "Maria Lopez", "email": "maria@example.com", "phone": "(909) 555-0142" },
"guests": { "invited": 180, "yes": 142, "no": 11, "pending": 27 },
"meals": { "Filet": 88, "Salmon": 41, "Vegetarian": 13, "not chosen": 27 },
"tables": 18,
"budget": 18500,
"payments": [
{ "label": "Deposit", "due": "2026-06-01", "amount": 5000, "paid": true },
{ "label": "Second payment", "due": "2026-09-01", "amount": 9300, "paid": true },
{ "label": "Final payment", "due": "2026-10-17", "amount": 4200, "paid": false }
],
"balance_due": 4200,
"timeline": [
{ "time": "6:00 PM", "label": "Guests arrive" },
{ "time": "7:00 PM", "label": "Grand entrance" },
{ "time": "7:30 PM", "label": "Dinner" },
{ "time": "8:30 PM", "label": "Waltz" }
],
"vendors": [
{ "role": "DJ", "name": "Sonido Rey", "contact": "(909) 555-0177", "arrive": "3:30 PM" }
],
"links": {
"website": "https://app.tablescape.vip/#site-emgx4k2q8a7d3kf.7Hq2xK9pLm",
"staff": "https://app.tablescape.vip/#staff-emgx4k2q8a7d3kf.Vb4nR8tWc2"
},
"updated_at": "2026-10-21T22:14:09Z"
}
Guests and RSVPs
GET/api/v1/events/{id}/guestslist_guests
Returns {"guests": [{id, name, household, party, rsvp, meal, diet, table, email, phone}], "total"}. household is the id of one invitation and party names the other guests on it. Guests added through the API that the team’s app hasn’t taken in yet are included with "pending_sync": true.
| Query | Values |
|---|---|
rsvp | yes, no or pending |
q | Text to search for in names, emails, households or phone numbers |
limit | 1 to 250, default 100 |
curl "https://app.tablescape.vip/api/v1/events/emgx4k2q8a7d3kf/guests?rsvp=pending" \
-H "Authorization: Bearer tsk_your_key"
POST/api/v1/events/{id}/guestsadd_guests
Body: {"guests": [{name, household?, email?, phone?, meal?, rsvp?}]} with 1 to 200 guests. rsvp is yes, no or pending (the default). The guests are queued and join the plan the next time the team’s app is open, with new ids. Exact duplicates (same name and email) are skipped. To add someone to an existing party, send that party’s household exactly as the guest list shows it; any other text starts a new party for the guests in this call. Returns HTTP 202 with {"queued"}, the number of guests queued. Needs a write key.
curl -X POST https://app.tablescape.vip/api/v1/events/emgx4k2q8a7d3kf/guests \
-H "Authorization: Bearer tsk_your_write_key" \
-H "Content-Type: application/json" \
-d '{"guests":[{"name":"Luis Garcia","household":"Garcia"},{"name":"Elena Garcia","household":"Garcia","meal":"Salmon"}]}'
{ "queued": 2 }
POST/api/v1/events/{id}/rsvpset_rsvp
Body: {"guest_id", "rsvp", "meal"?} where rsvp is yes or no. Leave meal out to keep the guest’s current choice. The guest must already be on the list (otherwise 404 guest not found). Returns HTTP 202 with {"id"}. Needs a write key.
curl -X POST https://app.tablescape.vip/api/v1/events/emgx4k2q8a7d3kf/rsvp \
-H "Authorization: Bearer tsk_your_write_key" \
-H "Content-Type: application/json" \
-d '{"guest_id":"k3j9x2a","rsvp":"yes","meal":"Filet"}'
GET/api/v1/events/{id}/day-ofget_day_of_status
Live numbers for the day, including staff phone updates the team’s app hasn’t taken in yet.
curl https://app.tablescape.vip/api/v1/events/emgx4k2q8a7d3kf/day-of \
-H "Authorization: Bearer tsk_your_key"
{
"event_id": "emgx4k2q8a7d3kf",
"checked_in": 142,
"expected": 169,
"vendors_arrived": 5,
"vendors_total": 6,
"tasks_done": 23,
"last_update_at": "2026-10-24T19:42:17Z"
}
Inquiries
GET/api/v1/inquirieslist_inquiries
Newest first. status is open (the default), handled or all; limit is 1 to 100, default 25. Each inquiry has id, created_at, handled, name, email, phone, type, event_name, date, venue, guests, budget, source and notes.
curl "https://app.tablescape.vip/api/v1/inquiries?status=open&limit=10" \
-H "Authorization: Bearer tsk_your_key"
POST/api/v1/inquiriescreate_inquiry
Body: {name, email, phone?, type?, event_name?, date?, venue?, guests?, budget?, notes?}. A name and a valid email are required. It arrives exactly like a website inquiry, marked with source api, so alerts and the CRM work as usual. No auto-reply email goes to that address, since the person never filled in the form. Returns HTTP 201 with {"id"}. Needs a write key.
curl -X POST https://app.tablescape.vip/api/v1/inquiries \
-H "Authorization: Bearer tsk_your_write_key" \
-H "Content-Type: application/json" \
-d '{"name":"Ana Ruiz","email":"ana@example.com","type":"baby shower","date":"2027-05-08","guests":60,"notes":"Found us on Instagram"}'
PATCH/api/v1/inquiries/{id}update_inquiry
Body: {"handled": true} or {"handled": false}. Returns {"id", "handled"}. Needs a write key.
curl -X PATCH https://app.tablescape.vip/api/v1/inquiries/b2e7c0d4-8f3a-4e61-a9d2-5c1b7e9f0a34 \
-H "Authorization: Bearer tsk_your_write_key" \
-H "Content-Type: application/json" \
-d '{"handled":true}'
GET/api/v1/summaryget_business_summary
The state of the business between from and to (default: today in your time zone to 90 days ahead). Money is in whole dollars. new_leads lists inquiries from the last 30 days with no reply logged.
curl "https://app.tablescape.vip/api/v1/summary?from=2026-10-01&to=2026-12-31" \
-H "Authorization: Bearer tsk_your_key"
{
"from": "2026-10-01",
"to": "2026-12-31",
"events_by_status": { "inquiry": 6, "proposal": 3, "booked": 9, "hold": 1 },
"upcoming": [
{ "id": "emgx4k2q8a7d3kf", "name": "Rosa's Quinceañera", "date": "2026-10-24", "status": "booked", "guests": 180 }
],
"booked_revenue": 186400,
"collected": 121750,
"outstanding": 64650,
"payments_due": [
{ "event_id": "emgx4k2q8a7d3kf", "event": "Rosa's Quinceañera", "label": "Final payment", "due": "2026-10-17", "amount": 4200 }
],
"open_inquiries": 0,
"new_leads": [
{ "id": "emk2p9r4d1vx8ca", "name": "Wedding · Ana Ruiz", "date": "2027-06-12", "client_name": "Ana Ruiz", "inquired_at": "2026-10-21T18:04:11Z" }
]
}
GET/api/v1/openapi.json
The OpenAPI 3.1 spec for every route above. No key needed. Import it into Postman, Insomnia or a code generator.
curl https://app.tablescape.vip/api/v1/openapi.json
Webhooks
Get a signed POST the moment something happens, in Zapier, Make, n8n, Slack, Discord or your own server.
- On the Team page, in the Integrations card, add a webhook URL and pick the events it should get (or all of them).
- Tablescape gives the webhook its own signing secret. Use it to verify each delivery.
- Press Send test to send a
testevent. The card shows the last 5 deliveries and their status.
Up to 10 webhooks per company. The URL must use https:// on port 443 with a public host name (no IP addresses or local names such as localhost), up to 500 characters.
Events
| Event | Sent when |
|---|---|
lead.created | A new inquiry arrives, from your website form or the API |
rsvp.received | A guest replies |
event.booked | An event’s status becomes booked |
song.requested | A guest requests a song on the event website |
feedback.received | A client sends feedback after the event |
test | You press Send test in the Integrations card |
* | Subscribe to all of the above |
Headers and payload
| Header | Value |
|---|---|
Content-Type | application/json |
User-Agent | Tablescape-Webhooks/1.0 |
X-Tablescape-Event | The event type, for example lead.created |
X-Tablescape-Delivery | A unique id for this delivery |
X-Tablescape-Signature | sha256= and the hex HMAC-SHA256 of the raw body, keyed with the webhook’s secret |
{
"id": "6c1f2a9e-41d7-4c2b-9a53-0f6f1d2c8b10",
"type": "lead.created",
"created_at": "2026-10-23T18:04:11Z",
"company": { "name": "Rosewood Events", "slug": "rosewood" },
"data": {
"inquiry_id": "b2e7c0d4-8f3a-4e61-a9d2-5c1b7e9f0a34",
"name": "Maria Lopez",
"email": "maria@example.com",
"type": "wedding",
"date": "2027-06-12",
"guests": 150
},
"text": "New lead: Maria Lopez, wedding on Jun 12, 2027 for 150 guests",
"content": "New lead: Maria Lopez, wedding on Jun 12, 2027 for 150 guests"
}
Deliveries go out right after the change. A failed delivery never blocks or undoes the change that caused it. Reply with a 2xx status quickly and do slow work afterward. Tablescape waits up to 5 seconds for an answer and does not retry, so a delivery that fails is not sent again. The Integrations card shows each delivery’s response for about 6 hours. Use the REST API (GET /api/v1/inquiries?status=all, since the team’s app marks new leads handled within moments) to catch up after downtime.
Verify signatures
Compute the HMAC over the raw request body, byte for byte, before any JSON parsing, and compare it in constant time. Parsing and re-serializing the JSON changes the bytes and breaks the signature.
Node.js (Express)
import crypto from 'node:crypto';
import express from 'express';
const app = express();
const SECRET = process.env.TABLESCAPE_WEBHOOK_SECRET;
// express.raw keeps the body as the exact bytes Tablescape signed.
app.post('/tablescape', express.raw({ type: 'application/json' }), (req, res) => {
const expected = 'sha256=' +
crypto.createHmac('sha256', SECRET).update(req.body).digest('hex');
const given = req.get('X-Tablescape-Signature') || '';
const ok = given.length === expected.length &&
crypto.timingSafeEqual(Buffer.from(given), Buffer.from(expected));
if (!ok) return res.status(401).send('bad signature');
const event = JSON.parse(req.body.toString('utf8'));
console.log(event.type, event.text);
res.sendStatus(200);
});
app.listen(3000);
Python (Flask)
import hashlib
import hmac
import json
import os
from flask import Flask, abort, request
app = Flask(__name__)
SECRET = os.environ["TABLESCAPE_WEBHOOK_SECRET"].encode()
@app.post("/tablescape")
def tablescape():
raw = request.get_data() # the exact bytes Tablescape signed
expected = "sha256=" + hmac.new(SECRET, raw, hashlib.sha256).hexdigest()
given = request.headers.get("X-Tablescape-Signature", "")
if not hmac.compare_digest(given, expected):
abort(401)
event = json.loads(raw)
print(event["type"], event["text"])
return "", 200
Slack, Discord and automation tools
text (read by Slack) and content (read by Discord), so the message shows up as is. Pick only the events you want in that channel.For Zapier, start a Zap with Webhooks by Zapier and the Catch Hook trigger (Webhooks by Zapier needs a paid Zapier plan). In Make, add a Custom webhook. In n8n, add a Webhook node, set its HTTP Method to POST, use its Production URL and activate the workflow (the Test URL only listens while you click Listen for test event). Paste the URL each one gives you into Tablescape, press Send test, and map the fields from the sample. To act back on Tablescape from those tools, call the REST API with a key in the Authorization header.
Errors and limits
REST errors look like {"error": {"code": 404, "message": "event not found"}}.
| Status | Message | What it means |
|---|---|---|
| 400 | bad request: ... | A value is missing or invalid. The message says which. |
| 401 | invalid api key | The key is missing, wrong or revoked. |
| 403 | this key is read-only | A write call was made with a read key. |
| 404 | event not found, guest not found, inquiry not found | Nothing with that id in your company. |
| 429 | rate limit | More than 1000 calls this clock hour with this key, or more than 200 leads logged through the API in the last hour. Wait the number of seconds in the Retry-After header. |
| Limit | Value |
|---|---|
| Calls per key | 1000 per clock hour |
| Leads logged through the API | 200 per company per hour |
| Active keys per company | 20 |
| Webhooks per company | 10 |
| Guests per add_guests call | 1 to 200 |
| Guests per event | 2000 |
| Page size | Events and inquiries up to 100, guests up to 250 |
Security
- Keys are shown once. Tablescape stores only a SHA-256 hash, so a lost key can’t be recovered. Create a new one and revoke the old one.
- Read-only by default. A write key can add guests, record RSVPs, log leads and mark leads handled. No key can delete anything.
- Revoke any time in the Integrations card. A revoked key stops working on its next call.
- One company per key. A key only ever sees its own company. Responses never include client links, guest codes or vendor codes.
- Signed webhooks. Each webhook has its own secret. Check
X-Tablescape-Signaturebefore you trust a delivery. - Good habits. One key per tool, a read key wherever you can, and keys in environment variables rather than in code or shared files.