stageTrackerProposal
POST /api/v1/trackers/{trackerId}/proposals
Durable standalone Tracker authoring. Current workspace membership and registered scoped Agent/account grants are required. If-Match identifies the record for record writes and the Tracker for lifecycle/schema writes. Retries replay durable results; bulk items have independent indexed outcomes. Schema preview is paginated and read-only. Breaking application requires explicit allowBreaking, bounded replacement mappings with record ETags and explicit migrationId to resume; incompatible records retain old values and inspectable immutable revisions. Archived and Git-authoritative ordinary writes fail explicitly. Human acceptance/sharing configuration requires the owning human. Query/native-view/Git/MCP/SDK lanes remain reserved.
Access
Section titled “Access”Use a credential with commentary.trackers.write.
Provider access, workspace membership, and agent grants are enforced separately. A token does not expand access to a repository or resource. Set up developer access.
Parameters
Section titled “Parameters”| Name | Location | Type | Required | Description |
|---|---|---|---|---|
trackerId |
path | string | Yes | |
If-Match |
header | string | Yes | |
Idempotency-Key |
header | string | Yes |
Request body
Section titled “Request body”Required. Supported content types: application/json.
| Field | Type | Required | Description |
|---|---|---|---|
bundle |
ProjectAgentPortableTracker | Yes | |
expectedSchemaRevisionId |
string | Yes | Minimum length: 1. Maximum length: 512. |
baseCommitSha |
string | Yes |
Call the endpoint
Section titled “Call the endpoint”Replace path placeholders and your credential. For body operations, create request.json using the required fields above; this command does not invent resource identifiers or consent.
curl --request POST \ 'https://commentary.dev/api/v1/trackers/<trackerId>/proposals' \ --header 'Authorization: Bearer <your-token>' \ --header 'Content-Type: application/json' \ --data-binary @request.jsonResponses
Section titled “Responses”| Status | Meaning | Payload |
|---|---|---|
200 |
Authorized domain result with the exact applicable ETag. | ProjectAgentstageTrackerProposalOutput |
400 |
Bounded v1 machine-readable failure. | object |
401 |
Bounded v1 machine-readable failure. | object |
403 |
Bounded v1 machine-readable failure. | object |
404 |
Bounded v1 machine-readable failure. | object |
409 |
Bounded v1 machine-readable failure. | object |
412 |
Bounded v1 machine-readable failure. | object |
413 |
Bounded v1 machine-readable failure. | object |
422 |
Bounded v1 machine-readable failure. | object |
428 |
Bounded v1 machine-readable failure. | object |
429 |
Bounded v1 machine-readable failure. | object |
500 |
Bounded v1 machine-readable failure. | object |
503 |
Bounded v1 machine-readable failure. | object |
Successful response fields
Section titled “Successful response fields”| Field | Type | Required | Description |
|---|---|---|---|
data |
ProjectAgentTrackerPortabilityReceipt | Yes | |
idempotencyReplayed |
boolean | No |
Recover from errors
Section titled “Recover from errors”Use the returned status and error body. Correct invalid fields before retrying; reconnect or narrow the target for authentication and permission errors. For conditional writes, reload the latest version before preparing a new request. Respect rate-limit headers and retry only when the operation’s idempotency contract permits it.
Contract and related guidance
Section titled “Contract and related guidance”Operation ID: stageTrackerProposal. Download the OpenAPI contract for complete constraints and code generation. Browse endpoints.