Docs / OverviewSDK downloadsGitHub ↗
Developer signal / v2026.09

Ship the signal.
Keep the player.

One integration layer for permission, identity, delivery, and engagement across native apps and game engines.

Choose your SDKExplore the API
8Integration paths
2 BetaNative cores
5 PreviewEngine adapters

Start with the client

Use a publishable key in shipped applications. Server keys stay in infrastructure you control.

curl -X POST https://api.pushhub.kemegames.com/api/v1/devices/register \
  -H "Authorization: ApiKey $PUSHHUB_API_KEY" \
  -H "X-App-Id: $PUSHHUB_APP_ID" \
  -H "Content-Type: application/json" \
  -d '{
    "deviceToken": "<fcm-or-apns-token>",
    "platform": "android",
    "userId": "player_1842"
  }'

Base URL: https://api.pushhub.kemegames.com/api/v1

Pick a route

The same installation contract sits beneath every SDK, so identity and delivery stay consistent across platforms.

Client SDKsAndroid, iOS, Unity, Unreal, Flutter, React Native, Godot, and JavaScript.COMPARE INTEGRATIONS → REST APIInteractive request and response contracts generated from the production OpenAPI specification.OPEN REFERENCE → Release registryImmutable packages, support channels, file sizes, and SHA-256 verification data.VERIFY A RELEASE →