Authenticated instance control, permission checks and durable result exchange
Served by the optional standalone Source manager. Instances initiate every exchange; this is not a Server or public MCP endpoint. The operation path chooses owner/connect/poll/reply/sync/execution/results/stopped-targets/close and the applicable fields. Source observations continue to go directly to the PC Server.
Authorization
BearerAuth Bearer credential resolved to an opaque authenticated Principal by the Server deployment.
In: header
Path Parameters
^[A-Za-z0-9_.-]+$1 <= length <= 256Value in
- "owner"
- "connect"
- "poll"
- "reply"
- "sync"
- "execution"
- "results"
- "stopped-targets"
- "close"
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/source-management/instances/string/owner" \ -H "Content-Type: application/json" \ -d '{}'{}Source manager reverse channel close POST
Previous Page
Inventory ownership data missing after switching Access enforcement on POST
Inspect the Scopes that were written while Access was disabled: missing Artifact owners, pending Review Candidates without an owner attestation, and, when named, the background Principal's per-Scope write authority. Produces no change. In enforced mode completes as a deployment administrator; in disabled mode completes without authentication because the Server cannot yet protect anything. A background Principal check requires an available Access store; otherwise it reports 503 relationship_management_unavailable. Use the offline ownership command to check the proposed background Principal before enforcement is enabled.

