Submit and search Leads via the Tripleseat API's public lead form endpoint
domain: api.tripleseat.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get your account's public_key from Settings > API/Webhooks for use in unauthenticated lead submissions
POST to https://api.tripleseat.com/v1/leads/create.json?public_key=YOUR_PUBLIC_KEY with a lead[...] body including location_id and lead_form_id
GET https://api.tripleseat.com/v1/leads/search.json with query, lead_status, created_after/created_before, and site_id parameters to find leads
PUT https://api.tripleseat.com/v1/leads/{id}.json to attach lead sources or update contact_preference and other fields
Respect the 10 requests/second rate limit that applies specifically to the /v1/leads and /v1/leads/search endpoints
Known gotchas
Forgetting to change the URL to the /create.json?public_key=... form (vs. the standard /v1/leads.json path) is the most common integration mistake and produces a 404
Omitting location_id on a multi-location site returns an explicit "Location ID can not be blank" error, but omitting lead_form_id silently succeeds with 200 OK and no form attribution
The Leads endpoints have their own 10 req/sec rate limit, separate from other Tripleseat API limits
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?