Affiliate infrastructure for iGaming

Every click accounted for.
Every partner measured.

BetDivision is the API that manages your affiliate programme and tracks it end to end — partners, clicks, conversions, commissions and analytics through one auditable pipeline.

Get API access Read the endpoints

<40 msmedian click write
99.9%uptime target
26 moattribution window

Platform

One API for the whole affiliate stack

Stop reconciling three dashboards and a spreadsheet. BetDivision keeps partner records, traffic, revenue and payouts in a single consistent model.

Affiliate management

Onboard partners, store agreements, set per-partner terms, sub-affiliate trees and approval workflows without touching a spreadsheet.

Click & conversion tracking

First-party click IDs, deduplication, server-to-server postbacks and deterministic attribution across devices and domains.

Real-time analytics

Cohorts, funnels, LTV by source, creative-level performance and geo breakdowns available the second the event lands.

Payout automation

Rev-share, CPA, hybrid and tiered models with holdbacks, negative carryover, multi-currency runs and exportable statements.

Fraud detection

Velocity scoring, datacentre and VPN signals, impossible-geo checks and incentivised-traffic patterns flagged before payout.

Developer first

REST + JSON, idempotent writes, cursor pagination, signed webhooks, sandbox keys and a versioned contract that will not break under you.

How it works

Three calls from zero to attribution

1
Register the partner

POST a partner to /v1/affiliates and BetDivision returns a tracking link and a signing secret. Terms, tiers and sub-affiliates are set here once.
2
Record the click

Your redirect layer calls /v1/clicks. We write a first-party click ID, fingerprint the request for fraud signals and hand back the destination URL.
3
Send the conversion

When a player registers or deposits, post the event to /v1/conversions. Commission is calculated instantly and pushed to your webhook and analytics.

The API

Predictable endpoints, signed webhooks

Everything the dashboard does, the API does. Authenticate with a bearer key, send JSON, get JSON. Writes are idempotent, so a retried postback never doubles a commission.

POST/v1/affiliatescreate or update a partner
POST/v1/clicksrecord a click, get a click_id
POST/v1/conversionsregister a conversion event
GET/v1/reports/performancemetrics by partner, source, day
GET/v1/payoutscommission runs and statements
POST/v1/webhookssubscribe to signed events

conversion.postback.sh

# Attribute a deposit to the referring affiliate
curl -X POST https://api.betdivision.co.za/v1/conversions \
  -H "Authorization: Bearer bd_live_••••" \
  -H "Idempotency-Key: dep_90a4f1" \
  -d '{
    "click_id": "bdc_8Kq2ZR",
    "event": "deposit",
    "amount": 750.00,
    "currency": "ZAR",
    "player_ref": "sha256:9f2c…"
  }'

# 201 Created
{
  "conversion_id": "bdv_2f81c0",
  "affiliate":     "alpha-partners",
  "model":         "hybrid",
  "commission":    187.50,
  "fraud_score":   0.03,
  "status":        "approved"
}

Analytics

Numbers your finance team can sign off

Every figure traces back to a raw click and a raw conversion, so a disputed commission takes minutes to resolve instead of days.

Revenue by traffic source Last 30 days

SEO86%

Streams72%

Social64%

Email52%

Comparison44%

Push31%

Direct24%

Attribution accuracy 99.4% audited against raw logs

Fraudulent clicks blocked 2.1M in the last quarter

Avg. payout run time 11 min for 4,000+ partners

FAQ

Questions we get before a build

How fast can we integrate BetDivision?

Most teams are live in a day. Drop one tracking snippet or call the click endpoint from your own redirect service, then post conversion events server-to-server. Sandbox keys are issued the same day you request access.

Does BetDivision work without third-party cookies?

Yes. Attribution runs on a first-party click identifier plus server-to-server postbacks, with an optional pseudonymous device signature as a fallback, so nothing depends on third-party cookies.

What commission models are supported?

Revenue share, CPA, hybrid, tiered and fixed-fee models, with per-partner overrides, negative-carryover rules, holdbacks and multi-currency payouts.

How do you handle traffic fraud?

Every click is scored for duplicate fingerprints, impossible geo hops, datacentre ranges, click-to-conversion velocity and incentivised patterns. Suspicious volume is flagged before it reaches a payout run.

Where is data stored and is it POPIA compliant?

Data is encrypted in transit and at rest, retained on the schedule you configure, and processed under an operator agreement aligned with POPIA and the GDPR.

Contact

Request API access

Tell us about your programme and we will send sandbox credentials plus a short integration guide.

Call us087 0571581
Emailmanager@betdivision.co.za
Company registration2026/087518/07