Refresh an expired or expiring Accela Construct API OAuth2 access token using the authorization-code flow's refresh token
domain: developer.accela.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm the app was authorized via the Authorization Code Flow, since the Implicit Flow does not issue refresh tokens at all
Store the refresh_token returned alongside the original access_token from the initial code exchange
Before or after the access token expires, POST to https://auth.accela.com/oauth2/token with the refresh_token to obtain a new access_token
Update the app's stored access token with the new value and continue calling Construct API endpoints as normal
If a refresh token itself becomes invalid, generate a new one via the Accela Admin Portal (or, on v4.4.9+, the Construct admin portal) per application and agency
Known gotchas
Apps using the Implicit Flow cannot refresh tokens by design and must re-authenticate the user instead
Refresh tokens are managed per application per agency; revoking or regenerating one in the Admin Portal invalidates prior refresh tokens for that app/agency pair
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?