Developers

Build on Trendly.

Tell Trendly about the sales your creators bring in, from your own systems, a Cloudflare Worker or Impact.com. Or connect your Trendly account to an AI assistant and run campaigns from a chat. Pick the guide that fits your setup.

Start here

How affiliate sales reach Trendly

Every affiliate sale follows the same four steps, whichever way you connect. You only ever handle the third one, and on Impact.com not even that.

  1. Creator

    Shares a code or a link

    Their personal discount code, or a link to your site with their code in it.

  2. Customer

    Buys from you

    Using the code at checkout, or after arriving through the link.

  3. You

    Your system, the Worker or Impact tells Trendly

    One HTTPS call per order and per change, or nothing at all on Impact.com.

  4. Trendly

    Credits the creator and pays out

    Matches the creator, holds the commission through your refund window, then pays it in a payout run.

Guides

Pick your path

Not sure?

Which guide do I need?

IFREAD
Your shop, app or backend can make an HTTPS call when an order changesSales API
Your site runs on Cloudflare, or creators share links to your site rather than codesCloudflare Worker
Your affiliate program already runs on Impact.comImpact.com
You want to search creators, run campaigns or handle offers from Claude, ChatGPT or your editorMCP connector

Beyond sales

Campaigns, offers and creators

The Sales API covers affiliate sales and codes. The rest of Trendly is reachable through the MCP server, which acts as a signed-in user with the same permissions as the dashboard. Connect it to an AI assistant, or to any MCP client you write yourself.

Sales API basics

True of every call

One key, in a header

Every call carries Authorization: Bearer trk_live_… (or the same value as X-API-Key) over HTTPS to https://api.trendly.com.sa. Keys are created in your developer settings, shown once and stored hashed.

Test keys store real test data

A trk_test_… key runs the same code against the same program. Its orders are stored marked as test, left out of every figure and payout, and can be cleared from the dashboard.

The version is in the path

Anything that would break a working integration ships as /v2, never as a change to /v1. Additive changes land in place and are listed in the changelog.

Every call is logged back to you

Each response carries an X-Request-Id. GET /v1/events returns your own request history with bodies, and the same log is in the dashboard. Send the request id from a failing call and Trendly can see exactly what you sent and what came back.

Get a key

If you have a Trendly login, open Developers in the dashboard and create a test key yourself. If you do not, your Trendly contact can issue one. The MCP connector and Impact.com do not need a key.

Your API keys