INDEPENDENT DEVELOPER REFERENCE
Why can a DFS request return 403?
DFS is available for authenticated beta evaluation on the canonical production host. Outside that condition the route returns 403 because source redistribution permission is pending. Rows cover selected slates, not complete sport boards. An API key grants technical access and does not establish source redistribution rights.
Editorial review: · Not a live coverage report
What the 403 tells you
The message reads that DFS public redistribution is pending source permission. Check that you called draftkingsapi.com directly rather than a preview host or a proxy that changes the host header. If the response persists, treat it as a real boundary and do not try to bypass it.
Check the recorded data
Related resources
For developers building DFS tools on current DraftKings slates and roster-slot salaries. Not for contest results, ownership, salary history or republishing rows.
DraftKings DFS contests and salaries APIExplore US-DK sport, contest, slate and draftable observations with selected-slate limits and roster-slot salary semantics.
Why am I getting a 401 or 403?A 401 means the key is missing, malformed or revoked. A 403 means an origin, plan or redistribution boundary, not a problem with the key.
Can I redistribute data from this API?An API key gives technical access, not a redistribution license. Rows carry rights notes, and you must resolve rights for anything you publish.
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.