Describe debugger scenarios supported by a resource

GET/v1/debug-sessions/capabilities

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
NameLocationTypeRequiredDescription
targetKindqueryfunction | web_app | connector | skillYes—
resourceIdquerystringYes—

Body schema

This endpoint does not require a request body.

None.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

200Resource-specific debugger capabilities and active execution bindingapplication/json
FieldTypeRequiredDescription
schemaVersioncomputer_agents_diagnostic_v1Yes—
targetobjectYes—
target.kindfunction | web_app | connector | skillYes—
target.resourceIdstringYes—
target.resourceNamestringYes—
bindingobjectYes—
binding.modedeployed_revisionYes—
binding.revisionstringYes—
readybooleanYes—
readinessobjectNo—
readiness.runtimeSupportedbooleanNo—
readiness.credentialsConnectedbooleanNo—
readiness.activebooleanNo—
readiness.packageValidbooleanNo—
readiness.reasonstringNo—
connectorobjectNo—
connector.connectorIdstringYes—
connector.providerstringYes—
connector.runtimeSupportedbooleanYes—
connector.unsupportedReasonstringNo—
connector.probeActionstringNo—
connector.credentialsobject[]Yes—
connector.credentials[].idstringYesUnique identifier.
connector.credentials[].namestringYesHuman-readable name.
connector.credentials[].identitystringNo—
connector.credentials[].statusvalid | invalidYesCurrent lifecycle status.
connector.credentials[].isDefaultbooleanYes—
connector.credentials[].updatedAtstringNoISO 8601 timestamp.
connector.capabilitiesobject[]Yes—
connector.capabilities[].idstringYesUnique identifier.
connector.capabilities[].accessread-only | interactiveYes—
connector.capabilities[].descriptionstringNoHuman-readable description.
connector.capabilities[].inputSchemaobjectNo—
skillobjectNo—
skill.skillIdstringYes—
skill.sourcepublished_version | saved_version | editor_candidate | system_bundleYes—
skill.versionIdstringYes—
skill.contentDigeststringYes—
skill.runtimeContractVersioncustom-skill-v2Yes—
skill.activebooleanYes—
skill.packageValidbooleanYes—
skill.requiredContextSupportedbooleanNoThis backend supports loading required custom Skill instructions into every live thread execution. Clients must require true before starting a mandatory custom Skill test.
skill.manifestobjectYes—
skill.manifest.entrypointSKILL.mdYes—
skill.manifest.fileCountintegerYes—
skill.manifest.totalBytesintegerYes—
skill.manifest.runnableFilesstring[]Yes—
skill.manifest.requiredRuntimespython | node | shell[]Yes—
skill.issuesobject[]Yes—
skill.issues[].codestringYes—
skill.issues[].severityerror | warningYes—
skill.issues[].messagestringYesMessage text.
skill.issues[].pathstringNoWorkspace-relative file path.
skill.versionsobject[]Yes—
skill.versions[].idstringYesUnique identifier.
skill.versions[].labelstringYes—
skill.versions[].sourcepublished_version | saved_version | editor_candidate | system_bundleYes—
skill.versions[].contentDigeststringYes—
scenariosobject[]Yes—
scenarios[].idfunction.http_request | web_app.route_request | connector.connection_health | connector.runtime_access | connector.tool_call | skill.package_validation | skill.runtime_readinessYesUnique identifier.
scenarios[].titlestringYesDisplay title.
scenarios[].descriptionstringNoHuman-readable description.
scenarios[].inputSchemaobjectNo—
scenarios[].stepsobject[]No—
scenarios[].steps[].idstringYesUnique identifier.
scenarios[].steps[].titlestringYesDisplay title.
scenarios[].steps[].descriptionstringYesHuman-readable description.
scenarios[].steps[].statuspending | running | passed | failed | skippedYesCurrent lifecycle status.
scenarios[].steps[].durationMsintegerNo—
scenarios[].steps[].summarystringNo—
scenarios[].steps[].evidenceobjectNo—
scenarios[].steps[].errorobjectNo—
scenarios[].steps[].error.codestringNo—
scenarios[].steps[].error.messagestringNoMessage text.
400Invalid diagnostic target
None.
403Active organization or debugger permission required
None.
404Target resource not found
None.
502Connector runtime could not be reached
None.
503Connector diagnostics are not configured for this deployment
None.
Describe debugger scenarios supported by a resource
Loading...
Response 200
Loading...
See the ACP quickstart and SDK flow