Build a ready-to-send request
pc_build_requestBuild a Partner Center REST request as structured data: resolved URL, headers, and body skeleton. Use it to get a request object for your own client without sending it.
Instructions
Assemble one Partner Center REST request as structured data: the resolved URL with your params substituted into the path placeholders, concrete headers (Bearer plus a freshly generated MS-RequestId on writes), and a request-body skeleton derived from the operation's documented fields. Use this when you want an object to send from your own client. For a language-specific code snippet use pc_generate_call instead, and to lint a request you already wrote use pc_validate_request. Read-only and offline: the request is constructed and handed back, never sent, and the Authorization header is a <access-token> placeholder — no credentials are read or required. Not idempotent in one respect: a random MS-RequestId is minted on each call for write operations, so reuse the returned value across retries rather than calling again. Unsupplied placeholders are reported in missingParams rather than failing, and an unknown id returns ok:false with suggestions.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Exact scenario id in kebab-case, e.g. "create-cart". Case-sensitive; discover ids with pc_list_scenarios or any pc_plan_* tool. | |
| params | No | Values for the {placeholder} segments in the operation's path, as a flat string-to-string map — e.g. { "customer-id": "c7f6e4b1-...", "subscription-id": "..." }. Keys are matched loosely, so "customer-id", "customerId", and "customerid" all work. Values are URL-encoded for you. Omit it, or leave some out, to get the URL with those placeholders intact and the names listed in `missingParams`. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| ok | Yes | True when the call succeeded and `data` is populated; false when `error` explains why not. | |
| data | No | The result payload. Present only when `ok` is true. | |
| error | No | Human-readable reason the call failed. Present only when `ok` is false. | |
| suggestions | No | Valid values to retry with, returned alongside `error` when the requested identifier was not found. |