Build a partner integration

Connect a new partner yourself — paste their example reply and the CRM fills in the rest. No code, no support ticket.

Connecting a new partner is the one thing every other platform makes you open a support ticket for. Here you do it yourself, in a form, in a few minutes — this page walks through it as if you've never done one before.

The three objects, and why they're separate

Delivery is a short chain. An Integration template is the recipe for talking to one partner's API — their URL, how you log in, which lead field goes where. A Partner holds the secrets (your API key or login) and points at a template. A Campaign sits under a partner and is the thing a Flow actually routes leads to.

They're separate so one recipe serves many: build the template once, and every partner on that same CRM reuses it with their own key. If you're connecting a single partner, tick “Auto-create Partner + Campaign” when you save and the CRM builds the whole chain for you — you only add the credentials afterward.

The six steps of a template

• Name — anything you'll recognise later.
• Transport — the partner's endpoint URL, the HTTP method (GET/POST) and body format (JSON/query). Straight from their docs.
• Auth — how you authenticate: an API key in a header, a bearer token, or login+password. You pick the method here; the actual secret is entered per-partner, so the same template stays shareable.
• Request mapping — which of your lead fields fills which of the partner's request fields. Click a field, click a macro like {phone} or {email} to drop it in.
• Response parsing — where in the partner's reply to read the four things that matter (below). This is the step people stall on, and the one the CRM now does for you.
• Status pull (optional) — how to fetch call-statuses and deposits back on a schedule. It has a page of its own, and so does mapping the partner's status names onto yours.

You don't have to read JSON — paste a sample

In Response parsing, click “Paste a sample reply” to open the helper, drop in an example response from the partner's docs and press Detect. The CRM shows you exactly where each value lives and fills it in when you click Use. If it can't find one, it tells you the names that field usually goes by so you can point it yourself. This is the whole point: you never have to know what a dot-path is. (Got the partner's full docs instead? The AI draft button at the top drafts the entire template at once.)

The four things it reads from the reply

• Accept path + values — the field that says the lead was taken, and the values that count as success (e.g. status = ok or accepted). Anything else is treated as a rejection.
• Lead ID path — the partner's own id for the lead. You need it so status sync can find this lead again later.
• Autologin URL path — a link that logs the player straight into the partner's page. Your Mask prelander forwards the player on to it once it's available.
• Error path — where the partner writes the reason for a rejection. That text becomes the lead's fail_reason and is passed back to your traffic source, so they see why.

Prove it before real traffic

Press “Send a test”. It fires one probe lead through the real config and shows the whole round-trip: the exact request that went out, the partner's raw reply, and what the CRM parsed out of it — accepted or not, the lead id, the autologin. If a path is wrong you see it here, on one test lead, instead of discovering it after a day of live traffic.

When something's off

• Every lead rejected — the accept values don't match. Check what the partner's reply actually says in the test round-trip and set the accept values to that.
• Accepted but no autologin forwarded — the autologin path is wrong or the partner didn't return one on a test lead.
• Statuses never update — the lead id path is wrong, so status sync can't match leads back; or the status pull isn't configured. See Postbacks & status sync.
• 401 / 403 from the partner — auth. The credentials on the Partner page are missing or wrong, or the auth method doesn't match their docs.

Odd or undocumented payload? Paste the partner's raw API docs into the AI assistant for a full draft you then review — see “AI draft” for what to paste and what to check. And the same in-app help lives beside the form as the Smart Guide — the docs explain the model, the Smart Guide answers “what do I press right now”.

Still stuck?

You shouldn't need us for this — doing it yourself is the whole point. But if a partner's API does something genuinely unusual, send us their docs and we'll help you map it.

• Telegram @d0petech
• https://t.me/d0petech
• Fastest reply
• [email protected]
• mailto:[email protected]
• Email support