INDEPENDENT DEVELOPER REFERENCE
Why am I getting a 401 or 403?
A 401 means the Bearer key is missing, malformed, invalid or revoked. A 403 means the key worked but a boundary applied: a rejected origin, DFS redistribution permission, or a delivery feature your plan lacks. Read the message field, then fix the key or check the plan.
Editorial review: · Not a live coverage report
Check these first
The header must read exactly Authorization: Bearer dk_ plus 64 hexadecimal characters. Keys in query strings are not accepted. Watch for quotes or a trailing newline from an environment file. A delivery 403 reads either Developer or Production subscription required or Production subscription required.
curl -i "https://draftkingsapi.com/api/v1/coverage" \
-H "Authorization: Bearer $DRAFTKINGS_API_KEY"Check the recorded data
Related resources
What each status means, what counts against your plan, when limits reset, and how to write retry logic that does not waste quota.
Why can a DFS request return 403?DFS is an authenticated beta on the canonical host. Outside it, or when permission is withheld, the route returns 403. Do not bypass it.
How do I get an API key?Create an account, open the dashboard and create a named key. The secret appears once, and every /api/v1 data request needs it as a Bearer token.
Independent service operated by DD Inc., not affiliated with or endorsed by DraftKings. Technical access is not a redistribution license. No wagering: this service does not place, recommend or settle entries or bets. Check sources and status for actual capture context.