Platform

Support

Email [email protected]. Include the request ID and we can usually find the problem without a back-and-forth.

What to include

Your app's client_id.
The request_id from the error body, or the X-Request-ID response header. It lets us find the exact request without asking for tokens.
The endpoint, the time (with time zone) and the status code you got.
For webhooks: the subscription ID (whs_...) and, if you have one, the delivery ID (whd_...) from the CorrConnect-Delivery-Id header.

Never send an access token, a refresh token, a webhook secret or an athlete's data. We don't need them, and we'll ask you to rotate anything you send.

Common requests

You want	Do this
Higher rate limits	Email us your `client_id`, what you're building and the volume you expect. See rate limits.
More than 10 apps	Delete apps you no longer use, or email us.
A data source or data type we don't have	Tell us which and how many of your users need it. See data sources.
Early access	Request it on the CorrConnect home page.

Security reports

Put "Security" in the subject. See security and privacy.

Before you write

Errors lists every code with the fix.
Testing your integration walks through the failure cases worth rehearsing.
The OpenAPI document is the exact contract.