# Support

## Where to ask

- **On Telegram:** [@creatorguardsupport](https://t.me/creatorguardsupport), our support account.
- **In the partner or agency portal**, the **Support** button: it opens your own Telegram support group if one is set up for you, otherwise our Telegram support.
- **By email:** [info@creator-guard.com](mailto:info@creator-guard.com).

Our support never asks for your password, a login code or a full API key, on Telegram or anywhere else. Anyone who does is not us.

## What to include

- The **`request_id`** (`req_…`) of the request — from the error body or the `X-Request-Id` header. With it we find the request in our log.
- The **creator number** (`CR-1047`) or your `external_id` when the question is about a creator.
- The HTTP status and the error `code`.
- Your key's **prefix** (`cg_live_ab12`, as shown under **Settings → API**) when the question is about a key.

Never send the full API key, not even to us. We never need it.

## Common requests

| You want to… | Do this |
|---|---|
| Get a key, another scope or an IP allowlist | Ask us. The key is handed over once, through a secure channel. |
| Revoke a key that may have leaked | Tell us right away. It stops working on the next request. |
| Higher limits for an import | Tell us the volume and timing before you start. |
| Know why a creator returned `409` | Send us the handle. We do not reveal the other account, but we check that nothing went wrong. |
| A webhook endpoint that was disabled | Fix the receiver, then re-enable it: [Webhooks](https://docs.creator-guard.com/webhooks/#retries). |
