Retrieves a paginated list of all Blueprint V2 blueprints in the enterprise, with optional filtering and sorting. Returns an array of BlueprintV2 objects matching the provided filters; supports filtering by name (case-insensitive or exact), by app or app version IDs across Android, iOS, and Windows, by file or Wi-Fi network references, and by iOS provisioning profile. Results can be ordered by any supported field using the ordering parameter.

About List Blueprints (V2)

Blueprints in Esper define the desired state for managed devices — grouping app assignments, device settings, policies, and content into a reusable configuration template. Blueprint V2 is the current, supported version of the blueprint system; Blueprint V1 is deprecated. This endpoint lists all blueprints scoped to the enterprise, enabling integrators to build UIs, trigger automated deployments, or audit which blueprints reference a given app, file, or network configuration.

Key Fields / Query Parameters

name — Filter by blueprint name, case-insensitive partial match

name_exact — Filter by exact name, case-sensitive

ordering — Sort results by a field (prefix with - for descending); combine multiple fields with commas (e.g., -created_at,-updated_at)

settings__android__app_id — Filter to blueprints that include a specific Android app (by Esper app UUID)

settings__android__app_version_id — Filter to blueprints that include a specific Android app version

settings__ios__app_id / settings__ios__app_version_id — Same as above for iOS apps

settings__windows__app_id / settings__windows__app_version_id — Same as above for Windows apps

settings__android__file_id — Filter to blueprints that reference a specific managed file

settings__android__wifi_network_id — Filter to blueprints that include a specific Wi-Fi network profile

settings__ios__provisioning_profile_id / settings__ios__provisioning_profile_version_id — Filter by iOS provisioning profile or profile version

Common Use Cases

Listing all blueprints to populate a blueprint selection UI or dashboard

Finding which blueprints reference a specific app version before pushing an update or deprecating a version

Auditing all blueprints that use a particular Wi-Fi network or managed file

Retrieving all iOS blueprints that include a specific provisioning profile

Best Practices

Use settings__* filter parameters when tracing blueprint dependencies on a specific resource — this is faster than fetching all blueprints and filtering client-side

Use name for fuzzy search and name_exact when integrating with systems that require precise name matching

Paginate results using next and previous links in the response for large blueprint libraries

Workflow

Call GET /api/v2/blueprints/ with any relevant filter parameters

Inspect the count field in the response to determine if pagination is needed

Iterate through next links to retrieve subsequent pages if next is non-null