Create an app
Establish the tenant and app boundary for credentials, devices, and messaging.
API and SDKs
A clean push surface for the backend you already trust.
Register devices, manage player context, fire events, operate campaigns, and inspect outcomes through explicit contracts and scoped credentials.
Illustrative API request202 Accepted
Overview
Audience
Messages
Delivery
Settings
Live workspace
POST /event-triggers/fire
Auth
Scoped keyIdentity
IdempotentDispatch
AsynchronousCurrent flow
EventNameplayer.reward_ready
DeviceTokenResolved before storage
TemplateVariablesValidated payload
Example data for product illustration. Not customer performance.
Integrate once. Keep provider complexity behind the boundary.
Your game services speak one app-scoped API while PushHub owns provider adaptation, durable dispatch, retries, and operational evidence.
How it works
The shortest responsible path to a production send.
Issue a scoped key
Grant only the API capabilities required by the calling service.
Register devices
Store provider tokens with player identity and useful device properties.
Send or fire
Use direct notifications, campaigns, or idempotent event triggers.
Capability depth without the fine-print surprise.
Current and planned capabilities are labeled directly, so teams can evaluate PushHub without confusing vision for availability.
REST resources
Use documented JSON endpoints for apps, devices, segments, campaigns, templates, triggers, and analytics.
Scoped API keys
Create named credentials with explicit permissions and revoke them from the workspace.
OpenAPI contract
Explore a machine-readable specification and hosted reference documentation.
JavaScript SDK
A typed JavaScript client provides an early integration path while additional SDK coverage matures.
In the game
Designed around game-service responsibilities.
Device lifecycle
Register, update, or deactivate a token as identity and app state change.
Transactional push
Send to a known player or device from a trusted game-service action.
Event automation
Publish a game event and let durable triggers handle the timing and provider path.
The contract includes failure behavior.
Authentication, idempotency, tenant ownership, quota enforcement, validation, and normalized errors are part of the integration surface, not footnotes.
Least privilege
Keys receive only the scopes their service needs.
Hashed secrets
Raw API keys are shown once and stored as hashes.
Idempotent events
Event keys are hashed before persistence and duplicate work is rejected.
Questions teams ask before they commit.
Your app still configures its own provider credentials, but your backend uses one PushHub API surface for both delivery paths.
Build the next player return.
Start with one app, one meaningful moment, and one audience worth reaching.