Determine realistic API access paths for OpenTable and Resy reservation data before committing to either as an integration partner
domain: opentable.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
For OpenTable, apply through its public API Partners program (Become a Partner application); approval is required, but the application process itself is publicly documented and self-initiated
After OpenTable approval, expect sandbox access followed by a certification step before production reservation-management API access is granted
For Resy, understand there is no public self-serve developer portal or published OpenAPI spec — access is restricted to approved partners (POS, CRM, loyalty, marketing, discovery) under a direct partnership agreement negotiated with Resy's partnerships team
If a use case only needs availability/reservation display rather than write access, evaluate whether a widget/booking-button embed (rather than a full API integration) meets the requirement with far less gating
Budget partnership negotiation time for Resy specifically — treat 'get a Resy API key' as a business-development task, not a developer signup form
Known gotchas
OpenTable's application process being public doesn't mean approval is guaranteed or fast — it's still a partnership review, not instant key issuance
Resy has essentially no public technical on-ramp; don't scope a project assuming you can self-serve a sandbox key the way you might with OpenTable or many delivery APIs
Booking-button/widget embeds (no API access needed) are a legitimate fallback for simple reservation display/CTA use cases when full API partnership isn't feasible
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?