When to Use This Method
- You want to build a creator selection UI matching your game’s style
- You want seamless integration with your game’s UX flow
- You need to control boost registration/removal timing via game logic
Full Flow
Development Tasks
| # | Task | Owner | Description |
|---|---|---|---|
| 1 | Creator search/selection UI | Game Client | Creator list, search, selection screens |
| 2 | Creator query API integration | Game Server | Query creator/campaign data |
| 3 | Boost registration API | Game Server | User-creator matching |
| 4 | Payment registration API | Game Server | Send in-game purchases |
| 5 | (Optional) Webhook receiver | Game Server | Receive external change events |
Step 1: Query Creators (Game Server)
Query creator information from your game server to display in your game client.Creator Search
- cURL
- Node SDK
- Go SDK
Campaign Creators
You can also query only creators participating in a specific campaign.- cURL
- Node SDK
- Go SDK
Details: API Reference - Query Endpoints
Step 2: Register Boost (Game Server)
When the user selects a creator, register the boost from your game server.- cURL
- Node SDK
- Go SDK
Boost Change Rules
POST /sponsors operates as an upsert:
| Current State | Behavior |
|---|---|
| No boost | Create new |
| Same creator boosted | Return current state |
| Different creator boosted | Change after 30-day cooldown |
| Boost ended | Reactivate |
Details: Creator Boost
Step 3: Register Payments (Game Server)
When an in-game purchase occurs, send the payment information to PlayCamp. It’s automatically attributed to the boosted creator.- cURL
- Node SDK
- Go SDK
Details: Payment Registration
Step 4: (Optional) Webhook Receiver
With direct Server API integration, your game server already knows boost results since it makes the API calls directly. However, webhooks are useful when:- A PlayCamp admin manually changes a boost
- You want to verify payment registration results asynchronously
- You want to receive coupon redemption events
Details: Webhook Events
Step 5: Settlement
Monthly settlement is processed based on payment data.- Revenue Close — Payment data aggregated at end of each month
- Revenue Reconciliation — Match PlayCamp settlement data with your internal records
- Settlement Payment — Payment after reconciliation confirmation
- Creator Settlement — PlayCamp distributes revenue to creators
Details: Settlement