remy
remy

Resolve Creator Invite Endpoint

Changed on

Exchange the token in /creator-partnership/{token} for the form prefill behind it.

The token is an opaque id, so the landing page cannot read it — it has to ask. Same shared static x-api-key gate as the intake routes, since the page calling this has no session. The answer is built fresh on every call, not served from a snapshot taken when the link was minted — current_plan moves the moment the creator joins or upgrades, so a creator who opened the link, joined at Registered and came back would otherwise still be told they held nothing.

404s once the Redis TTL has passed; there is nothing else to expire.

Rate limited because the x-api-key it is gated on ships in the landing page's own source and cannot be a secret. Guessing a token is hopeless either way — 32 random bytes — but the cap costs nothing. Generous enough that a creator reloading the page never trips it.

get/api/v1/remy/creator-invite/{token}

Request

  • Base URL
    https://api.brandbooster.ai (the document declares no server; this is the origin it was published from)
  • URL
    https://api.brandbooster.ai/api/v1/remy/creator-invite/{token}
  • Auth
    API key in header X-Internal-Api-Key

Path parameters

tokenstring required

Response

Successful Response

creator_idstring required
planstring required
current_planstring nullable
namestring nullable
emailstring nullable
profile_linkstring nullable
nichestring[]
countrystring nullable
languagestring[]
brands_worked_withstring[]
published_ratenumber nullable
campaignsobject[]
recent_postsobject[]
connected_accountobject nullable
connected_platformsstring[]
has_brand_kit_proofboolean
citystring nullable
metricsobject

Changes

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status