- Is the source set up correctly? Check source status, credentials, advertised capabilities, and compliance.
- What happened on recent buyer traffic? Inspect recent AdCP calls, responses, task statuses, and failures for that source.
Endpoint
GET /api/v2/storefront/inventory-sources/{sourceId}/diagnostics
Returns seller-facing diagnostics for one third-party sales-agent or modular
inventory source. The response combines the current source setup, recent AdCP
activity, test-run evidence, latency rollups, error rates, discovery
participation, demand impact, and developer handoff identifiers.
Request
Parameters
| Field | Type | Required | Notes |
|---|---|---|---|
sourceId | string (path) | Yes | Storefront-scoped inventory source ID. |
windowHours | integer (query) | No | Lookback window for activity and test-run rollups. Defaults to the service window, minimum 1, maximum 720 (30 days). |
Response
| Field | What it tells you |
|---|---|
source | Current setup state: source identity, status, endpoint, auth, advertised capabilities, and latest health. |
window | The lookback period and how much activity/test-run evidence was sampled. |
performance | Request/response counts, completion/failure/input-required rates, timeout rate, latency percentiles, and whether latency exceeded the configured threshold. |
toolBreakdown[] | Per-tool outcomes across all sampled calls, including get_products, create_media_buy, updates, and other AdCP tools. |
discoveryParticipation | Whether buyer discovery called, skipped, excluded, or timed out this source. |
outcomeMix | Whether calls returned products, returned no products, failed, timed out, waited for input, or were business-rejected. |
demandImpact | Buyer-demand impact estimate and notes for missed product opportunities. |
recentActivity[] | Most recent calls, responses, task statuses, errors, trace/correlation identifiers, and summaries. |
diagnosis | Severity, likely cause, next steps, and developer handoff details to share with the source operator. |
Errors
400 BAD_REQUEST—windowHoursis not a positive integer or is greater than720.401 UNAUTHORIZED— missing or invalid API key.404 NOT_FOUND— no inventory source with thissourceIdexists for the storefront.
Open the diagnostics surface
In the app, open Ask Murph, choose Help, then choose Diagnostics. For third-party sales-agent traffic, select the Debug calls tab. You can also open that tab directly by replacing<customer-id> with your
account id:
debugSourceId or debugTaskId:
Start with the inventory source
Open the storefront inventory source in the app, or call Get storefront readiness. ThesourceDiagnostics[] entry for each source gives the current operating picture:
| Field | What it tells you |
|---|---|
sourceStatus | Whether the source is active, pending, or disabled. |
auth | Whether the source requires credentials and whether they are configured. |
capabilities | Whether the source advertises support for product discovery, media-buy creation, updates, signals, and wholesale products. |
compliance | Latest AAO / AdCP compliance result for the source. |
debug | Sanitized advertised tools, channels, publisher domains, protocol version, billing support, and related capability metadata. |
health | Current source health, including latest error, latest success, and latest check timestamps when available. |
Inspect recent AdCP activity
For source-specific traffic, use Ask Murph > Help > Diagnostics > Debug calls and ask about the inventory source by name. Murph can inspect recent third-party sales-agent activity for the caller’s storefront: requests, responses, webhook/status changes, task IDs, task statuses, and sanitized payloads. This is the right path for questions like:- “Why did this source fail
get_products?” - “What did Interchange send to my sales agent?”
- “What did my sales agent return?”
- “Which recent calls are failed or waiting for input?”
- “Is this a protocol problem, an auth problem, or a business rejection?”
- “Where do I see whether this sales agent is slow or getting excluded?”
| Signal | How to read it |
|---|---|
| Tool | The AdCP operation, such as get_products or create_media_buy. |
| Task status | COMPLETED means the source finished; FAILED means the source rejected or errored; INPUT_REQUIRED means the source is waiting on seller action; PENDING or WORKING means the source has not finished yet. |
| Payload issue | A sanitized error or rejection message, when the source returned one. |
| Task ID | The correlation handle to share with the sales-agent operator or developer. |
| Timestamp | When Interchange observed the activity. |
Buyer discovery debug output
Buyer product discovery fans out to reachable sales agents in parallel. Slow or failing agents do not block fast agents. When a buyer calls discovery withdebug: true, the response can include agentResults[], which shows which
agents returned products, returned no products, failed, or were skipped.
Use this when you need the buyer-side view of a discovery request: which agents
were asked, which agents were skipped before fanout, and which agent-controlled
reason was returned.
Buyer debug output is scoped to that buyer request. Seller diagnostics are
scoped to the storefront inventory source. Use the seller view when you are
operating the source; use buyer debug output when you are reproducing one buyer
discovery call.
What this does not answer yet
The current diagnostics show source state and recent protocol activity. They do not yet provide a complete performance dashboard with source-level latency percentiles, timeout rates, exclusion counts, or “lost buyer demand” trends for each third-party sales agent. Those are product diagnostics we expect to grow into the inventory-source health view. Until then, combine:sourceDiagnostics[].healthfor the latest known source health.- Murph diagnostics for recent ADCP call details.
- Buyer discovery
agentResults[]withdebug: truefor one discovery request.
Practical checklist
When a source is not showing up or a buyer request did not return products:- Confirm the inventory source is active.
- Confirm credentials are configured if the source requires auth.
- Confirm the source advertises the needed capability, especially
get_productsfor product discovery. - Check source health for the latest error, success, and check timestamps.
- Ask Murph to inspect recent debug calls for that source.
- If reproducing a buyer discovery request, run discovery with
debug: trueand inspectagentResults[]. - If the failure is still unclear, share the source name, task ID, timestamp, and sanitized error with your sales-agent operator or Scope3 support.
Related
Inventory sources
Register and manage the sources behind your storefront
Get storefront readiness
Inspect readiness and per-source diagnostics
Product discovery
Understand buyer discovery and
agentResultsErrors
Shared Interchange error contract