Error Codes

Persistly uses a small structured error vocabulary.

Exact error categories make SDK handling simpler and give coding agents stable patterns to generate around. Keep your game-specific messaging separate from the platform error code itself.

Error Schema

These error codes and HTTP statuses are the current public runtime set.

Persistly uses a small structured error vocabulary. Keep the numeric HTTP status visible and map your game-specific UX on top of the stable error code.

HTTP 400invalid_request

The request body, parameters, or payload shape is invalid for the runtime contract.

HTTP 401unauthorized

The runtime key is missing, malformed, revoked, or does not belong to the target environment.

HTTP 404not_found

The referenced saveId does not exist in the environment identified by the runtime key.

HTTP 409conflict

The submitted baseVersion is stale. Persistly returns the canonical current save so the client can reconcile.

HTTP 413payload_too_large

The metadata or state payload exceeds Persistly's documented byte limits.

HTTP 429rate_limited

The client exceeded allowed request volume for the current environment or plan.

HTTP 500server_error

Persistly failed internally and the operation result should be treated as unknown.