Share a plan with a workspace member
Authorization
bearerAuth A personal API key (psk_…) or an OAuth access token (plan_at_…). Scopes: read, write.
In: header
Path Parameters
Project slug, e.g. recipe-box.
Plan handle within the project, e.g. PLAN-12.
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
application/json
application/json
application/json
curl -X POST "https://example.com/v1/projects/string/plans/string/sharing/collaborators" \ -H "Content-Type: application/json" \ -d '{ "role": "VIEWER" }'{ "collaborator": { "userId": "string", "role": "VIEWER" }, "rootPlanId": "string", "scopeNote": "string"}Push a plan and its Specs to the connected tracker POST
The response carries `push.belowReady`: every spec in the plan that is still below Ready, with its readiness label and why. It is `[]` for a plan where everything is Ready, and `push.belowReadyUnavailable` is true when the check could not run (which `[]` alone cannot tell you). Long plans list the first 10 and report the rest as `push.belowReadyOmitted`. Pushing is never blocked by any of it.
Add a Spec to a plan POST
Next Page