Changelog
Newest first. Rules for version numbers: 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). 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); 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) ends
failedwithlast_error: scope_removedwhen it is next due, also when it was being sent at the moment the endpoint was narrowed.POST /v1/webhook-endpoints/{id}/deliveries/{d}/retryrefuses such a delivery with409 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
failedwithlast_error: internal_error. It does not count toward disabling your endpoint. A delivery whose 16 attempts are used up endsfailed(last_error: lease_expired) instead of being sent a 17th time when our sender stopped during its last attempt. deletion_request.completedalso 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-lostworks only fromacceptedbefore the placement fee was received; after that it answers409 deal_paid, fromaccepted,contactedandin_talksalike. 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}/earningsanswersstatus: "void"(amounts as before) for a lead that is lost, rejected or withdrawn and has no booked commission, instead ofexpected. A deal that completes after the agency reported it lost, or after the lead was closed, books no commission. Details: 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
vettingon the agency profile (GET /v1/agency-profileand the answer ofPATCH /v1/agency-profile), read-only:status(registered,in_revieworvetted) andwaiting_matches, the number of creators matched to your agency who wait for your vetting (a count only, nothing about them). Sendingvettingin aPATCHis400 unknown_field. The sandbox (test keys) always reportsvettedwithwaiting_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.
1.19.0 — 2026-10-12 — Leads with just a name
Changed
POST /v1/leadsneeds onlycreator_nameandconsent_confirmed: true, the same as a new creator in the partner portal.platformsand a contact (instagram_handleorother_contact) are optional now: a body without them no longer answers400 missing_field/400 missing_contact. Every field is still accepted and checked exactly as before when you send it (platformsat least one entry, aninstagram_handlemust be an Instagram profile, …), so keep sending everything you know. Without aninstagram_handlethere is no duplicate check by handle; send anexternal_idso a retry finds her again.PATCH /v1/leads/{id}may clear both contacts (instagram_handleandother_contactset tonull), as in the portal: it no longer answers400 missing_contact, a lead may end up without any contact. Every field you send is still checked as before (creator_nameandplatformscannot be cleared).missing_contactis now answered only byPATCH /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-reviewandPOST /v1/creator/submit-for-reviewanswer422 not_ready_for_reviewwithfee_missinginerror.blockerswhile the lead has noplacement_fee(or0);next_actions.can_submit_for_reviewisfalseuntil 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 showfee_missing. Creator tokens now seefee_missinginnext_actions.blockerstoo: 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 withPOST /v1/oauth-apps/{id}/roll; a leaked previous secret stops working), a leaked token ends that creator's authorization. Details: OAuth. - Audit actions
oauth_app.secret_leakedandoauth_app.token_leakedinGET /v1/audit-events(actorsystem).
1.16.0 — 2026-10-08 — Data protection addendum
Added
- Agreement type
api_dpa: the data protection addendum for API partners (v1), for every account, with the EU Standard Contractual Clauses (Module One) for transfers to the USA.GET /v1/me(terms) andGET /v1/agreementslist it afterapi_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 withPOST /v1/agreements/api_dpa/accept; the acceptance counts for live and test keys. Rules: Authentication → Data protection addendum. - Event
agreement.publishedforapi_dpagoes to every approved account, referral partners and agencies. terms_not_acceptedcan nameagreement_type: "api_dpa".- The 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_acceptedwithagreement_type: "api_dpa"(api_termsis 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
matchon every offer (GET /v1/offers,GET /v1/offers/{id}, the offer actions,POST /v1/test-helpers/offersand theoffer.*event payloads): how well she fits your search profile, checked with the same rules as our own matching.scorecounts the criteria met (a close match counts ½),totalthe criteria checked,knocked_outsays a must-match criterion was missed (sort byscore/total, knocked-out offers last), andcriterialists each one askey+result(hit,nearormiss) +must. Only names and results, never her values:nicheandplatformsare only everhitormiss(a close match within your tolerance shows ashitand counts as a full point inscore).nullwithout a search profile (or with nothing filled in) and while her listing is hidden.
Changed
- The offer
ETagnow also changes when your search profile changes, so aPATCHwith an olderIf-Matchanswers412after you edit your search profile. - Every offer's
ETagchanges once when this version is deployed (it now includes the match). Read the offer again before aPATCHwithIf-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-linkmakes 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.urlof a lead is set only in the201ofPOST /v1/leadsthat created it. A200(an existing lead returned),GET /v1/leads/{id}and anIdempotency-Keyreplay of the201answerconsent.url: null;consent.expires_atkeeps showing when her current link stops working. A200no 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
enabledanddisabled_reasonon every OAuth app (GET,POST,PATCH /v1/oauth-apps…). An app is disabled only by offboarding (disabled_reason: member_offboarded,redirect_uris: []):/oauth/authorizedoes not know it and/oauth/tokenanswersunauthorized_clientfor codes and refresh tokens, without revoking anything.PATCH /v1/oauth-apps/{id}withredirect_urisenables 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.updatedbysysteminGET /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 answersinvalid_grantuntil 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 answersinvalid_scope. Idempotency-Keyis 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 (v1), for every account.GET /v1/me(terms) andGET /v1/agreementslist 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 withPOST /v1/agreements/api_terms/accept; the acceptance counts for live and test keys. Rules: Authentication → API Terms. - Event
agreement.publishedforapi_termsgoes to every approved account, referral partners and agencies. terms_not_acceptedcan nameagreement_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: otherwise403 terms_not_acceptedwithagreement_type: "api_terms". Reads,DELETE /v1/api-keys/{id},DELETE /v1/oauth-apps/{id},DELETE /v1/webhook-endpoints/{id},DELETE /v1/members/{id}andPOST /v1/agreements/{type}/acceptkeep 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(objectoffer, scopeoffers: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
listingandphoto_countarenullandGET /v1/offers/{id}/photosanswers409 invalid_state— for every offer status, unless your placement of her iscompleted. Her contact after payment is not affected. - The
creator.privacyscope 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).
Tightened
creator_nameon offers (GET /v1/offers,GET /v1/offers/{id}, every offer action and thedata.objectof offer events) and on reservations (GET /v1/reservations,GET /v1/reservations/{id}, reservation events) isnulluntil your agency paid for her (a reservation of yours for her that ispaidorcompleted;nullagain after a refund). Identify her bycreator_ref(CR-…) before that. The portal shows the creator number too. Sandbox offers follow the same rule (…/mark-paidshows the name).GET /v1/creator/data-export/{id}andGET /v1/jobs/{id}(creator token) answer only the app that requested the export; another of her connected apps gets404 not_found.POST /v1/creator/data-exportcounts 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.acceptedwhen terms are accepted overPOST /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 same201invitation 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 was400 invalid_fieldemail.POST /v1/leads/{id}/consent-link: anIdempotency-Keyreplay answersurl: null(the link is never stored); call again for a link.DELETErequests ignoreIf-Match(noDELETEoperation documents it); a malformedIf-Matchon aDELETEis no longer a400.- Requests refused before any work for a limit (
429 rate_limited,429 concurrency_limited) no longer appear inGET /v1/request-logsandGET /v1/usage; they never counted towards the rate limit.403 ip_not_allowedstill 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_rolledbysystem); roll it to see the new one. POST /oauth/token,POST /oauth/revoke,GET /oauth/authorizeand the consent decision share the per-IP budget of requests without an account: over it,429withRetry-After. Successful token and revoke calls do not spend it.
Tightened
- Creator API:
POST /v1/creator/consent/grant,POST /v1/creator/age-confirmationandPOST /v1/creator/agreements/{type}/acceptwith 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/membersandDELETE /v1/members/{id}(scopemembers:manage): the people of an account with their roles (owner,admin,developer,viewer) andemail_verified(falsefor a login created on the join page), invitations fordeveloperorviewerwith a one-time join link (join_url, valid 48 hours, shown once —join_url: nullin anIdempotency-Keyreplay; inviting an address again replaces its open invitation; an address whose login cannot join any account is400 invalid_fieldemail; at most 20 attempts per 24 hours,409 limit_reached), removal and revocation; the owner answers409 invalid_statewithcurrent_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 (acg_test_key gets404 not_found). Changes appear inGET /v1/audit-eventsasmember.invited,member.joined,member.role_changed,member.removedandmember.invitation_revoked.- Key scope
members:manage, selectable for new keys in the portal and overPOST /v1/api-keys.
Tightened
- A rolled key in its grace period can no longer use
members:manageoroauth_apps:manage(as beforekeys:manageandwebhooks: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:readandaudit: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: nullin anIdempotency-Keyreplay).409 invalid_statewithcurrent_stateclaimed,withdrawnorrejected.- Key scope
oauth_apps:manage(OAuth apps that creators sign in to with Creator Guard), selectable for new keys in the portal and overPOST /v1/api-keys. - OAuth apps (
oauth_apps:manage):GETandPOST /v1/oauth-apps,GET,PATCH(withIf-Match) andDELETE /v1/oauth-apps/{id},POST /v1/oauth-apps/{id}/roll; theoauth_appobject. At most 10 apps per mode; the client secret of a confidential app is shown once (client_secret: nullin anIdempotency-Keyreplay), a roll keeps the previous secret valid for 24 hours; deleting an app revokes every creator's grant to it. Changes appear inGET /v1/audit-eventsasoauth_app.created,oauth_app.updated,oauth_app.deletedandoauth_app.secret_rolled. - OAuth 2.1 authorization server on
https://app.creator-guard.comfor the apps above:GET /oauth/authorize(hosted sign-in and consent screen, authorization code with PKCES256, live apps only),POST /oauth/token(authorization_code,refresh_tokenwith 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. AnIdempotency-Keyis ignored (a code is single-use).- Creator endpoints for a creator's OAuth access token (security scheme
creatorToken, scopescreator.profile:read,creator.profile:write,creator.photos:write,creator.consent:write,creator.support,creator.privacy):GET /v1/creator/me;GETandPATCH /v1/creator/profile(withIf-Match; never fees, deal terms orof_verified);POST /v1/creator/submit-for-review;GETandPOST /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,…/revokeandPOST /v1/creator/age-confirmation(consent ledger entries with channeloauth_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 is409 invalid_statewithcurrent_stateage_declined/age_pendingwhile 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) andGET /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-appsandDELETE /v1/creator/connected-apps/{app}(the calling app's own grant only;DELETEneedscreator.profile:write). An account API key on these is403 wrong_account_type. GET /v1/jobs/{id}: asynchronous jobs (the data export); thejob,data_request,creator,creator_profile,consent_state,consent_text,creator_agreement,support_ticket,support_messageandconnected_appobjects.- Events
data_export.ready,job.completedanddeletion_request.completedfor the account that owns the OAuth app which acted for the creator (objectsdata_requestandjob, read withoauth_apps:manage).data.objectis a reference ({"id": "dreq_…", "object": "data_request"},{"id": "job_…", "object": "job"}), never her data; the schemasDataRequestRef,JobRef,DataRequestEventandJobEvent. 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 holdsoauth_apps:manage(OAuth apps exist only from 1.8.0 on). GET /v1/events?object=also takesdreq_…andjob_…ids.x-oauthon thecreatorTokensecurity 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, Creator API endpoints, Consent ledger and Hosted pages for creators (consent link, claim link, creator portal).
Changed
- The error codes
invalid_token,expired_tokenandconsent_text_outdatedare now answered (creator endpoints);account_not_activealso answers a creator token while the account that owns the app is not approved (her grant stays). A withdrawal of consent never fails withconsent_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 is502 upstream_failedas 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:
GETandPUT /v1/search-profile(incl.flex),GETandPATCH /v1/agency-profile,GET /v1/offers,GETandPATCH /v1/offers/{id},GET /v1/offers/{id}/photos, the actionsaccept,decline,undo-accept,mark-contacted,mark-in-talks,mark-signedandmark-lost,GET /v1/reservations,GET /v1/reservations/{id},POST /v1/reservations/{id}/warranty-claimandGET /v1/reservations/{id}/creator. A referral partner's key gets403 wrong_account_typeon them (checked before the scope). Guide: Agencies. - Accepting an offer needs the current
warranty_terms; without them403 terms_not_acceptednamesagreement_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.cancelledandwarranty_claim.created(objectsofferandreservation, read withoffers:readandreservations:read). - Test helpers
POST /v1/test-helpers/offers,POST /v1/test-helpers/reservations/{id}/mark-paid,…/completeand…/refund, andPOST /v1/test-helpers/clock/advance(test keys only).POST /v1/test-helpers/resetleaves an agency's test offers and reservations in place (known limit). - The scopes
offers:read,offers:write,reservations:read,reservations:writeandsearch_profile:writeare accepted again, now that their endpoints exist. Agency keys issued by Creator Guard carry them plusaccount:write. - Error codes
offer_taken,offer_expired,listing_unavailable,payment_pending,undo_window_passed,claim_existsandwarranty_expiredare now answered by the agency endpoints.
1.6.0 — 2026-10-05 — Consent link in the lead
Added
consenton the lead returned byPOST /v1/leads(201and200) andGET /v1/leads/{id}:status(pending,granted,revoked),url(her personal consent page) andexpires_at. Creating a lead makes the link or extends it to at least 30 days, likePOST /v1/leads/{id}/consent-link; reading a lead never extends it.urlandexpires_atarenullafter 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 helpersPOST /v1/test-helpers/leads/{id}/confirm,…/approve-listing,…/reject,POST /v1/test-helpers/commissions/{id}/mark-paidandPOST /v1/test-helpers/reset; sandbox files underGET /v1/test-files/{path}. - API keys:
GETandPOST /v1/api-keys,POST /v1/api-keys/{id}/roll(grace period 0–72 hours),DELETE /v1/api-keys/{id}; theapi_keyobject; key self-service and key policies in the portal. - Webhooks:
/v1/webhook-endpoints(list, create, get, change withIf-Match, delete),…/roll(new signing secret, 24 hours of overlap),…/test,…/replay,…/deliveriesand…/deliveries/{d}/retry; signed deliveries (CG-Signature), retries for 72 hours, egress IP 187.127.76.75. - Events:
GET /v1/eventsandGET /v1/events/{id}(30 days); 17 event types, documented as OpenAPIwebhooks. versionon leads, photos and commissions;sequenceon events.- Photos:
GETandPOST /v1/leads/{id}/photos(multipart upload, metadata removed on our side),PATCHandDELETE /v1/leads/{id}/photos/{photo};lead,created_atandversionon the photo object. - Earnings:
GET /v1/commissions,GET /v1/commissions/{id}(?expand=lead),GET /v1/payout-details(masked). - Account:
PATCH /v1/me,PUTandDELETE /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_removedwhen an authenticator is set up or removed). ?fields=on everyGETthat answers JSON.- Error codes
limit_reached(409, witherror.limit) andupstream_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_fieldonip_allowlistoutside 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_scopefor other event types). GET /v1/audit-eventsanswers 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:manageorwebhooks: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:manageandmembers:manageare no longer accepted (400 invalid_fieldonscopes); 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-Keyon everyPOST,ETag/If-Match,RateLimitheaders,X-Request-Id, one error format withdetailsanddoc_url.
Removed
- The previous endpoint
POST https://creator-guard.com/api/partner/v1/leadsand 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
submittedis 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 issubmitted(as in the portal); afterwards the answer is409 duplicate_own_lead, nothing changes, anderror.leadnames her. instagram_handlemust be an Instagram profile.instagram.com,www.,m.andinstagr.amlinks,/_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 with400 invalid_fieldinstead of being misread — before,m.instagram.com/xorlinktr.ee/xcollapsed 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_referreranswers per partner account in 24 hours; after that every request with aninstagram_handlegets429 duplicate_limit_reached.
Added
- Every response of the endpoint, whatever its status code, carries the header
X-API-Versionwith the contract version (1.2.0).
Fixed
- Ranges are checked.
ageabove 99 andfollower_countabove 2,147,483,647 return400 invalid_fieldinstead of500 internal_error. - Pick-list spelling.
platforms,content_typesandnichethat 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_idor 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_idfor safe retries; duplicate recognition by Instagram handle.- Rate limits of 60 requests per minute and 2,000 per day per key.