Blueprint managed config update via API not pushed to devices — trigger convergence manually

Android

When you update a managed configuration in a Blueprint via API and include "publish": true, the Blueprint is promoted to its published state but assigned devices do not receive the change. No configuration update appears on the devices.

Why this happens

Publishing a Blueprint and converging devices to that Blueprint are two separate operations in Esper's API. Setting "publish": true in a PUT request updates the Blueprint's published state only — it does not dispatch a convergence job to enrolled devices. Devices receive updates only when a convergence command is explicitly triggered after publishing.

How to update a managed configuration and push it to devices

Find the target Blueprint ID. List all Blueprints in your enterprise to identify the one you want to update:
```
GET https://{{tenant_name}}-api.esper.cloud/api/v2/blueprints/?limit=100&offset=0
```
Note the id value for the target blueprint in the response.
Fetch the current Blueprint payload. Retrieve the full Blueprint details so you can build your update on top of the existing configuration rather than overwriting unrelated fields:
```
GET https://{{tenant_name}}-api.esper.cloud/api/v2/blueprints/{{blueprint_id}}/
```
Copy the managed_config block from the response to use as the base for your PUT request body.
Publish the Blueprint with the updated managed configuration key. Submit a PUT request with the modified managed_config object and "publish": true:
```
PUT https://{{tenant_name}}-api.esper.cloud/api/v2/blueprints/{{blueprint_id}}/
```
Include the full updated managed_config block in the request body along with "publish": true. A successful response confirms the Blueprint is now in its published state.
Trigger device convergence. After publishing, dispatch an explicit convergence command to push the updated Blueprint to all assigned devices. In the Esper API reference, locate the converge or apply endpoint under the Blueprints section and call it with your blueprint_id. This step is required — without it, devices remain on their previously converged state.

Verify

Verify: In the Esper Console, navigate to Devices & Groups → [Device Name] → Blueprint. The Blueprint status should show as In Sync within a few minutes of triggering convergence, confirming the device has received and applied the updated managed configuration.

If this doesn't resolve it

Before contacting support, collect the following:

The blueprint_id used in the PUT and convergence requests
The full API response body from the PUT request, including any error codes or status fields
The full API response from the convergence request
A screenshot or exported Activity Feed entry from Devices & Groups → [Device Name] → Activity Feed showing the device's Blueprint state
The device's serial number or Esper device ID

Contact Esper Support with the above information and reference the Blueprint ID and the approximate time the convergence command was dispatched.

Still need help?

If you're still experiencing issues with blueprint managed config updates not syncing to your devices, submit a support ticket and include your blueprint configuration details, the device IDs affected, and the timestamp when you triggered the update.