API Documentation: Complete Integration Guide for Casino Affiliates
Here's the reality: clunky integrations kill conversions. I've watched affiliates lose 12-18% of their revenue because their tracking setup couldn't handle cross-device attribution or mobile app installs.
That ends here. AffiliGaming's REST API gives you pixel-perfect tracking across every player touchpoint - desktop, mobile web, native apps, even smart TV interfaces. We're talking sub-50ms response times and 99.97% uptime, backed by the same infrastructure powering $2.3B in annual affiliate revenue.
This isn't another "developer documentation" maze. I'm walking you through real-world implementation, from authentication to advanced webhook automation. Whether you're running a casino affiliate platform with 50 sites or building custom tracking for a single high-traffic domain, you'll find exactly what you need.
Authentication & API Access
Most platforms won't tell you this, but authentication is where 60% of integration failures happen. Not here.
AffiliGaming uses OAuth 2.0 with rotating bearer tokens. You get API credentials the moment you're approved - no waiting for "technical review" or jumping through bureaucratic hoops.
Quick start authentication:
Generate API key pair from dashboard (Settings > API Access)
Request bearer token via POST to /oauth/token
Token expires after 24 hours - refresh endpoint provided
Rate limits: 10,000 requests/hour (scales with tier)
Pro tip: implement token refresh automation immediately. I've tested dozens of setups, and manual token management creates tracking gaps during off-hours. Check our getting started with platform integration guide for automated refresh scripts.
Sandbox Environment
Test everything before going live. Our sandbox mirrors production perfectly - same endpoints, same response times, just flagged test data.
Sandbox URL: https://sandbox-api.affligaming.com
Production URL: https://api.affligaming.com
No data pollution. No broken attribution from test clicks. Switch endpoints when you're ready.
Core Tracking Endpoints
These are your money-makers. Master these four endpoints and you'll handle 95% of affiliate scenarios.
/track/click - Player Click Attribution
Records initial player interaction. Captures device fingerprint, geo data, referral source.
Required parameters:
affiliate_id (your unique identifier)
campaign_id (campaign/creative tracking)
player_ip (for geofencing compliance)
Optional but recommended:
sub_id (granular campaign tracking)
landing_page (conversion funnel analysis)
device_fingerprint (cross-device attribution)
Returns: Unique click_token (90-day cookie lifespan). Store this for conversion matching.
/track/conversion - Player Registration/Deposit
Fires when player completes valued action. Registration, first deposit, qualified play - whatever triggers commission.
Critical: Include click_token from original click. Without it, you're flying blind on attribution.
Conversion types supported:
registration (account creation)
first_deposit (initial bankroll load)
qualified_player (meets wagering threshold)
redeposit (returning player value)
Response includes commission amount and player lifetime value projection. Use this data to optimize your highest-value traffic sources.
/stats/realtime - Live Performance Data
Pull current stats without waiting for daily reports. Updates every 60 seconds.
Query by affiliate_id, campaign_id, date range, or device type. JSON response with clicks, conversions, commission earned, pending revenue.
I run this endpoint every 5 minutes during peak traffic hours. Catches conversion drops instantly - you'll know if tracking breaks before you lose serious money.
/players/activity - Player Behavior Insights
Track referred player activity post-conversion. Game preferences, session frequency, lifetime deposits.
Why this matters: A player depositing $50/month for 18 months is worth 36x more than a one-time $500 whale. This endpoint shows you which traffic sources deliver sticky players versus bonus hunters.
Advanced Integration Features
Webhook Automation
Stop pulling data manually. Configure webhooks to push conversion events to your systems in real-time.
Set up via dashboard or POST to /webhooks/create with your endpoint URL. We'll fire JSON payloads on conversion events, commission updates, player milestones.
Webhook event types:
conversion.registered
conversion.deposited
commission.earned
commission.revised (rare, but happens with chargebacks)
player.milestone (custom triggers you define)
Includes retry logic with exponential backoff. If your endpoint is down, we'll keep trying for 72 hours before flagging the issue.
Cross-Device Attribution
Here's where most platforms fall apart. Player clicks your link on mobile, registers on desktop 6 hours later. Who gets credit?
You do. Our device fingerprinting tracks 23 data points - screen resolution, browser plugins, timezone, canvas fingerprint, WebGL renderer. Matches players across devices with 94.7% accuracy.
No additional implementation needed. It's baked into /track/click automatically.
Server-to-Server Postback
For affiliates running traffic through intermediary platforms (ad networks, DSPs), S2S postback eliminates cookie dependency.
Pass click_token through your traffic chain, fire postback directly to our servers on conversion. Bypasses browser restrictions, ad blockers, cookie cleaners.
Want to see how this stacks up against other solutions? Our compare integration capabilities page breaks down S2S implementation across major platforms.
Compliance & Data Handling
Nobody got into this to become a regulatory expert. But here's what you need to know.
All API traffic is encrypted (TLS 1.3 minimum). Player data is hashed - you never see PII unless explicitly authorized by operator agreement.
Geofencing is automatic. If a player clicks from a restricted state, /track/click returns "geoblocked" status. No commission credit, no compliance headache.
For detailed regulatory requirements by state, check our compliance requirements for API usage documentation. Covers New Jersey, Pennsylvania, Michigan, and emerging markets.
Rate Limits & Performance
Standard tier: 10,000 requests/hour across all endpoints.
Pro tier: 50,000 requests/hour.
Enterprise: Custom limits negotiated (we've handled 500K/hour for major networks).
Hit the limit and you'll get 429 status code with retry-after header. Implement exponential backoff in your integration - don't hammer the endpoint, you'll just extend the timeout.
Average response time: 47ms globally. Our CDN edge nodes in 12 US markets ensure sub-60ms responses even during peak NFL Sunday traffic.
Support & Implementation Assistance
Look, I know developers hate reading documentation. Sometimes you just need a human.
Technical support via Slack channel (response time under 15 minutes during business hours) or email for complex integration questions. We'll jump on a call for enterprise implementations.
Sample code libraries available in PHP, Python, Node.js, and Ruby. Copy, paste, customize. No need to build authentication logic from scratch.
Common integration time:
Basic tracking: 2-4 hours
Full webhook automation: 1-2 days
Custom multi-tier affiliate network: 1-2 weeks with our team's help
Questions on specific endpoints or edge cases? Hit our support team. We've integrated with everything from WordPress plugins to custom-built traffic management platforms - chances are we've solved your scenario before.
API Documentation: Complete Integration Guide for Casino Affiliates
Here's the reality: clunky integrations kill conversions. I've watched affiliates lose 12-18% of their revenue because their tracking setup couldn't handle cross-device attribution or mobile app installs.
That ends here. AffiliGaming's REST API gives you pixel-perfect tracking across every player touchpoint - desktop, mobile web, native apps, even smart TV interfaces. We're talking sub-50ms response times and 99.97% uptime, backed by the same infrastructure powering $2.3B in annual affiliate revenue.
This isn't another "developer documentation" maze. I'm walking you through real-world implementation, from authentication to advanced webhook automation. Whether you're running a casino affiliate platform with 50 sites or building custom tracking for a single high-traffic domain, you'll find exactly what you need.
Authentication & API Access
Most platforms won't tell you this, but authentication is where 60% of integration failures happen. Not here.
AffiliGaming uses OAuth 2.0 with rotating bearer tokens. You get API credentials the moment you're approved - no waiting for "technical review" or jumping through bureaucratic hoops.
Quick start authentication:
Pro tip: implement token refresh automation immediately. I've tested dozens of setups, and manual token management creates tracking gaps during off-hours. Check our getting started with platform integration guide for automated refresh scripts.
Sandbox Environment
Test everything before going live. Our sandbox mirrors production perfectly - same endpoints, same response times, just flagged test data.
Sandbox URL: https://sandbox-api.affligaming.com
Production URL: https://api.affligaming.com
No data pollution. No broken attribution from test clicks. Switch endpoints when you're ready.
Core Tracking Endpoints
These are your money-makers. Master these four endpoints and you'll handle 95% of affiliate scenarios.
/track/click - Player Click Attribution
Records initial player interaction. Captures device fingerprint, geo data, referral source.
Required parameters:
Optional but recommended:
Returns: Unique click_token (90-day cookie lifespan). Store this for conversion matching.
/track/conversion - Player Registration/Deposit
Fires when player completes valued action. Registration, first deposit, qualified play - whatever triggers commission.
Critical: Include click_token from original click. Without it, you're flying blind on attribution.
Conversion types supported:
Response includes commission amount and player lifetime value projection. Use this data to optimize your highest-value traffic sources.
/stats/realtime - Live Performance Data
Pull current stats without waiting for daily reports. Updates every 60 seconds.
Query by affiliate_id, campaign_id, date range, or device type. JSON response with clicks, conversions, commission earned, pending revenue.
I run this endpoint every 5 minutes during peak traffic hours. Catches conversion drops instantly - you'll know if tracking breaks before you lose serious money.
/players/activity - Player Behavior Insights
Track referred player activity post-conversion. Game preferences, session frequency, lifetime deposits.
Why this matters: A player depositing $50/month for 18 months is worth 36x more than a one-time $500 whale. This endpoint shows you which traffic sources deliver sticky players versus bonus hunters.
Advanced Integration Features
Webhook Automation
Stop pulling data manually. Configure webhooks to push conversion events to your systems in real-time.
Set up via dashboard or POST to /webhooks/create with your endpoint URL. We'll fire JSON payloads on conversion events, commission updates, player milestones.
Webhook event types:
Includes retry logic with exponential backoff. If your endpoint is down, we'll keep trying for 72 hours before flagging the issue.
Cross-Device Attribution
Here's where most platforms fall apart. Player clicks your link on mobile, registers on desktop 6 hours later. Who gets credit?
You do. Our device fingerprinting tracks 23 data points - screen resolution, browser plugins, timezone, canvas fingerprint, WebGL renderer. Matches players across devices with 94.7% accuracy.
No additional implementation needed. It's baked into /track/click automatically.
Server-to-Server Postback
For affiliates running traffic through intermediary platforms (ad networks, DSPs), S2S postback eliminates cookie dependency.
Pass click_token through your traffic chain, fire postback directly to our servers on conversion. Bypasses browser restrictions, ad blockers, cookie cleaners.
Want to see how this stacks up against other solutions? Our compare integration capabilities page breaks down S2S implementation across major platforms.
Compliance & Data Handling
Nobody got into this to become a regulatory expert. But here's what you need to know.
All API traffic is encrypted (TLS 1.3 minimum). Player data is hashed - you never see PII unless explicitly authorized by operator agreement.
Geofencing is automatic. If a player clicks from a restricted state, /track/click returns "geoblocked" status. No commission credit, no compliance headache.
For detailed regulatory requirements by state, check our compliance requirements for API usage documentation. Covers New Jersey, Pennsylvania, Michigan, and emerging markets.
Rate Limits & Performance
Standard tier: 10,000 requests/hour across all endpoints.
Pro tier: 50,000 requests/hour.
Enterprise: Custom limits negotiated (we've handled 500K/hour for major networks).
Hit the limit and you'll get 429 status code with retry-after header. Implement exponential backoff in your integration - don't hammer the endpoint, you'll just extend the timeout.
Average response time: 47ms globally. Our CDN edge nodes in 12 US markets ensure sub-60ms responses even during peak NFL Sunday traffic.
Support & Implementation Assistance
Look, I know developers hate reading documentation. Sometimes you just need a human.
Technical support via Slack channel (response time under 15 minutes during business hours) or email for complex integration questions. We'll jump on a call for enterprise implementations.
Sample code libraries available in PHP, Python, Node.js, and Ruby. Copy, paste, customize. No need to build authentication logic from scratch.
Common integration time:
Questions on specific endpoints or edge cases? Hit our support team. We've integrated with everything from WordPress plugins to custom-built traffic management platforms - chances are we've solved your scenario before.