PlayStation Store API v2 Reference

Rate limiting

Each response carries your live usage in headers:

When the monthly quota is exhausted you get 429 RATE_LIMITED (with Retry-After = seconds to the 1st of next month). There is also a short-term burst limit of 120 requests per minute per IP to protect the service; exceeding it returns 429 with Retry-After to the next minute. Please cache responses in your own database rather than re-requesting the same data.

Response format

Every response is a JSON object with the same envelope:

{
  "success": true,
  "data": { ... } | [ ... ] | null,
  "meta": {
    "region": "US",
    "pagination": { "page": 1, "limit": 20, "total": 134 },
    "rate_limit": { "limit": 50000, "used": 12, "remaining": 49988, "reset_at": "2026-07-01T00:00:00Z" },
    "response_ms": 14
  },
  "error": null
}

On failure, success is false, data is null, and error is { "code": "STRING_CODE", "message": "…", "status": 4xx }. Errors your integration is expected to handle (e.g. REGION_NOT_IN_PLAN) additionally carry a machine-readable error.details object. For the region gate it includes requested_region, enabled_regions and the exact self-service call to enable it, so you can branch on fields instead of parsing the message. All responses also send X-API-Version: 2 and permissive CORS headers (Access-Control-Allow-Origin: *, methods GET, PUT, POST, OPTIONS).

Errors

Common query parameters

The game object

The game/product endpoints (/games, /games/{ppid}, /games/search, /deals, /demo…) all return the same object. Notable fields, grouped:

Prices are integers in the region’s minor units (scaled by decimalPlaces from /regions). For display, use the matching formatted… string. LowestEverPrice/LowestEverPlusPrice are null when no record exists. HoursLow/HoursHigh are in hours (-1 = unknown). Internal columns are never returned; use fields= to narrow the object further. VoiceLang and SubtitleLang are flat JSON arrays of strings and are [] when we have none: every element is a plain non-empty string, never a nested array, an object or a number. Elements are normally language codes (en, pt_BR, zh_Hant), but a small number of products were labelled by hand by our staff and carry readable names instead (English), so treat an element as an opaque string rather than assuming it parses as a code. VoiceLangByPlatform and SubtitleLangByPlatform are objects keyed by platform (PS4, PS5, PS3, VITA) and are {} when we have none; each value follows the same flat-array-of-strings rule. Every store-metadata field is null until we have observed it. StarRating is a number from 0 to 5, and IsAgeRestricted is 0, 1 or null.

What v1 does and does not have. The legacy v1 endpoint (/api.php) returns none of the store-metadata fields, none of the per-platform language objects, and none of the three store-price fields below, because v1 is frozen and its response shape does not change. It does return VoiceLang and SubtitleLang, and always has: the difference is the type. In v1 they are JSON-encoded strings you have to decode yourself; in v2 they are real JSON arrays.

The store’s own price fields

Three pricing fields come straight from the PlayStation Store rather than from our price history. They are v2 only, they are per region, and each is null until we have actually seen it on that storefront.

Unlike LowestEverPrice, the two formatted… companions here are always present and are null when we have no price, so you can read both keys without checking whether they exist.

Delisting: one more way a product is detected as gone

The PlayStation Store answers with HTTP 200 and a page containing no product at all once a product is permanently withdrawn. We used to read that as “page loaded, product still live”. We now recognise it and count it the same as a 404, which feeds the usual delist evidence counter.

What that means for you: nothing in the response shape changes. Delisted, PubDelisted and IsDelisted keep their meaning and their 0/1 type. But products that were gone from the store while we still reported them as live will now correctly report IsDelisted: 1, so if you branch on that flag expect a one-off step up in how many products match. A product is still only marked delisted after repeated evidence across several regions, and a delisting a human has ruled on by hand is never overridden.

Engineering notes & best practices

Everything below is exact, production-grade behaviour. The quickstart is enough to read prices; this is the precise contract for integrations that must stay correct under load.

Two independent limits: monthly quota & burst

• Monthly quota: your plan’s request budget, counted per calendar month and reset at 00:00 UTC on the 1st. v1 (/api.php) and v2 share one counter. Exhausting it returns 429 RATE_LIMIT_EXCEEDED; Retry-After = seconds to the 1st. One successful call = one unit, however many records it returns.
• Burst limit: a separate 120 requests/minute/IP across every endpoint (including unauthenticated and 404 traffic). Over it returns 429; Retry-After = seconds to the next minute. Independent of your monthly budget.
• Free meta endpoints: /status, /account, /account/usage, GET /regions and GET/PUT /account/regions never spend monthly quota (they still count toward the burst limit).
• Both surface live in headers: X-RateLimit-Limit/Used/Remaining and X-RateLimit-Reset (Unix epoch). Trust the header over a counter of your own.

The real unit is records, not calls

List endpoints return up to your plan’s page size (25 on Free, 200 on Business), so your true data ceiling is monthly_limit × max_page. Pull wide pages with precise filters instead of many tiny calls: same quota, far fewer round-trips.

Pagination

• page is 1-based; limit is clamped to [1, max_page] (default 20 or the plan cap, whichever is smaller). Out-of-range numbers clamp silently; a non-numeric value is 400 INVALID_PARAM.
• Deep paging is capped: an effective offset (page-1) × limit above 100,000 returns 400. Narrow with filters (region, platform, price, discount) rather than paging that far.
• with_total=0 skips the COUNT(*) and is noticeably faster on large result sets when you only need the next page. With it on, meta.pagination carries total, total_pages and has_more.
• Ordering is stable: every sort breaks ties by PPID descending, so a row never jumps between pages.

Filtering: exact semantics

• DLC and demos are hidden by default. Pass exclude_dlc=0 and/or exclude_demo=0 to include them.
• DLC has three states, not two. Nothing sent = base games only; exclude_dlc=0 = base games and add-ons together; only_dlc=1 = add-ons alone. Sending only_dlc=1 together with exclude_dlc=1 is a contradiction and returns 400 INVALID_PARAM rather than an empty list.
• is_bundle=1 keeps only bundles, products whose game groups two or more titles. It is the one filter that reads a column outside Products and Regions, and it does not change any other count.
• platform and genre are any-of (OR): platform=ps4,ps5 matches titles on either.
• sort=sale_price ranks by the PS Plus price; price by base price. Default sort popularity, default direction desc (asc for name).
• price_min/price_max take a human price in the region’s currency (e.g. 19.99), matched against the base price.
• /games/search resolves your text to at most the 200 closest name matches before filtering. It is for “find this game”, not enumeration.

Types & null handling

• Prices are integers in the region’s minor units (scaled by decimalPlaces from /regions). Don’t divide by 100 blindly: JP has 0 decimal places. For display, use the matching formatted… string.
• LowestEverPrice / LowestEverPlusPrice are null when unknown, with no sentinel integer to special-case. Their formatted… companions are absent, not null, in that case.
• LowestRecentPrice / LaunchPrice are also null when unknown, but their formatted… companions are always present and null alongside them. PriceCurrency is null or a 3-letter code, never an empty string.
• VoiceLang / SubtitleLang are arrays and are [], never null. The array is flat and every element is a non-empty string: no nested arrays, no objects, no numbers, no nulls. Most elements are language codes; a hand-labelled product returns readable names (English) instead, so do not assume an element parses as a code. VoiceLangByPlatform / SubtitleLangByPlatform are objects and are {}, never null or [], and each value obeys the same flat-array-of-strings rule.
• Every store-metadata field (NpTitleId, ConceptID, StarRating…) is null until observed. IsAgeRestricted is tri-state: 1, 0 or null, so test it with an explicit null check, not for truthiness.
• HoursLow / HoursHigh are floats in hours (e.g. 7.5); -1 = unknown. Difficulty is 1 to 10, -1 unknown.
• Flag/count fields (IsPS5, Platinum, Genre…) are integers, not JSON booleans.

Field projection

fields= can only narrow an object: it drops everything not listed, and unknown names are ignored (never an error). It shrinks payloads and your parsing surface; it cannot add or rename fields. Use the exact public names from the game object.

Caching

• List responses (/games, /deals) send Cache-Control: private, max-age=300. Reuse for 5 minutes, but note the private (per-key) flag: shared/CDN caches must not store them. /regions is cached 24h; the keyless /demo is public.
• Persist results in your own database and serve from there; call the API to refresh, not on every page view. Prices move over hours, not seconds.
• Responses Vary on X-API-Key, so never key a shared cache on the URL alone.

Robust error handling

• Branch on error.code (stable), never on error.message (may be reworded).
• 403 REGION_NOT_IN_PLAN carries structured error.details: requested_region, enabled_regions[], plan and the exact how_to_enable call. Branch on those, don’t parse prose.
• Honour Retry-After on every 429 and back off.
• GET is safe to retry (idempotent). PUT /account/regions with an unchanged list is a no-op that does not spend your once-per-24h change, so it is safe to call defensively.

Terms of use

On the Free and Indie plans, please show a “Powered by PlatPrices” attribution wherever the data appears. Pro and Business plans have no attribution requirement. We may throttle or revoke keys that abuse the service. Commercial use requires a paid plan.