Skip to main content
Real-world integration cases from game studios, showing the full flow and development tasks for each integration pattern.

​
Common Prerequisites

These are required for all integration methods. See Overview for details.
1

Get API Keys

Create a project on PlayCamp platform and obtain your Server Key.
EnvironmentURL
Sandboxhttps://sandbox-sdk-api.playcamp.io
Livehttps://sdk-api.playcamp.io
2

Register Webhook URL

Register a webhook URL to receive event notifications from PlayCamp on your game server. See Webhook Events.
3

Integration Verification

To publish a campaign, you must call 3 required APIs (POST /sponsors, POST /coupons/validate, POST /payments) at least once each in the Live environment. Calls with isTest: true count as verification.

​
Choose Your Integration Method

WebView + Webhook

Use PlayCamp’s built-in WebView UI for the fastest integration. No additional UI development needed.Best for: Quickly providing creator boost functionality

Direct Server API

Build your own UI for creator selection and boost. Full control over the game UX.Best for: Custom creator selection UI matching your game’s style

Partner Gateway

Partner Gateway relays authentication, webhook conversion, and payment sync. Minimizes changes to existing systems.Best for: Integrating while keeping existing API specifications (prior consultation required)
Both methods can be used simultaneously. For example, use WebView for boost and Server API for payment registration.

​
FAQ

​
How should we handle the PlayCamp entry icon in-game?

You can freely design the PlayCamp entry point (icon/button) within your game. There are no specific size or placement guidelines — place it where it feels natural in your game UI. Contact your PlayCamp representative if you need official assets.

​
Can we test in Sandbox first?

Yes. All APIs can be tested in the Sandbox environment (https://sandbox-sdk-api.playcamp.io) first. Sandbox is completely isolated from Live. You can also use the isTest: true parameter to verify integration without creating real data. See Test Mode.

​
What if we have multiple campaigns?

When running multiple campaigns for one game, you must specify campaignId in API calls to distinguish between campaigns. If campaignId is omitted, the request is automatically assigned to the currently active campaign.