Obtain a WHCC Order Submit API access token to authenticate print-order requests
domain: whcc.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get an API key and secret from WHCC by requesting partner/developer access via the WHCC Developer site
Call the Order Submit API's Request Access Token endpoint with your key/secret credentials
Store the returned bearer token for use in the Authorization header of subsequent Order Import/Submit calls
Prefer the simpler Access Token flow unless you specifically need the OAuth login-page flow for end-user credential capture
Refresh the token before it expires rather than waiting for a request to fail
Known gotchas
WHCC exposes two distinct auth flows (plain Access Token vs OAuth); the OAuth flow is meant for presenting an end-user login page, not simple server-to-server calls
Order Submit API tokens are separate from Editor API tokens — a token from one does not work with the other
Credentials/tokens are tied to a specific WHCC account; requesting the wrong scope can produce orders billed to the wrong account
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?