Skip to main content
Set the creator that a user boosts. After setting a boost, the user’s payments are automatically attributed to the creator.

POST /sponsors Behavior

POST /sponsors works as upsert:
Current StateRequested creatorKeyBehavior
No boost-Create new
Boosting same creatorSameReturn current state
Boosting different creatorDifferentChange after 30-day cooldown
Boost ended-Reactivate
POST /sponsors handles both boost creation and changes in one API.

Flow

1. Search/Select creator  →  2. Create boost (POST /sponsors)  →  3. Future payments auto-attributed

Create Boost

If campaignId is not specified, it will be automatically assigned to the currently active campaign.
When operating multiple campaigns for a single game, you must specify campaignId to distinguish between campaigns.
Request
curl -X POST "https://sandbox-sdk-api.playcamp.io/v1/server/sponsors" \
  -H "Authorization: Bearer ak_server_xxx:secret" \
  -H "Content-Type: application/json" \
  -d '{
    "userId": "user_12345",
    "creatorKey": "ABC12",
    "callbackId": "game-session-abc123"
  }'
Response (201 Created)
{
  "data": {
    "userId": "user_12345",
    "campaignId": "campaign_001",
    "creatorKey": "ABC12",
    "isActive": true,
    "sponsoredAt": "2024-01-15T10:30:00.000Z"
  }
}

Remove Boost

If campaignId is not specified, boost from the active campaign will be removed. Request
curl -X DELETE "https://sandbox-sdk-api.playcamp.io/v1/server/sponsors/user/user_12345" \
  -H "Authorization: Bearer ak_server_xxx:secret"

Optional Parameters

FieldTypeDescription
campaignIdstringCampaign ID (auto-assigned to active campaign if not specified)
callbackIdstringWebhook tracking ID (included in webhook events)
isTestbooleanTest mode (does not create actual data)

Error Handling

HTTPCodeDescriptionAction
400BAD_REQUESTNo active campaign or 30-day cooldownCheck campaign status, wait for cooldown
404NOT_FOUNDCreator not foundVerify creatorKey