PSN:B2B API

Use the PSN:B2B API to connect a wholesale PlayStation Store code catalog to reseller operations: check regional inventory, create funded orders, read order status, and retrieve delivered codes after payment and stock are confirmed.

Integration path

Register a free PSN:B2B business account.
Request API access by submitting a ticket on the support page. Choose the "API Access Request" topic from your registered account. Access is reviewed manually for eligible B2B accounts; timing depends on account details, risk checks, and support workload.
Receive your Bearer API key. Base URL: https://psnb2b.org/api/v1
Fund the account with a supported cryptocurrency method shown at checkout before placing live orders.
Start with inventory and a small test order before automating higher-volume fulfillment.

Authentication

API requests use an Authorization Bearer header. Keys are account scoped and should be stored server side, rotated if exposed, and used only by the approved business account. Authorization: Bearer <YOUR_API_KEY>

curl -sS "https://psnb2b.org/api/v1/inventory" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Accept: application/json"

Core endpoints

GET/inventory

Returns the regional catalog available to the account, including denominations, currencies, current account pricing, and stock state where exposed.

GET/balance

Returns the account balance and pricing tier visible to the approved business account.

POST/orders

Creates a funded wholesale order for a selected region, denomination, and quantity. The buyer remains responsible for choosing the correct PSN account region.

GET/orders/{id}

Returns the latest order state so the reseller can keep its own storefront and customer messaging in sync. (pending, paid, delivered, failed)

GET/orders/{id}/codes

Retrieves delivered PlayStation Store codes for completed orders, with delivery records available for reconciliation and support.

POST/claims

Submits a code-support case inside the published policy window for invalid-code, wrong-region, or technical delivery issues. Code Support Policy

Integration readiness

Before you automate PlayStation Store code delivery

The API works best when it mirrors the same controls a B2B buyer already needs: region fit, funded orders, delivery records, and a clear path for code-support evidence.

Controls to keep in your reseller system

Region and currency validationShow the PlayStation account region, catalog region, currency, and denomination before the buyer or support team treats a code as usable.
Funded order checksConfirm account balance, payment state, order ID, quantity, and selected SKU before creating higher-volume orders.
Delivery reconciliationStore delivered-code retrieval time, order status, and storefront order reference so finance and support can read the same record.
Code-support case dataKeep order_id, delivered code, error screenshot, attempted redemption time, and PSN account region ready for policy review.

Connect the API page to the right operating page

API access does not replace catalog review, account-region checks, or the public code-support policy. Use the linked pages as source material for your internal runbook.

Live regional catalogCheck denominations, currency, and account-region fit before mapping SKUs into your own store.Open catalog Code-support policyUse this when your integration needs a standard evidence set for invalid, wrong-region, or already-used reports.Read policy API access requestSubmit the business account, use case, and integration context through the support channel for review.Request access Account termsReview buyer responsibility, digital delivery rules, region restrictions, and acceptable-use boundaries before launch.Read terms

Access is reviewed account by account

The API is an account feature for approved B2B buyers. Availability, limits, key rotation, webhooks, and operational controls may depend on account review, risk checks, and active support guidance.

Rate limits

Rate limits and order-placement controls may apply by account, endpoint, and operational risk. Treat response headers and support guidance as the source of truth for the active limit.

Webhooks

Webhook setup can be requested through support for approved accounts that need order-status events. Integrations should still reconcile against the order-status endpoint.

PSN:B2B API questions for reseller operations

How do I get API access for PSN:B2B?

Create a PSN:B2B business account and submit an API access request from the support page. API keys are issued manually for eligible B2B accounts after account and use-case review.

Is the PSN:B2B API a separate paid product?

The API is an account feature for approved B2B buyers. Partners pay for the wholesale codes they order; any account-specific limits or requirements are confirmed during review.

Which workflows can the API support?

The API is intended for catalog sync, balance checks, order creation, order-status checks, delivered-code retrieval, and code-support case submission.

What controls should stay in place when delivery is automated?

Approved accounts can automate internal reseller fulfillment, but region, denomination, payment state, stock state, and support materials should remain validation gates before any code is released to an end customer.

API automation

PSN gift card API for reseller platforms that need automated fulfillment

This solution is for teams that already have demand and want less manual work: sync available PlayStation Store inventory, place wholesale orders, track delivery, and prepare code-support evidence through a structured API workflow.

Read API documentation

Browse catalogue Request API key

Documents:Wholesale Overview 2026 (PDF) · API Integration Guide (PDF) · Code Support Policy (PDF)