Create an org- or repo-tier blueprint
Snapshot Setup (Organization)
Create an org- or repo-tier blueprint
Create a blueprint. type is inferred from repo_name.
Per spec, this never auto-triggers a build — callers must
POST /builds explicitly.
POST
Create an org- or repo-tier blueprint
Permissions
Requires a service user with theManageRepoBlueprints permission at the organization level. Creating org-tier blueprints requires the ManageOrgSnapshots permission.
Behavior
Creates an org- or repo-tier blueprint. A blueprint defines the declarative environment configuration for Devin sessions. Mutating a blueprint does not auto-trigger a build — you must explicitly call the builds endpoint.Blueprints do not exist independently of your environment configuration. Creating a blueprint with a
repo_name also adds that repository to the environment — there is no separate endpoint to register the repo first. The repository is cloned into the environment on the next build, and indexing is kicked off for it.The reverse holds too: removing a repository from the environment (the Include in environment toggle in the UI) deletes every blueprint for that repo, including all of its workspace scopes.owner/repo); an unknown or inaccessible repo returns 404 and no blueprint is created. If an active blueprint already exists for that repo and scope, the request returns 409 — use the update endpoint instead.Authorizations
Service User credential (prefix: cog_)
Path Parameters
Organization ID (prefix: org-)
Example:
"org-abc123def456"
Body
application/json
Response
Successful Response
Public Blueprint resource shape.
Note: the type enum may grow in the future; clients MUST gracefully
handle unknown values. YAML contents are fetched separately via
GET /blueprints/{id}/contents.

