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.
Public docs should focus on the release path: ps_test_ for development, ps_live_ for production, one explicit API origin, and a clear create/load/sync verification checklist before launch.
Workflow
Test the real runtime path, not just mocks or local abstractions.
Point your SDK at https://api.persistly.app for production-grade runtime traffic.
Verify create, load, sync, and at least one conflict path before shipping a live build.
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
Release Checklist
A game should pass these checks before you ship ps_live_ traffic.
Create a save in a non-production environment and persist the returned saveId locally.
Load the same save from a second device or fresh client session to verify canonical state restore.
Force a sync conflict with an older baseVersion and confirm your game handles the canonical server save intentionally.
Rotate from ps_test_ to ps_live_ only after the stage flow works exactly as expected.