# Changelog

Newest first. Rules for version numbers: [Versioning](https://docs.creator-guard.com/versioning/). A version marked **unreleased** is merged but not live yet; it ships with the next production release, and its heading then gets the release date. The platform API continues the version numbers of the previous partner endpoint, which ended at 1.3.0; its history is at the end of this page.

**Announced 11 November 2026:** Account e-mails (confirmation codes, password resets, invitations, security notices) will be sent through ALL-INKL.COM (Neue Medien Münnich, Germany), which already hosts our mailbox and domain name service, instead of Resend (Plus Five Five, Inc., USA). Resend then stops being a sub-processor ([Sub-processors](https://docs.creator-guard.com/legal/sub-processors/)). Sender: `noreply@creator-guard.com`. No change to the API, keys or webhooks.

**5 November 2026:** Our database, logins and file storage moved from Supabase (USA) to our own server at OVHcloud in France. Supabase is no longer a sub-processor ([Sub-processors](https://docs.creator-guard.com/legal/sub-processors/)); the stopped copy it kept was deleted the same day. Everyone signs in once more; two-factor sign-in stays set up. No change to the API, keys or webhooks.

## 1.23.0 — unreleased (ships with the next production release) — Webhook scope on every send

### Tightened

- **An endpoint's scope holds on every send, not only when an event is queued.** A delivery of an event the endpoint may no longer carry (its object type left the endpoint's scope, see [Webhooks](https://docs.creator-guard.com/webhooks/)) ends `failed` with `last_error: scope_removed` when it is next due, also when it was being sent at the moment the endpoint was narrowed. `POST /v1/webhook-endpoints/{id}/deliveries/{d}/retry` refuses such a delivery with [`409 invalid_state`](https://docs.creator-guard.com/errors/#invalid_state) (`current_state: scope_removed`). Effective with the production release of this version.

### Changed

- **Our own failures end.** A delivery we cannot prepare (an internal error on our side, not your receiver's) is tried again with a growing pause, at most hourly; once it is past the 72-hour retry window it ends `failed` with `last_error: internal_error`. It does not count toward disabling your endpoint. A delivery whose 16 attempts are used up ends `failed` (`last_error: lease_expired`) instead of being sent a 17th time when our sender stopped during its last attempt.
- **`deletion_request.completed` also when we delete her data outside the request.** If our team deletes or anonymises a creator's data for another reason while your app's deletion request for her is open, the request is completed and your account receives the event, as it would have for the request itself.

## 1.22.0 — unreleased (ships with the next production release) — No "lost" after payment

### Tightened

- **A paid deal can no longer be marked lost.** `POST /v1/offers/{id}/mark-lost` works only from `accepted` before the placement fee was received; after that it answers [`409 deal_paid`](https://docs.creator-guard.com/errors/#deal_paid), from `accepted`, `contacted` and `in_talks` alike. A paid deal ends only through a warranty claim (`POST /v1/reservations/{id}/warranty-claim`) or Creator Guard. The agency portal follows the same rule. Effective with the production release of this version.

### Added

- Error code `deal_paid` (409).

## 1.21.0 — unreleased (ships with the next production release) — Earnings of closed leads

### Changed

- **Only a completed placement earns a commission.** `GET /v1/leads/{id}/earnings` answers `status: "void"` (amounts as before) for a lead that is lost, rejected or withdrawn and has no booked commission, instead of `expected`. A deal that completes after the agency reported it lost, or after the lead was closed, books no commission. Details: [Listing](https://docs.creator-guard.com/listing/).
- Accepting an offer in the agency portal now follows the same rules as `POST /v1/offers/{id}/accept` (the current placement warranty terms, a vetted agency), and an accept can no longer be undone once the fee was received. No change to the API itself.

## 1.20.0 — 2026-10-17 — Agency vetting state

### Added

- `vetting` on the agency profile (`GET /v1/agency-profile` and the answer of `PATCH /v1/agency-profile`), read-only: `status` (`registered`, `in_review` or `vetted`) and `waiting_matches`, the number of creators matched to your agency who wait for your vetting (a count only, nothing about them). Sending `vetting` in a `PATCH` is [`400 unknown_field`](https://docs.creator-guard.com/errors/#unknown_field). The sandbox (test keys) always reports `vetted` with `waiting_matches: 0`.

### Changed

- **Offers reach an agency only after its vetting.** An agency account is ready at once, but offers with a creator's profile (and her listing, photos and offer events) reach it only once our 5-point vetting is done (`vetting.status: "vetted"`). A creator matched to an agency before that waits and is offered when the vetting is done. Details: [Agencies](https://docs.creator-guard.com/agencies/#offers).

## 1.19.0 — 2026-10-12 — Leads with just a name

### Changed

- **`POST /v1/leads` needs only `creator_name` and `consent_confirmed: true`**, the same as a new creator in the partner portal. `platforms` and a contact (`instagram_handle` or `other_contact`) are optional now: a body without them no longer answers `400 missing_field` / `400 missing_contact`. Every field is still accepted and checked exactly as before when you send it (`platforms` at least one entry, an `instagram_handle` must be an Instagram profile, …), so keep sending everything you know. Without an `instagram_handle` there is no duplicate check by handle; send an `external_id` so a retry finds her again.
- **`PATCH /v1/leads/{id}` may clear both contacts** (`instagram_handle` and `other_contact` set to `null`), as in the portal: it no longer answers `400 missing_contact`, a lead may end up without any contact. Every field you send is still checked as before (`creator_name` and `platforms` cannot be cleared).
- `missing_contact` is now answered only by `PATCH /v1/creator/profile` (her own profile must keep a contact; unchanged).

## 1.18.0 — 2026-10-09 — The fee before review

### Tightened

- **Submit for review needs the fee.** `POST /v1/leads/{id}/submit-for-review` and `POST /v1/creator/submit-for-review` answer [`422 not_ready_for_review`](https://docs.creator-guard.com/errors/#not_ready_for_review) with `fee_missing` in `error.blockers` while the lead has no `placement_fee` (or `0`); `next_actions.can_submit_for_review` is `false` until it is set. The portal and the Telegram bot follow the same rule. Leads our team added for your account are not affected and never show `fee_missing`. Creator tokens now see `fee_missing` in `next_actions.blockers` too: her referral partner still has to set the fee.

## 1.17.0 — 2026-10-08 — Leaked OAuth secrets and tokens

### Added

- Leaked OAuth client secrets (`cgcs_`) and creator access and refresh tokens (`cgo_`, `cgr_`) are now revoked automatically when they turn up in public (GitHub secret scanning), like API keys: a leaked client secret is replaced by one nobody knows (roll a new one with `POST /v1/oauth-apps/{id}/roll`; a leaked previous secret stops working), a leaked token ends that creator's authorization. Details: [OAuth](https://docs.creator-guard.com/oauth/).
- Audit actions `oauth_app.secret_leaked` and `oauth_app.token_leaked` in `GET /v1/audit-events` (actor `system`).

## 1.16.0 — 2026-10-08 — Data protection addendum

### Added

- Agreement type `api_dpa`: the [data protection addendum](https://docs.creator-guard.com/legal/dpa/) for API partners (v1), for every account, with the EU Standard Contractual Clauses (Module One) for transfers to the USA. `GET /v1/me` (`terms`) and `GET /v1/agreements` list it after `api_terms`; `GET /v1/agreements/api_dpa/{version}` returns the text. Accept it once per account, by an owner or admin, in the portal (Settings → API) or with `POST /v1/agreements/api_dpa/accept`; the acceptance counts for live and test keys. Rules: [Authentication → Data protection addendum](https://docs.creator-guard.com/authentication/#data-protection-addendum).
- Event `agreement.published` for `api_dpa` goes to every approved account, referral partners and agencies.
- `terms_not_accepted` can name `agreement_type: "api_dpa"`.
- The [sub-processors](https://docs.creator-guard.com/legal/sub-processors/) list is published.

### Tightened

- With a **live key**, the actions that need the API Terms (creating or rolling a live key, registering a live OAuth app, every other write) also need the accepted data protection addendum: otherwise `403 terms_not_accepted` with `agreement_type: "api_dpa"` (`api_terms` is named first when both are missing). The same actions stay open as for the API Terms; test keys and creator access tokens are never checked. An account that held a live key when the addendum was published has **30 days** from the release to accept it (the date is shown in the portal); an account without a live key accepts it before its first one.

## 1.15.0 — 2026-10-08 — Search-profile match on offers

### Added

- `match` on every offer (`GET /v1/offers`, `GET /v1/offers/{id}`, the offer actions, `POST /v1/test-helpers/offers` and the `offer.*` event payloads): how well she fits your search profile, checked with the same rules as our own matching. `score` counts the criteria met (a close match counts ½), `total` the criteria checked, `knocked_out` says a must-match criterion was missed (sort by `score` / `total`, knocked-out offers last), and `criteria` lists each one as `key` + `result` (`hit`, `near` or `miss`) + `must`. Only names and results, never her values: `niche` and `platforms` are only ever `hit` or `miss` (a close match within your tolerance shows as `hit` and counts as a full point in `score`). `null` without a search profile (or with nothing filled in) and while her listing is hidden.

### Changed

- The offer `ETag` now also changes when your search profile changes, so a `PATCH` with an older `If-Match` answers `412` after you edit your search profile.
- Every offer's `ETag` changes once when this version is deployed (it now includes the match). Read the offer again before a `PATCH` with `If-Match`.

## 1.14.0 — 2026-10-06 — Consent links shown once

### Changed

- Consent links are stored only as hashes (like claim links), so a link is shown once, when it is made. `POST /v1/leads/{id}/consent-link` makes a **new** link on every call (valid at least 30 days). **Behaviour change (beta):** the lead's previous link can no longer be used to give consent — only to withdraw one, like an expired link (her confirmation page promises she can withdraw by opening her link again). Before, the call returned the same link and extended it, so call it only when you are about to send her the link. Two calls at the same moment each return a link; only the later one can give consent.
- `consent.url` of a lead is set only in the `201` of `POST /v1/leads` that created it. A `200` (an existing lead returned), `GET /v1/leads/{id}` and an `Idempotency-Key` replay of the `201` answer `consent.url: null`; `consent.expires_at` keeps showing when her current link stops working. A `200` no longer extends that link. Links sent before this version keep working until they expire or a new one is made.

## 1.13.0 — 2026-10-06 — Offboarding OAuth apps

### Added

- `enabled` and `disabled_reason` on every OAuth app (`GET`, `POST`, `PATCH /v1/oauth-apps…`). An app is disabled only by offboarding (`disabled_reason: member_offboarded`, `redirect_uris: []`): `/oauth/authorize` does not know it and `/oauth/token` answers `unauthorized_client` for codes and refresh tokens, without revoking anything. `PATCH /v1/oauth-apps/{id}` with `redirect_uris` enables it again.

### Changed

- Removing a member (or lowering her role below admin) also removes every redirect URI of a live OAuth app that one of her keys added (`oauth_app.updated` by `system` in `GET /v1/audit-events`): open authorization codes issued to those URIs stop working, and a creator authorization whose current refresh token was issued through one of them is revoked (the creator connects the app again). An app left without redirect URIs is disabled. When you replace the list, only the URIs you add are recorded as yours; URIs registered before this version are not linked to any key and are not removed by offboarding.
- Removing a redirect URI (yourself or through offboarding) also ends what was issued through it: an open authorization code for it fails at `POST /oauth/token` (`invalid_grant`), and a refresh token whose authorization went through it answers `invalid_grant` until the URI is registered again (nothing is revoked by this). Refresh tokens issued before this version are not affected.
- The scopes a creator approves on the consent screen apply to her authorization when the app exchanges the code at `POST /oauth/token`, not already when she approves: until then her existing tokens keep the scopes they had. A code asking for a scope the app no longer has answers `invalid_scope`.
- `Idempotency-Key` is now kept per API key (before: per account). A request repeated with another key of the same account runs anew instead of replaying the first key's answer. A retry sent with a key rolled in between is a new request as well.

## 1.12.0 — 2026-10-06 — API Terms of Use

### Added

- Agreement type `api_terms`: the [API Terms of Use](https://docs.creator-guard.com/legal/api-terms/) (v1), for every account. `GET /v1/me` (`terms`) and `GET /v1/agreements` list it after your account's terms; `GET /v1/agreements/api_terms/{version}` returns the text. Accept it once per account, by an owner or admin, in the portal (Settings → API) or with `POST /v1/agreements/api_terms/accept`; the acceptance counts for live and test keys. Rules: [Authentication → API Terms](https://docs.creator-guard.com/authentication/#api-terms).
- Event `agreement.published` for `api_terms` goes to every approved account, referral partners and agencies.
- `terms_not_accepted` can name `agreement_type: "api_terms"`.

### Tightened

- With a **live key**, creating or rolling a live key (`POST /v1/api-keys`, `POST /v1/api-keys/{id}/roll`, and in the portal), registering a live OAuth app (`POST /v1/oauth-apps`) and every other write need accepted API Terms: otherwise `403 terms_not_accepted` with `agreement_type: "api_terms"`. Reads, `DELETE /v1/api-keys/{id}`, `DELETE /v1/oauth-apps/{id}`, `DELETE /v1/webhook-endpoints/{id}`, `DELETE /v1/members/{id}` and `POST /v1/agreements/{type}/accept` keep working; test keys and creator access tokens are never checked. An account that held a live key when the API Terms were published has **30 days** from the release to accept them (the date is shown in the portal); an account without a live key accepts them before its first one.

## 1.11.0 — 2026-10-05 — Creator privacy for agencies

### Added

- Event `offer.consent_revoked` (object `offer`, scope `offers:read`): the creator withdrew her consent to share her profile. It goes to every agency holding an offer for her, whatever the offer's status, so you can delete what you stored of her listing and photos. With it, an accepted offer whose reservation still awaits payment is retracted and that reservation cancelled (`offer.retracted`, `reservation.cancelled`); no reservation of hers can be paid while the withdrawal stands. Endpoints subscribed with `["*"]` receive it at once; an endpoint with a list of types receives it after you add it.

### Changed

- While her consent is withdrawn, an offer's `listing` and `photo_count` are `null` and `GET /v1/offers/{id}/photos` answers `409 invalid_state` — for every offer status, unless your placement of her is `completed`. Her contact after payment is not affected.
- The `creator.privacy` scope text on the consent screen now says that the app receives the copy of her data, including her support conversations.
- Invitations to join an account are deleted 30 days after they were accepted, revoked or expired ([Data retention](https://docs.creator-guard.com/data-retention/)).

### Tightened

- `creator_name` on offers (`GET /v1/offers`, `GET /v1/offers/{id}`, every offer action and the `data.object` of offer events) and on reservations (`GET /v1/reservations`, `GET /v1/reservations/{id}`, reservation events) is `null` until your agency paid for her (a reservation of yours for her that is `paid` or `completed`; `null` again after a refund). Identify her by `creator_ref` (`CR-…`) before that. The portal shows the creator number too. Sandbox offers follow the same rule (`…/mark-paid` shows the name).
- `GET /v1/creator/data-export/{id}` and `GET /v1/jobs/{id}` (creator token) answer only the app that requested the export; another of her connected apps gets `404 not_found`. `POST /v1/creator/data-export` counts its one export per 24 hours per app.

## 1.10.0 — 2026-10-05 — Security review

### Added

- Error code `referrer_app_not_allowed` (`403`).
- `GET /v1/audit-events`: `agreement.accepted` when terms are accepted over `POST /v1/agreements/{type}/accept` (key, IP, type and version; accepting the same version again writes nothing).

### Changed

- `POST /v1/members`: an address whose login cannot join any account now gets the same `201` invitation as any other address (it is listed, counts towards the 20 per 24 hours and has the same join page); it can never be accepted. Before it was `400 invalid_field` `email`.
- `POST /v1/leads/{id}/consent-link`: an `Idempotency-Key` replay answers `url: null` (the link is never stored); call again for a link.
- `DELETE` requests ignore `If-Match` (no `DELETE` operation documents it); a malformed `If-Match` on a `DELETE` is no longer a `400`.
- Requests refused before any work for a limit (`429 rate_limited`, `429 concurrency_limited`) no longer appear in `GET /v1/request-logs` and `GET /v1/usage`; they never counted towards the rate limit. `403 ip_not_allowed` still appears there (so you see a key used from outside its allow-list) and still does not count towards the rate limit.
- Removing a member (or lowering her role below admin) replaces the client secret of every OAuth app whose current or still-accepted previous secret was set by one of her keys (`oauth_app.secret_rolled` by `system`); roll it to see the new one.
- `POST /oauth/token`, `POST /oauth/revoke`, `GET /oauth/authorize` and the consent decision share the per-IP budget of requests without an account: over it, `429` with `Retry-After`. Successful token and revoke calls do not spend it.

### Tightened

- Creator API: `POST /v1/creator/consent/grant`, `POST /v1/creator/age-confirmation` and `POST /v1/creator/agreements/{type}/accept` with a token of an OAuth app owned by the account that referred her → `403 referrer_app_not_allowed`. She gives her consent, 18+ confirmation and terms only on Creator Guard (consent link or creator portal). Withdrawing consent and reading her consent state are unchanged.
- A member who joined through an invitation made by an API key cannot create or roll portal keys that are less restricted than that key: they get its IP allowlist and expire no later than it does.

## 1.9.0 — 2026-10-05 — Team members

### Added

- `GET /v1/members`, `POST /v1/members` and `DELETE /v1/members/{id}` (scope `members:manage`): the people of an account with their roles (`owner`, `admin`, `developer`, `viewer`) and `email_verified` (`false` for a login created on the join page), invitations for `developer` or `viewer` with a one-time join link (`join_url`, valid 48 hours, shown once — `join_url: null` in an `Idempotency-Key` replay; inviting an address again replaces its open invitation; an address whose login cannot join any account is `400 invalid_field` `email`; at most 20 attempts per 24 hours, `409 limit_reached`), removal and revocation; the owner answers `409 invalid_state` with `current_state: owner`. Removing a person also revokes their open invitations and every API key whose secret they had, and disables webhook endpoints whose signing secret they know (new secret, roll it to see it). Live keys only (a `cg_test_` key gets `404 not_found`). Changes appear in `GET /v1/audit-events` as `member.invited`, `member.joined`, `member.role_changed`, `member.removed` and `member.invitation_revoked`.
- Key scope `members:manage`, selectable for new keys in the portal and over `POST /v1/api-keys`.

### Tightened

- A rolled key in its grace period can no longer use `members:manage` or `oauth_apps:manage` (as before `keys:manage` and `webhooks:manage`): `403 insufficient_scope`.
- In the portal, a member with the developer role creates, rolls and revokes only keys with read scopes, `keys:manage`, `webhooks:manage`, `usage:read` and `audit:read`.

## 1.8.0 — 2026-10-05 — Creator API, OAuth and claim links

### Added

- `POST /v1/leads/{id}/claim-link` (`leads:write`): a single-use link (7 days) where she chooses her own email and password for the creator portal; a new link replaces the open one. The URL is shown once (`url: null` in an `Idempotency-Key` replay). `409 invalid_state` with `current_state` `claimed`, `withdrawn` or `rejected`.
- Key scope `oauth_apps:manage` (OAuth apps that creators sign in to with Creator Guard), selectable for new keys in the portal and over `POST /v1/api-keys`.
- OAuth apps (`oauth_apps:manage`): `GET` and `POST /v1/oauth-apps`, `GET`, `PATCH` (with `If-Match`) and `DELETE /v1/oauth-apps/{id}`, `POST /v1/oauth-apps/{id}/roll`; the `oauth_app` object. At most 10 apps per mode; the client secret of a confidential app is shown once (`client_secret: null` in an `Idempotency-Key` replay), a roll keeps the previous secret valid for 24 hours; deleting an app revokes every creator's grant to it. Changes appear in `GET /v1/audit-events` as `oauth_app.created`, `oauth_app.updated`, `oauth_app.deleted` and `oauth_app.secret_rolled`.
- OAuth 2.1 authorization server on `https://app.creator-guard.com` for the apps above: `GET /oauth/authorize` (hosted sign-in and consent screen, authorization code with PKCE `S256`, live apps only), `POST /oauth/token` (`authorization_code`, `refresh_token` with rotation; a reused code or refresh token ends the whole grant), `POST /oauth/revoke` (RFC 7009) and the metadata document `/.well-known/oauth-authorization-server` (RFC 8414). Browser apps may read token and revocation answers only from the origin of one of their registered redirect URIs.
- `POST /v1/test-helpers/oauth-codes` (`oauth_apps:manage`, test keys only): an authorization code for a test-mode app and a sandbox lead, as if the creator had clicked "Allow"; valid for 60 seconds, exchanged at `/oauth/token`. An `Idempotency-Key` is ignored (a code is single-use).
- Creator endpoints for a creator's OAuth access token (security scheme `creatorToken`, scopes `creator.profile:read`, `creator.profile:write`, `creator.photos:write`, `creator.consent:write`, `creator.support`, `creator.privacy`): `GET /v1/creator/me`; `GET` and `PATCH /v1/creator/profile` (with `If-Match`; never fees, deal terms or `of_verified`); `POST /v1/creator/submit-for-review`; `GET` and `POST /v1/creator/photos` (metadata removed on our side), `DELETE /v1/creator/photos/{photo}`; `GET /v1/creator/consent-text`, `GET /v1/creator/consent`, `POST /v1/creator/consent/grant`, `…/revoke` and `POST /v1/creator/age-confirmation` (consent ledger entries with channel `oauth_app:app_…`; a grant needs the current text version, a withdrawal never fails because of it; a grant also records her 18+ confirmation like the hosted consent page and is `409 invalid_state` with `current_state` `age_declined` / `age_pending` while her 18+ check is declined or under review); `GET /v1/creator/agreements`, `POST /v1/creator/agreements/creator_terms/accept`; `/v1/creator/support-tickets` (list, open, messages, reply, close); `POST /v1/creator/data-export` (`202` + job) and `GET /v1/creator/data-export/{id}` (a new download link of at most 1 hour on every call while the export is kept, 7 days); `POST /v1/creator/deletion-request`; `GET /v1/creator/connected-apps` and `DELETE /v1/creator/connected-apps/{app}` (the calling app's own grant only; `DELETE` needs `creator.profile:write`). An account API key on these is `403 wrong_account_type`.
- `GET /v1/jobs/{id}`: asynchronous jobs (the data export); the `job`, `data_request`, `creator`, `creator_profile`, `consent_state`, `consent_text`, `creator_agreement`, `support_ticket`, `support_message` and `connected_app` objects.
- Events `data_export.ready`, `job.completed` and `deletion_request.completed` for the account that owns the OAuth app which acted for the creator (objects `data_request` and `job`, read with `oauth_apps:manage`). `data.object` is a reference (`{"id": "dreq_…", "object": "data_request"}`, `{"id": "job_…", "object": "job"}`), never her data; the schemas `DataRequestRef`, `JobRef`, `DataRequestEvent` and `JobEvent`. A webhook endpoint set up before 1.8.0 receives them only after its event types are changed in the portal or with a key that holds `oauth_apps:manage` (OAuth apps exist only from 1.8.0 on).
- `GET /v1/events?object=` also takes `dreq_…` and `job_…` ids.
- `x-oauth` on the `creatorToken` security scheme: issuer, metadata and revocation URLs, PKCE methods, client authentication methods and the lifetimes of codes, tokens and a rolled client secret.
- Guides in the new section "Creators": [OAuth for creator dashboards](https://docs.creator-guard.com/oauth/), [Creator API endpoints](https://docs.creator-guard.com/creator-api/), [Consent ledger](https://docs.creator-guard.com/consent-ledger/) and [Hosted pages for creators](https://docs.creator-guard.com/hosted-pages/) (consent link, claim link, creator portal).

### Changed

- The error codes `invalid_token`, `expired_token` and `consent_text_outdated` are now answered (creator endpoints); `account_not_active` also answers a creator token while the account that owns the app is not approved (her grant stays). A withdrawal of consent never fails with `consent_text_outdated`.
- `DELETE /v1/leads/{id}/photos/{photo}`: the photo is removed first and its file after; if removing the file fails, the photo is put back and the answer is `502 upstream_failed` as before (no photo can lose its file when the listing goes live at the same moment).
- Hosted consent link: after its 30 days it can no longer give consent, but it still withdraws a consent given through it.

## 1.7.0 — 2026-10-05 — Agency API

### Added

- **Agency endpoints** for agency keys: `GET` and `PUT /v1/search-profile` (incl. `flex`), `GET` and `PATCH /v1/agency-profile`, `GET /v1/offers`, `GET` and `PATCH /v1/offers/{id}`, `GET /v1/offers/{id}/photos`, the actions `accept`, `decline`, `undo-accept`, `mark-contacted`, `mark-in-talks`, `mark-signed` and `mark-lost`, `GET /v1/reservations`, `GET /v1/reservations/{id}`, `POST /v1/reservations/{id}/warranty-claim` and `GET /v1/reservations/{id}/creator`. A referral partner's key gets `403 wrong_account_type` on them (checked before the scope). Guide: [Agencies](https://docs.creator-guard.com/agencies/).
- Accepting an offer needs the current `warranty_terms`; without them `403 terms_not_accepted` names `agreement_type: "warranty_terms"`.
- Events `offer.created`, `offer.accepted`, `offer.declined`, `offer.expired`, `offer.retracted`, `offer.reopened`, `offer.progressed`, `reservation.created`, `reservation.paid`, `reservation.completed`, `reservation.refunded`, `reservation.cancelled` and `warranty_claim.created` (objects `offer` and `reservation`, read with `offers:read` and `reservations:read`).
- Test helpers `POST /v1/test-helpers/offers`, `POST /v1/test-helpers/reservations/{id}/mark-paid`, `…/complete` and `…/refund`, and `POST /v1/test-helpers/clock/advance` (test keys only). `POST /v1/test-helpers/reset` leaves an agency's test offers and reservations in place (known limit).
- The scopes `offers:read`, `offers:write`, `reservations:read`, `reservations:write` and `search_profile:write` are accepted again, now that their endpoints exist. Agency keys issued by Creator Guard carry them plus `account:write`.
- Error codes `offer_taken`, `offer_expired`, `listing_unavailable`, `payment_pending`, `undo_window_passed`, `claim_exists` and `warranty_expired` are now answered by the agency endpoints.

## 1.6.0 — 2026-10-05 — Consent link in the lead

### Added

- `consent` on the lead returned by `POST /v1/leads` (`201` and `200`) and `GET /v1/leads/{id}`: `status` (`pending`, `granted`, `revoked`), `url` (her personal consent page) and `expires_at`. Creating a lead makes the link or extends it to at least 30 days, like `POST /v1/leads/{id}/consent-link`; reading a lead never extends it. `url` and `expires_at` are `null` after her data was erased at her request. Lists, `PATCH`, withdraw and event payloads do not carry it.

## 1.5.0 — 2026-10-05 — Webhooks, photos, keys and test mode

### Added

- Test mode: `cg_test_` keys work on a sandbox with the same URLs; every limit is halved. Test helpers `POST /v1/test-helpers/leads/{id}/confirm`, `…/approve-listing`, `…/reject`, `POST /v1/test-helpers/commissions/{id}/mark-paid` and `POST /v1/test-helpers/reset`; sandbox files under `GET /v1/test-files/{path}`.
- API keys: `GET` and `POST /v1/api-keys`, `POST /v1/api-keys/{id}/roll` (grace period 0–72 hours), `DELETE /v1/api-keys/{id}`; the `api_key` object; key self-service and key policies in the portal.
- Webhooks: `/v1/webhook-endpoints` (list, create, get, change with `If-Match`, delete), `…/roll` (new signing secret, 24 hours of overlap), `…/test`, `…/replay`, `…/deliveries` and `…/deliveries/{d}/retry`; signed deliveries (`CG-Signature`), retries for 72 hours, egress IP 187.127.76.75.
- Events: `GET /v1/events` and `GET /v1/events/{id}` (30 days); 17 event types, documented as OpenAPI `webhooks`.
- `version` on leads, photos and commissions; `sequence` on events.
- Photos: `GET` and `POST /v1/leads/{id}/photos` (multipart upload, metadata removed on our side), `PATCH` and `DELETE /v1/leads/{id}/photos/{photo}`; `lead`, `created_at` and `version` on the photo object.
- Earnings: `GET /v1/commissions`, `GET /v1/commissions/{id}` (`?expand=lead`), `GET /v1/payout-details` (masked).
- Account: `PATCH /v1/me`, `PUT` and `DELETE /v1/me/logo`.
- `POST /v1/extract`: lead and listing fields suggested from text; nothing stored.
- Observability: `GET /v1/request-logs`, `GET /v1/usage`, `GET /v1/audit-events` (incl. `account.mfa_enabled` / `account.mfa_removed` when an authenticator is set up or removed).
- `?fields=` on every `GET` that answers JSON.
- Error codes `limit_reached` (409, with `error.limit`) and `upstream_failed` (502; also on photo and logo delete when the file cannot be removed — nothing changes then).
- Uploads (photos, logo): one at a time per key → otherwise `429 concurrency_limited`.
- Keys made or rolled over the API inherit the calling key's IP allowlist and expiry (`400 invalid_field` on `ip_allowlist` outside it).
- Webhook replay: at most 1,000 open deliveries per endpoint (`409 limit_reached`), 10 replays per account and day; deliveries are shared fairly between endpoints (at most 5 at once per endpoint).
- Webhook endpoints carry only the events the key that set them up may read (`403 insufficient_scope` for other event types).
- `GET /v1/audit-events` answers in the mode of the key (a test key sees only test-mode events).
- A rolled key in its grace period can no longer use `keys:manage` or `webhooks:manage` (`403 insufficient_scope`).

### Tightened

- `DELETE /v1/api-keys/{id}` needs every scope of the key it revokes (`403 insufficient_scope`), like roll.
- Keys carry only the scopes of endpoints that exist: `offers:*`, `reservations:*`, `search_profile:write`, `oauth_apps:manage` and `members:manage` are no longer accepted (`400 invalid_field` on `scopes`); they come back with their endpoints.

## 1.4.0 — 2026-10-05 — Platform API (beta)

### Added

- New API at `https://api.creator-guard.com/v1/`, in beta. Its version numbers continue after the previous endpoint's 1.3.0.
- Keys with scopes, optional expiry and IP allowlist; `GET /v1/me`.
- Agreements: list, read, accept. Option lists and brokerage settings.
- Leads: create (optionally with listing), list with filters and cursors, get with `expand`, update, withdraw.
- Listing: read and update, submit for review, confirmations, consent link, timeline, earnings.
- `Idempotency-Key` on every `POST`, `ETag` / `If-Match`, `RateLimit` headers, `X-Request-Id`, one error format with `details` and `doc_url`.

### Removed

- The previous endpoint `POST https://creator-guard.com/api/partner/v1/leads` and its documentation. It had no users; its history (1.0.0 to 1.3.0) is below.

## Previous endpoint POST /api/partner/v1/leads (retired)

The single endpoint `POST https://creator-guard.com/api/partner/v1/leads` that the platform API replaced in 1.4.0. It had no users. Kept here as a record; none of it applies to `/v1/` on `api.creator-guard.com`.

### 1.3.0 — 2026-10-04 — Partner terms

#### Tightened

- **Only accounts that accepted our partner terms can submit.** A valid key of an active account that has not accepted the partner terms yet gets `403 terms_not_accepted`, and nothing is saved. Accept the terms once in the partner portal; the key works right after. The same rule now applies to the portal itself.

#### Added

- Error code `terms_not_accepted` (`403`).

### 1.2.0 — 2026-10-04 — Duplicates, handles and account status

Fixes that make the API behave as documented and as the partner portal does. Most are invisible to a correct integration; the stricter answers come first.

#### Tightened

- **A lead past the stage `submitted` is never changed.** A request with the Instagram handle of a creator you submitted earlier used to overwrite her name, contact, followers, niche and notes at any stage. Now this happens only while she is `submitted` (as in the portal); afterwards the answer is `409 duplicate_own_lead`, nothing changes, and `error.lead` names her.
- **`instagram_handle` must be an Instagram profile.** `instagram.com`, `www.`, `m.` and `instagr.am` links, `/_u/` and `/stories/<username>` links, query strings and fragments are now understood. Other sites, other Instagram pages (posts, reels, highlights, help pages) and text that cannot be an Instagram username are rejected with `400 invalid_field` instead of being misread — before, `m.instagram.com/x` or `linktr.ee/x` collapsed to the domain and different creators looked identical.
- **Only active partner accounts can submit.** A valid key of a pending or disabled account gets `403 partner_not_approved`.
- **Duplicate budget.** At most 20 `409 duplicate_other_referrer` answers per partner account in 24 hours; after that every request with an `instagram_handle` gets `429 duplicate_limit_reached`.

#### Added

- Every response of the endpoint, whatever its status code, carries the header `X-API-Version` with the contract version (`1.2.0`).

#### Fixed

- **Ranges are checked.** `age` above 99 and `follower_count` above 2,147,483,647 return `400 invalid_field` instead of `500 internal_error`.
- **Pick-list spelling.** `platforms`, `content_types` and `niche` that match a pick-list value ignoring case are stored in the pick-list spelling (`onlyfans` → `OnlyFans`), so agency searches find them. Other values are kept as sent.
- **Simultaneous requests** with the same `external_id` or Instagram handle are handled one after the other and never create two leads.

### 1.1.1 — 2026-10-04 — Documentation site

#### Added

- This site and the OpenAPI 3.1 spec of the endpoint were published. No change to the API.

### 1.1.0 — 2026-09-30 — Creator numbers

#### Added

- Responses include `creator_ref`, the creator number (`CR-1047`) used in the partner portal and by our team. A new response field, so existing integrations keep working.

### 1.0.0 — 2026-09-15 — v1 launched

#### Added

- `POST /api/partner/v1/leads`: submit one creator per request with an API key.
- `external_id` for safe retries; duplicate recognition by Instagram handle.
- Rate limits of 60 requests per minute and 2,000 per day per key.
