Integration status
PSN:B2B API availability and integration status
PSN:B2B does not currently publish a self-service REST contract or a working public /api/v1 endpoint. This page separates the ordering flow available today from the items that must be confirmed before any integration work begins.
Current status
No public API contract is available
The public site does not expose a documented REST base URL, self-service API keys, endpoint schemas, rate limits, or webhook events. A support request may establish whether a future integration is suitable, but it does not by itself confirm availability.
01No live endpoint reference
Do not call guessed /api/v1 paths or treat earlier endpoint examples as an active interface.
02Web ordering is available
The supported public path is the authenticated business account, regional catalog, account funding, and web order flow.
03Support records requirements
Share the business account, use case, regions, expected volume, and record needs. A verified contract must follow before engineering starts.
How to order and keep usable records today
The existing web workflow already covers the decisions an integration would need to preserve. Keep those controls visible instead of designing around an unconfirmed interface.
- 1
Choose the PlayStation Store region, currency, denomination, and quantity from the live catalog.
- 2
Fund and place the order through the authenticated account flow; do not assume stock or timing before confirmation.
- 3
Keep the order ID, delivery timestamp, account region, and any code-support evidence with the buyer record.
What to define before discussing automation
A useful integration brief explains the buyer workflow and its controls. It should not start with invented endpoints.
- Region and SKU rulesList the PSN account markets, currencies, denominations, catalog labels, and wrong-region checks your system must preserve.
- Account and payment stateDefine who may order, how funded balance is checked, and which payment or risk state permits release.
- Order and delivery recordsSpecify order references, statuses, delivery timestamps, code retrieval records, and reconciliation ownership.
- Support evidenceDocument how your team will retain the customer error, attempted redemption time, account region, and order evidence.
Do not begin against an assumed contract
Engineering should begin only after PSN:B2B provides a verified base URL, authentication model, endpoint and error schemas, limits, webhook rules, support boundary, and change policy. Until then, the web account is the operational source of truth.
API availability questions
Does PSN:B2B currently offer a public API?
No public self-service API contract or working public /api/v1 endpoint is published on this site. Current purchasing uses the authenticated web account and store flow.
Can I build against the endpoint names that appeared here before?
No. Endpoint names, Bearer keys, limits, and webhook events are not an active public contract and must not be used for implementation.
What can a reseller use now?
A reseller can create a business account, review the regional catalog, fund the account, place web orders, and retain order and delivery records for support.
What should I send to support about a possible integration?
Send the account, business use case, target regions, expected order pattern, required records, security constraints, and support workflow. The reply must explicitly confirm availability and scope before development.