Skip to main content
Deprecated. This page documents the v2 buyer API, which is closed to new API clients and switches off on 1 December 2026. Use V3 instead: see Move a v2 buyer REST integration to V3. The conversion endpoint, Log event, stays open.
GET /api/v2/buyer/storefronts/{storefrontId} Returns a single storefront with canonical transaction readiness and separate rolled-up connection state: connected, requiresCredentials, and your registered customerAccounts. Use readiness.canTransact for availability. Use connection fields to diagnose buyer credential setup, for example after registering credentials or completing OAuth. Use the capabilities endpoint when you need source-level diagnostic rows.

Request

curl

Parameters

Response

customerAccounts is scoped to the authenticated buyer. On Storefront MCP discovery calls, supplying an opaque account ID without that buyer/storefront grant fails closed with ACCOUNT_NOT_FOUND and details.reason: "account_not_authorized_for_buyer". Use an account returned for the current buyer; an account visible to another buyer is not reusable.

Errors

  • 401 UNAUTHORIZED — missing or invalid bearer token.
  • 404 NOT_FOUND — the storefront does not exist or is not visible to the caller.
See Errors for the full error contract.

Storefront tasks

All storefront operations

Register source credentials

Connect a source that requires credentials

List storefronts

Paginated summaries

Get storefront capabilities

Source-level capability diagnostics