Updates a blueprint's top-level record by ID.

This performs a full replacement of the blueprint's editable fields using the BlueprintV2Put schema. It updates the blueprint record itself, not a specific version; to change the configuration devices actually receive, publish a new version instead.

About Update Blueprint Because Converge applies a specific version rather than the blueprint record directly, updating the blueprint itself is typically limited to metadata-level changes rather than configuration changes. If the goal is to change what devices receive (apps, files, restrictions, and so on), the correct approach is to create a new blueprint version rather than editing the existing blueprint record.

Common Use Cases

Renaming a blueprint or updating its top-level metadata

Correcting a blueprint record without affecting any of its published versions

Best Practices

Confirm whether the change belongs on the blueprint record or on a new version before calling this endpoint; device-facing configuration changes belong on a version

Provide the full set of editable fields in the request body, since this is a full replacement rather than a partial update

Workflow

Call GET /v2/blueprints/{blueprint_id}/ to review the current record

Prepare the full BlueprintV2Put payload with the updated fields

PUT to this endpoint to apply the update

Confirm the change with a follow-up GET