Look up an error code
pc_lookup_errorResolve Partner Center errors by looking up a numeric code or HTTP status. Returns meaning, known causes, remediation, documentation link, and typical scenarios.
Instructions
Look up a Partner Center error by its numeric code or HTTP status and return what it means, its known causes, the remediation, the doc link, and the scenarios where it usually appears. Use this when you already have a clean code. If you have a raw error response, pc_decode_error is better — it extracts the code and correlation id for you first. For a symptom described in prose with no code at all, use pc_diagnose. Read-only, offline, deterministic. Exactly one of code or httpStatus must be supplied; supplying neither returns ok:false. An unknown code returns ok:false with suggestions listing every code in the pack.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| code | No | Partner Center error code as a string, e.g. "900400" or "20002". Matched exactly, so strip surrounding text first. Takes precedence when both this and `httpStatus` are given. Supply this or `httpStatus`. | |
| httpStatus | No | HTTP status code to list errors for, e.g. 400 or 403. Use this when you have no Partner Center code — it returns every documented error with that status, so expect several. Ignored when `code` is supplied. Supply this or `code`. |
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. |