Skip to content

Partner integration notes ​

For partners integrating a CRM or vault: where to start in this documentation, and what we need from you to register your servers and pages.


1. Start here ​

  • Registration from your own screens: Onboarding - e-mail confirmation click, contract signature, POST /api/register, the API key created right after with the login token, Veriff.
  • Day-to-day work with a key: Vault for integrations - uploads, products, consent, sales.
  • Identity verification for programs: Verification and the webhook events account.verified / account.verification_declined in Webhooks.
  • Sales notifications: Webhooks - one webhook per creator; tell them apart by the URL you choose.
  • Running many creators from a few servers: Rate limits and Running many accounts from your own servers.

2. What we need from you ​

ItemWhyWhere it goes
Egress IP addresses or CIDR ranges of your serversCalls with a generated key from these addresses get the higher ceiling per IP (1000 / 1000 / 500 a minute for media reads, product reads, wallet) instead of 120 / 120 / 60Rate limits
Web origins of your sign-in and registration pages (https://app.example.com)POST /api/login, POST /api/register and POST /api/agencies/register answer our own apps and registered partner pages only; any other page is refused with 403 origin_not_allowed. A listed page is also accepted as the domain of return_url on POST /api/user/email/verify. The login token issued to a partner page or server expires after 4 hours - create the API key with it right awayOnboarding
Egress IP addresses of a server that signs creators in or registers themA registered server may call the three endpoints above without a page origin (same 4-hour token)Onboarding
Your production and staging web originsDirect browser uploads to Fangate's storage (presigned URLs) need them on the storage CORS allow-listUpload Sessions
Roughly how many creators you expect and how often you sync listsTo size the ceiling; we raise it when it turns out too low-

Send all of this to info@fangate.app. Anything else a creator does in person - payout details, password, keys - is in the Fangate dashboard; opening it in a pop-up from your product needs nothing from us.

Fangate backend developer documentation