Acquire an OAuth bearer token and scope requests to a location for the PAR Pay Service API
domain: developers.partech.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Complete brand onboarding with a Punchh/PAR representative before attempting any Pay Service calls, since the service requires account provisioning first
POST to the oauth/token endpoint to obtain a JWT bearer token for your onboarded application
Send Authorization: Bearer <JWT> on every subsequent Pay Service request
Include an X-LocationId header on requests to scope gift card/payment operations to the correct restaurant location
Re-request the token before it expires rather than reusing an expired JWT, and treat 401 responses as a signal to re-authenticate rather than retry the same call
Known gotchas
Onboarding is a manual, human-in-the-loop step via a Punchh/PAR rep — this is not fully self-service like typical OAuth client registration
Location scoping is done via a header (X-LocationId), not a path segment or body field, and omitting it will misapply or fail the operation rather than defaulting sensibly
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?