Skip to main content

Step 3 · Launch the system

Once you have a valid access_token from login, you open the affiliate system by loading its launch URL with the token attached. You embed it inside your platform via an iframe (or the equivalent in your stack), so the affiliate system appears directly within your product.

The launch URL​

Load the affiliate system by requesting this URL with the access token as the t query parameter:

GET https://<affiliate_system_host>/?t=<access_token>
  • <affiliate_system_host> is the host of the affiliate system. We provide the real host — for staging and for production — together with your credentials; it is not published here.
  • t is the access_token returned by the login endpoint.

Embed it in your platform with an iframe whose src is that URL:

<iframe
    src="https://<affiliate_system_host>/?t=<access_token>"
    width="100%"
    height="800"
    frameborder="0"
></iframe>

The access_token is short-lived (about 15 minutes — see Login), so generate a fresh token right before launching and build the URL with it each time, rather than reusing an old one.

A 403 when launching means QA is still pending

Before your webhooks pass our QA, loading the launch URL returns 403. This is expected and correct — it means QA is still pending, not that something is broken.

Your login keeps working throughout and returns a valid token the whole time; only the launch is gated. Once your webhooks pass QA, the launch is enabled and the system loads normally (returns 200).

See the Integration overview for the full order, and the Webhooks and Signature pages for what QA validates.

Troubleshooting​

  • You get a 403. First check whether your webhook QA has passed — this is the most common cause. Until it passes, the launch stays gated and returns 403 by design.
  • The system doesn't load and your token may be old. The access_token expires after about 15 minutes. Request a fresh token from login and rebuild the launch URL with it.