Skip to main content
POST
Create the enterprise-tier blueprint

Permissions

Requires a service user or personal access token with the ManageAccountSnapshots permission at the enterprise level.

Behavior

Creates the enterprise-tier blueprint. A blueprint defines the declarative environment configuration for Devin sessions. An enterprise can have only one active blueprint. The request body field contents is optional. Omit it to create an empty blueprint. The call validates the YAML and stores it as the first version of the blueprint. Creating a blueprint does not trigger a build. There is no enterprise-level builds endpoint. Builds run per organization through Trigger Build. Each organization build includes the enterprise blueprint.

Errors

  • 409 Conflict: An enterprise blueprint already exists. Use Update Enterprise Blueprint to change it.
  • 422 Unprocessable Entity: contents is not valid blueprint YAML. The detail field starts with Invalid YAML: and names the problem.

Authorizations

Authorization
string
header
required

Service User credential (prefix: cog_)

Body

application/json
contents
string | null

YAML body for the new blueprint. Omit to create an empty blueprint.

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.

blueprint_id
string
required
created_at
integer
required
repo_name
string | null
required
type
enum<string>
required
Available options:
enterprise,
org,
repo
updated_at
integer
required
build_on_default_branch_commit
boolean | null

Whether each push to the repo's default branch builds the environment. Null unless this is a repo's root blueprint.

report_check_runs
boolean | null

Whether each commit build is reported as a GitHub check run on the commit. Null unless this is a repo's root blueprint.

source
enum<string> | null

Where the YAML is authored: 'git' (synced from .devin/blueprint.yaml in the repo) or 'database' (edited via the API/UI). Always null for enterprise- and org-tier blueprints.

Available options:
git,
database