Authenticate to the Weeztix API and keep bearer tokens fresh for a long-running integration
domain: weeztix.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Set up the authentication flow described in Weeztix's docs to acquire an initial access/refresh token pair.
Send the access token as a Bearer token in the Authorization header on subsequent API calls.
Refresh the token before expiry using the documented refresh flow rather than waiting for a 401.
Reference the official PHP, Go, and Node code examples in the docs portal for a working implementation pattern.
Known gotchas
Public material for the older Eventix product name pointed developers to apiteam@eventix.io for full API documentation access — that support channel is a reasonable fallback if the self-serve docs are incomplete for your use case.
An access token is scoped to one or more specific companies at issuance — request it with the right company scope up front, since a token isn't automatically account-wide across every company you manage.
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?