Superfiliate

Partners API

Getting Started

Create a key in Settings → Developers, authenticate, and make your first request.

Base URL

All requests are served over HTTPS from a single base URL:

Base URLbash
https://api.superfiliate.com

Every endpoint lives under the /api/v1 prefix, and both requests and responses speak JSON. If you can make an HTTPS call, you can integrate with Superfiliate — there are no SDKs to install or frameworks to adopt.

Make your first request

  1. 1

    Get your API credentials

    Every integration authenticates with a client_id / client_secret pair, scoped per store. Create one in the Superfiliate app under Settings → Developers. Name it for the tool that will use it and copy the pair — the secret is shown once. If you're asked to pick scopes, grant only what the integration needs. The API keys guide walks through generate and revoke.

  2. 2

    Authenticate

    Join the two values with a colon and send them as a bearer token on every request:

    Request headerhttp
    Authorization: Bearer {{client_id}}:{{client_secret}}

    What each credential can touch is governed by scopes — see Authentication for the full list.

  3. 3

    Call the API

    List the campaigns on your store:

    List campaignsbash
    curl "https://api.superfiliate.com/api/v1/campaigns" \
      -H "Authorization: Bearer $SF_CLIENT_ID:$SF_CLIENT_SECRET"

    A healthy response comes back as plain JSON:

    Response · 200 OKjson
    [
      {
        "id": 123123,
        "name": "Wide Audience - Loyalty Program",
        "status": "active",
        "audience_type": "loyalty"
      },
      {
        "id": 456456,
        "name": "Cat Owners Instagram - 2022",
        "status": "finished",
        "audience_type": "creators"
      }
    ]
  4. 4

    Build from here

    You are ready to build on top of the Partners API. Go to the API reference for endpoint details, request schemas, and examples.

Rate limits

Requests are rate limited with a leaky-bucket strategy: you get a burst of 50 requests, recovering at 2 requests per second. Go over and the API answers with 429 Too Many Requests until the bucket drains. The rate limiting guide covers how to stay comfortably under.

Next steps