01
Use a ps_test_ runtime key for development, QA, and staging traffic, then switch to ps_live_ only in production builds.
Testing And Environments
Validate the integration in stage first, then promote the exact same flow to production.
Use ps_test_ keys while developing and switch to ps_live_ only after the same save flow passes against real runtime traffic.
Test Flow
Test the real runtime path, not just mocks or local abstractions.
02
Point your SDK at https://api.persistly.app for production-grade runtime traffic.
03
Verify create, load, sync, and at least one conflict path before enabling live runtime traffic.
Environment Rules
Keep stage and production behavior intentionally separate.
Create a project and keep stage and prod environments separate from day one.
Use ps_test_ keys in development and QA only. Never ship them as production credentials.
Use ps_live_ only in production builds and store them in the same secret/config channel as your other release credentials.
Default public API origin: https://api.persistly.app
Live Key Checks
A game should pass these checks before it sends ps_live_ traffic.
01
Create an account in a non-production environment and persist accountId plus accountSessionToken locally.
02
Load the same account and slot from a fresh client session to verify canonical data restore.
03
Force a sync conflict with an older baseVersion and confirm your game handles the cloud conflict branch intentionally.
04
Rotate from ps_test_ to ps_live_ only after the stage flow works exactly as expected.