Implement the Whatnot Seller API OAuth 2.0 authorization code flow to request scoped access to a seller's Whatnot account
domain: developers.whatnot.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register a client app with Whatnot to receive a client secret and register one or more redirect URIs
Redirect the seller to Whatnot's authorization endpoint to approve or deny the requested scopes
Handle the redirect callback containing the authorization code
Exchange the authorization code at the token endpoint for an access token and refresh token
Store the refresh token securely and use the refresh_token grant to obtain new access tokens before the current one expires
Known gotchas
Refresh tokens are valid for about 1 year and each refresh call invalidates and reissues a new refresh token that must be re-stored
The app is only granted the maximum scopes needed for its stated features (for example read:inventory plus write:inventory), and can request narrower per-user scopes
Access tokens use a distinct prefix in staging versus production, so environment mismatches are easy to spot
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?