Viewing Apps and Versions Linked to Blueprints: Console and API Options

Android

Improved Title: No single view of apps across Blueprints — Console and API options

---

When you need to audit which applications and versions are configured across multiple Blueprints, the Esper Console does not provide a single consolidated view. You must either review each blueprint individually in the Console, or use the Esper API to retrieve and aggregate that data programmatically.

Why this happens

The Esper Console displays application configurations in the context of a single blueprint at a time. There is no cross-Blueprint app inventory view built into the Console, so auditing more than one blueprint requires either repeated manual navigation or an API-based approach.

Option A: View apps in a single blueprint (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. This lists every application explicitly configured in that blueprint, along with its version name and version code.
4. Repeat steps 2–3 for each blueprint you need to audit.

Verify: Each blueprint's Apps section should list the package name, version name, and version code for every app configured in that blueprint. If an app does not appear here, it has not been explicitly added to that blueprint.

Option B: Retrieve app data across all Blueprints (Esper API)

1. Obtain your enterprise_id by navigating to Company Settings in the Esper Console. The enterprise ID is displayed on that page.
2. Retrieve all blueprint IDs by calling:

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

   This returns a list of every blueprint in your enterprise, each with its own blueprint_id.
3. For each blueprint_id returned, retrieve the full blueprint details:

   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 data across all blueprint IDs to build your complete cross-Blueprint application inventory.

Verify: Cross-check at least one blueprint's API response against its Apps section in the Esper Console. The package_name and version_name values returned by the API should match exactly what is shown in the Console.

API returns no application data for a blueprint

If the API response contains no application fields for a given blueprint, confirm the following before retrying:

• The blueprint has applications explicitly added in its Apps section in the Esper Console. Apps applied through a Group default or a separate policy are not reflected in the blueprint's API response.
• The blueprint_id you are querying matches the intended blueprint. Cross-check the ID against the list returned in step 2.

If this doesn't resolve it

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

• The enterprise_id and blueprint_id you are querying
• The full API response body showing the missing fields
• A screenshot of the Apps section for the same blueprint in the Esper Console

Contact Esper Support with this information for further investigation.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.