Waymark / Routes / developers.lightspeedhq.com Authenticate to the Lightspeed Retail (R-Series) API with OAuth 2.0 and stay under rate limits
domain: developers.lightspeedhq.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Register an app in the Lightspeed Retail (R-Series) developer portal to obtain a Client ID and Client Secret Redirect the merchant through the OAuth 2.0 authorization flow so they can grant your app account access Exchange the returned authorization code for an access token and refresh token Call the account API root using the access token in the Authorization header Proactively rotate the access token using the refresh token before the short-lived token expires Watch the rate-limit response headers and back off before hitting the bucket ceiling Known gotchas Each account+client pair gets its own leaky-bucket rate-limit allowance that refills gradually, and exceeding it returns HTTP 429 Rate limit allowance scales with the number of registers on the account, so low-register accounts throttle sooner Access tokens are short-lived (on the order of minutes) — cache and rotate refresh tokens rather than re-authenticating interactively
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