Configure a Mariana Tek webhook subscription for reservation and check-in events, choosing between API-key and OAuth2 (PKCE) authentication depending on whether the integration acts as a confidential service account or an end-user-facing app.
domain: guides.marianatek.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Decide whether the integration should authenticate as a service account (API key) or as an end user (OAuth2 Authorization Code, or Authorization Code + PKCE for public/native apps).
Register credentials accordingly per the Mariana Tek Credentials guide.
Request a webhook subscription by providing an HTTPS subscriber URL and the specific event types (e.g. customer created, reservation made, check-in) to receive.
Implement the webhook receiver to handle Mariana Tek's event POSTs instead of polling the Customer/Admin APIs for changes.
Validate incoming webhook payloads and cross-reference the Customer API for detail not included in the event body.
Known gotchas
API-key auth ties requests to a service account while OAuth2 ties them to an end user — picking the wrong model can leak or scope data incorrectly.
The subscriber URL must be HTTPS; Mariana Tek will not deliver webhooks to plain HTTP endpoints.
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?