{"templateId":"api_docs","sharedDataIds":{"apiDocsStore":"api-docs-openapi.yaml","sidebar":"sidebar-sidebars.yaml"},"props":{"definitionId":"openapi.yaml","settings":{"baseUrlPath":"/openapi"},"disableAutoScroll":true,"seo":{"title":"/v2/blueprints/","llmstxt":{"hide":true},"description":"Creates a new blueprint in the enterprise. Blueprints define device configuration and management rules (for example, kiosk/device mode settings, app/file payloads, Wi-Fi networks, and OS-specific restrictions). After you create a blueprint, you can publish versions and then assign/apply it to devices through separate workflows. Creating a blueprint doesn’t affect devices by itself. Devices won’t change until the blueprint (and typically a specific version) is assigned/applied via a separate endpoint/workflow. Because the create response is list-shaped, you should read the new blueprint ID from content.results[0].id. If your workflow relies on versioning, capture both the blueprint id and the returned version_id (if present in your create response), since later calls may require one or the other. Workflow: After creating a bluerprint, assign a device or group to it using POST https://{foo}-api.esper.cloud/api/v2/converge"},"dynamicMarkdocComponents":[],"metadata":{"subType":"openapi-operation"},"compilationErrors":[],"markdown":{"partials":{},"variables":{"rbac":{"teams":["anonymous"]},"user":{},"remoteAddr":{"hostname":"develop-api.esper.io","port":4000,"ipAddress":"216.73.216.6"},"lang":"default_locale","env":{"PUBLIC_REDOCLY_BRANCH_NAME":"main"}}},"pagePropGetterError":{"message":"","name":""}},"slug":"/openapi/blueprints_blueprints-api/paths/~1v2~1blueprints~1/post","userData":{"isAuthenticated":false,"teams":["anonymous"]},"isPublic":true}