No single view for apps across Blueprints — use Console or API to audit

Android

When you need to audit which applications and versions are configured across multiple Blueprints, the Esper Console does not provide a consolidated, cross-Blueprint view. You must inspect each Blueprint individually in the Console, or retrieve the data in bulk using the Esper API.

Why this happens

App configurations are stored per Blueprint, not in a shared registry. The Esper Console surfaces app details only within the context of a single Blueprint, so there is no built-in list view that aggregates applications and versions across all Blueprints in your enterprise.

Option 1: View apps in a single Blueprint using the Esper Console

1. In the Esper Console, navigate to Blueprints.
2. Click the name of the blueprint you want to inspect.
3. Select the Apps section within the blueprint.
4. Review the list of applications, noting the Version Name and Version Code for each app.
5. Return to Blueprints and repeat for each blueprint you need to audit.

Option 2: Retrieve app data across all Blueprints using the API

Use this approach when you manage many Blueprints and need a complete inventory without opening each one manually.

1. Locate your enterprise_id by navigating to Company Settings in the Esper Console. You need this value in every API call.
2. Retrieve all Blueprint IDs for your enterprise:

   GET /api/v0/enterprise/{enterprise_id}/blueprint/

   The response returns an array of Blueprint objects, each containing a unique id field. Collect all id values.
3. For each Blueprint ID, retrieve the full Blueprint configuration:

   GET /api/v0/enterprise/{enterprise_id}/blueprint/{blueprint_id}/

4. From each response, extract the following fields for every application entry:
   • app_name
   • package_name
   • version_name
   • version_code
5. Aggregate the extracted fields across all Blueprint IDs to build your complete cross-Blueprint application inventory.

Verify: Cross-check the package_name and version_name returned by the API against the app details shown in Blueprints → [Blueprint Name] → Apps in the Esper Console for at least one blueprint. If both sources match, your API results are accurate.

If the API returns no application data for a Blueprint

Confirm the following before concluding there is a data problem:

• The blueprint has applications explicitly configured under its own Apps section in the Esper Console — apps inherited from a Group default or applied through a separate configuration are not returned in the Blueprint API response.
• The blueprint_id you are querying matches the correct blueprint in your enterprise.

If this doesn't resolve it

If the API response is missing application fields that are visibly configured in the Esper Console, collect the following before contacting support:

• The enterprise_id and blueprint_id used in your API call
• The full API response body showing the missing or empty application data
• A screenshot of the Apps section of the same blueprint in the Esper Console, confirming the apps are visible there

Contact Esper Support with these details.

Still need help?

If you need assistance viewing apps across Blueprints or auditing through Console or API, please submit a support ticket and include details about which Blueprints you're trying to audit and whether you're using Console or API access.