# Welcome to the DUPR Partner API

## Ready to jump right in?

Get started with learning how to generate your access token:

{% content-ref url="/pages/K8AyyhKoxYNABP0iLCPQ" %}
[Partner Access Token Generation](/dupr-raas/get-started/partner-access-token-generation.md)
{% endcontent-ref %}

***

## Integration Checklist

To ensure a high-quality experience for all players, DUPR requires all partners to implement the following core features at a minimum. Use this list as a pre-launch checklist — each item links to the full requirements for that area.

* **SSO Login must be implemented for all users:** [SSO Login](/dupr-raas/integration-checklist/sso-login.md)
  * This is the only way that users can connect their DUPR account. Manually adding DUPR IDs is **not** allowed for users, tournament directors, admins, etc.
* **DUPR Rating must be visible and updated:** [Ratings and Webhooks](/dupr-raas/integration-checklist/ratings-and-webhooks.md)
  * Fetching the DUPR rating on user profiles must be visible and updated regularly through the use of webhooks.
* **User Gating:** [User Gating](/dupr-raas/integration-checklist/user-gating.md)
  * All users must have the correct entitlement(s) to use the platform and must have certain extra entitlements based on the type of tournament, league, etc. they are registering for.
* **Ability to create, update, and delete matches:** [Match Upload & Management](/dupr-raas/integration-checklist/match-upload-and-management.md)
  * The owner of the match must be able to do all of these actions.
  * Normal users are not allowed to submit matches. Only tournament directors, admins, etc.
  * Users must have the correct entitlements to be added in the match.
* **Club integration (if applicable):** [Club Integration](/dupr-raas/integration-checklist/club-integration.md)
  * If sending matches via a club, ensure that the owner of the matches have the correct permissions to submit matches for that club

***

## Integration Guides

Beyond the baseline checklist above, the following guides cover specific integration patterns that some partners need.

* **AI-Powered Ratings & Match Annotations:** [AI-Powered Ratings & Match Annotations](/dupr-raas/integration-guides/ai-powered-ratings-and-match-annotations.md)
  * For AI / computer-vision partners that produce rating estimates from video and want to attach them to DUPR match records. Requires whitelisting — contact **<tech@mydupr.com>** before integrating.

***

## Steps for Integration Review

Before moving to production, DUPR performs a thorough review of your application. Once you are ready, email **<tech@mydupr.com>** with the following details:

* **Platform Link:** A URL to your integration.
* **Test Credentials:** Any test accounts our team should use.
* **Compliance Summary:** A brief explanation of how each requirement above is met, including step-by-step testing directions.

{% hint style="info" %}
Reviews typically take up to **10 business days**. Upon approval, you will receive your production keys; otherwise, we will provide feedback on required adjustments.
{% endhint %}

***

## Support & Resources

We’re here to help. Check out our frequently asked questions linked below for quick answers.

{% content-ref url="/pages/DLWUxyrd2nrEcCdXjcCT" %}
[Developer FAQ](/dupr-raas/reference/developer-faq.md)
{% endcontent-ref %}

Still have questions? Reach out directly to our engineering team at **<tech@mydupr.com>**.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dupr.gitbook.io/dupr-raas/get-started/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.