Skip to content

gplay orders view

Look up one or more Google Play orders by order ID — the admin-side commerce diagnostic: a human or agent holds an order ID from a buyer complaint or a payout report and reads its state, total, and line items. This is the order lookup boundary of the commerce surface; real-time purchase-token verification is a runtime API gplay does not wrap (CONTEXT.md "Order" / ADR-0031).

Pass a single order ID for a detailed lookup (orders.get) or several to look them up together (orders.batchget, 1–1000 IDs per request — more is a usage error). batchget is all-or-nothing: if any ID is unknown or belongs to another package, the whole request fails. The order ID looks like GPA.1234-5678-9012-34567. The package defaults to the repo's .gplay/config.json pin when --package is omitted. This is a direct application-scoped read — it opens no Edit.

The human views show a compact summary (single: order id, state, total, creation time, line items; multiple: one line per order); --output json passes the Order (single) or BatchGetOrdersResponse (batch) through verbatim (ADR-0003), including the fields the summary omits (buyer address, tax, order history, sales channel, …).

Reading orders requires the service account to hold the CAN_VIEW_FINANCIAL_DATA permission (never part of a Role bundle); a 403 names it. An unknown order ID fails with exit 30.

[experimental] — the surface may still evolve (ADR-0010).

gplay orders view <orderId> [<orderId>...] [flags]
FlagDescription
--output stringoutput format: table, json, or markdown (default: auto — table on TTY, json in pipes/CI)
--package stringAndroid package name (overrides .gplay/config.json pin)
FlagDescription
--account stringname of a stored Account to use (overrides env and active Account)
--retry intretry transient failures (transport errors, 5xx, 429) up to N times with exponential backoff (default: 0, no retry)
--service-account stringpath to a service-account JSON, or inline JSON content (overrides --account, env, and active Account)
--timeout durationper-request API timeout, e.g. 30s or 2m (default: 60s for control-plane calls, none for uploads)
-v, --verboselog flow steps to stderr (info level)