# Developer FAQ

## How to Get Test Users

You should have received 4 test users in your onboarding email. If you did not receive them, please email us at <tech@mydupr.com> and we will create test users for you.

## How to Get a Test Club

You should have received a test club in your onboarding email. If you did not receive one, please email us at <tech@mydupr.com> and we will set up a test club for you.

## Match Submission Errors

If you're encountering errors during match submission, please check the following in your request payload:

* **No duplicate players:** Ensure that no single player appears two or more times in the submission.
* **No tied games:** All games within the match must have a clear winner; tied games are not permitted.
* **Unique identifier:** The `"identifier"` field must be unique for each *new* match submission. If you are updating an existing match, please use the designated update endpoint instead.

## Valid Match Sources

Valid `matchSource` values are `CLUB` and `PARTNER` .

* For `CLUB` submissions, you must include the correct `"clubId"` in the payload.
* For `PARTNER` submissions, the `"clubId"` field should be omitted from the payload.

## 403 Forbidden Error

A 403 Forbidden error indicates that you do not have the necessary permissions to access the requested endpoint. Several endpoints on our API reference are intentionally restricted and not available for public consumption.

If you believe you are incorrectly receiving this response for an endpoint you should have access to, please reach out to us for assistance.

**Common Endpoints Unavailable for Public Use:**

The following endpoints commonly return a 403 Forbidden error as they are restricted:

* All Provisional Rating Endpoints
* All Event Endpoints
* `/user/{version}/{id}/details`
* `/user/{version}/invite`

## 403 on `/match/{version}/annotate`

The annotation endpoint requires two things:

1. The `MATCH::ANNOTATE` authority on your API token. Standard match-create tokens do not include it by default — request it from <tech@mydupr.com>.
2. The target match must already exist (created via the match-create endpoint) and you must be the client that created it.

If you are also seeing `INFORMATIONAL is not permitted; contact DUPR to enable informational matches` on match-create, your client key has not been whitelisted for the AI-generated rating flow. Email <tech@mydupr.com> with your client ID to request access. See [AI-Powered Ratings & Match Annotations](/dupr-raas/integration-guides/ai-powered-ratings-and-match-annotations.md) for the full integration steps.


---

# 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/reference/developer-faq.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.
