Set the creator that a user boosts. After setting a boost, the user’s payments are automatically attributed to the creator.Documentation Index
Fetch the complete documentation index at: https://playcamp.io/docs/llms.txt
Use this file to discover all available pages before exploring further.
POST /sponsors Behavior
POST /sponsors works as upsert:
| Current State | Requested creatorKey | Behavior |
|---|---|---|
| No boost | - | Create new |
| Boosting same creator | Same | Return current state |
| Boosting different creator | Different | Change after 30-day cooldown |
| Boost ended | - | Reactivate |
POST /sponsors handles both boost creation and changes in one API.Flow
Create Boost
If
campaignId is not specified, it will be automatically assigned to the currently active campaign.- cURL
- Node SDK
- Go SDK
Remove Boost
IfcampaignId is not specified, boost from the active campaign will be removed.
Request
- cURL
- Node SDK
- Go SDK
Optional Parameters
| Field | Type | Description |
|---|---|---|
campaignId | string | Campaign ID (auto-assigned to active campaign if not specified) |
callbackId | string | Webhook tracking ID (included in webhook events) |
isTest | boolean | Test mode (does not create actual data) |
Error Handling
| HTTP | Code | Description | Action |
|---|---|---|---|
| 400 | BAD_REQUEST | No active campaign or 30-day cooldown | Check campaign status, wait for cooldown |
| 404 | NOT_FOUND | Creator not found | Verify creatorKey |