Execute an interactive debugger session
POST
/v1/debug-sessionsExecutes the selected scenario synchronously and returns ordered, redacted diagnostic evidence.
How to call this endpoint
Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.
Path, query, and header parameters
These parameters control which ACP object the endpoint acts on and how the request is processed.
Path parameters
None.
Query parameters
None.
Body schema
Content type: application/json · Required
| Field | Type | Required | Description |
|---|---|---|---|
| target | object | Yes | — |
| target.kind | function | Yes | — |
| target.resourceId | string | Yes | — |
| scenarioId | function.http_request | Yes | — |
| input | object | Yes | — |
| input.method | GET | POST | PUT | PATCH | DELETE | No | — |
| input.path | string | No | Workspace-relative file path. |
| input.body | object | No | — |
| input.expectedRevision | string | No | — |
| input.timeoutMs | integer | No | — |
What the API returns
Each response code below includes the documented payload shape for the ACP API.
201Completed diagnostic session, including expected target failuresapplication/json
| Field | Type | Required | Description |
|---|---|---|---|
| schemaVersion | computer_agents_diagnostic_v1 | Yes | — |
| id | string | Yes | Unique identifier. |
| status | running | passed | failed | Yes | Current lifecycle status. |
| target | object | Yes | — |
| target.kind | function | web_app | connector | skill | Yes | — |
| target.resourceId | string | Yes | — |
| target.resourceName | string | Yes | — |
| scenario | object | Yes | — |
| scenario.id | function.http_request | web_app.route_request | connector.connection_health | connector.runtime_access | connector.tool_call | skill.package_validation | skill.runtime_readiness | Yes | Unique identifier. |
| scenario.title | string | Yes | Display title. |
| scenario.description | string | No | Human-readable description. |
| scenario.inputSchema | object | No | — |
| scenario.steps | object[] | No | — |
| scenario.steps[].id | string | Yes | Unique identifier. |
| scenario.steps[].title | string | Yes | Display title. |
| scenario.steps[].description | string | Yes | Human-readable description. |
| scenario.steps[].status | pending | running | passed | failed | skipped | Yes | Current lifecycle status. |
| scenario.steps[].durationMs | integer | No | — |
| scenario.steps[].summary | string | No | — |
| scenario.steps[].evidence | object | No | — |
| scenario.steps[].error | object | No | — |
| scenario.steps[].error.code | string | No | — |
| scenario.steps[].error.message | string | No | Message text. |
| binding | object | Yes | — |
| binding.mode | deployed_revision | Yes | — |
| binding.revision | string | Yes | — |
| request | object | Yes | — |
| steps | object[] | Yes | — |
| steps[].id | string | Yes | Unique identifier. |
| steps[].title | string | Yes | Display title. |
| steps[].description | string | Yes | Human-readable description. |
| steps[].status | pending | running | passed | failed | skipped | Yes | Current lifecycle status. |
| steps[].durationMs | integer | No | — |
| steps[].summary | string | No | — |
| steps[].evidence | object | No | — |
| steps[].error | object | No | — |
| steps[].error.code | string | No | — |
| steps[].error.message | string | No | Message text. |
| result | object | No | — |
| outcome | object | Yes | — |
| outcome.summary | string | Yes | — |
| outcome.likelyCause | string | No | — |
| outcome.suggestedFix | string | No | — |
| startedAt | string | Yes | ISO 8601 timestamp. |
| completedAt | string | Yes | ISO 8601 timestamp. |
| durationMs | integer | Yes | — |
| redacted | true | Yes | — |
400Invalid target
None.
403Active organization or debugger permission required
None.
404Target resource not found
None.
Execute an interactive debugger session
Loading...
Response 201
Loading...