Authenticate to the Digitail API using OAuth 2.0 authorization code with PKCE
domain: documentation.digitail.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register your application and obtain client credentials via Digitail's API access request form before implementing OAuth
Generate a code_verifier (43-128 char random string), derive a code_challenge as the base64url-encoded SHA-256 hash of it, and generate a random state value
Redirect the user to https://vet.digitail.io/oauth/authorize with response_type=code, client_id, client_secret, redirect_uri, state, code_challenge, and code_challenge_method=S256
On callback, exchange the returned code (valid for only 10 minutes) for an access token by POSTing grant_type=authorization_code, client_id, client_secret, redirect_uri, code_verifier, and code to https://vet.digitail.io/oauth/token
Store the returned access_token, refresh_token, and expires_in, and use the access token as a bearer credential on subsequent API calls
Known gotchas
The authorization code is valid for only 10 minutes - exchange it for a token immediately rather than queuing the exchange
The code_verifier and state must be generated and stored client-side before redirecting, and reused exactly when exchanging the code, per PKCE requirements
Digitail issues separate credentials per environment - sandbox credentials will not work against the production OAuth 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?