Skip to content

List all policies in enterprise
Stable

Request

⚠️ Legacy feature. Compliance Policies (along with Templates, which apply them) are a legacy Esper product. For new device configuration work, use Blueprints instead — Compliance Policies remain available for existing Template-based deployments. See Introduction to Compliance Policies: https://help.esper.io/hc/en-us/articles/12653153592977-Introduction-to-Compliance-Policies

Retrieves all Compliance Policies configured for the enterprise.

Returns the enterprise's Compliance Policies — legacy, Template-applied device restriction/permission profiles — with optional filtering by name and active state.

About Compliance Policies A Compliance Policy is a set of device-configuration permissions and restrictions — screen and unlock behavior (keyguard, safe boot), connectivity (USB, tethering, NFC), communication (SMS, outgoing/incoming calls, dialer), hardware (camera, screenshots), and system controls (factory reset, ADB, side-loading, Play Store, app uninstall, date/time configuration) — that gets applied to a device after it has already been provisioned through a Template. They're commonly used to make a post-provisioning change to a Kiosk-mode device, such as temporarily re-enabling the status bar or ADB to pull a bug report, without re-provisioning the device. Templates and Compliance Policies are legacy Esper products; Blueprints are the current, recommended way to define device configuration for new work.

Key Fields / Query Parameters

  • name — Filter policies by name
  • is_active — Filter to only active (or inactive) policies
  • limit — Page size for pagination
  • offset — Pagination offset

Common Use Cases

  • Auditing which legacy Compliance Policies still exist on Template-provisioned devices
  • Finding an existing policy by name to reuse rather than duplicate on an older Template-based deployment
  • Checking is_active status across all policies during a legacy-device configuration review

Best Practices

  • For new device configuration, use Blueprints instead of creating additional Compliance Policies
  • Filter by is_active=true when looking for policies currently in use on legacy Template devices
  • Paginate with limit/offset for enterprises with many policies

Workflow

  1. GET this endpoint to review existing Compliance Policies on legacy Template devices
  2. POST a new policy only if the device fleet is still Template-based and not yet migrated to Blueprints
  3. Apply the policy's uuid to devices or groups still on the legacy Template system
Security
esper_cloud_api_apiKey
Path
enterprise_idstring, (uuid)required

ID of the enterprise

Query
namestring

filter by policy name

is_activeboolean

filter by Active policies

limitinteger

Number of results to return per page.

Default:20
offsetinteger

Return results from this index.

Default:0
cURL
curl -i -X GET \
  'https://develop-api.esper.io/_mock/openapi/enterprise/{enterprise_id}/policy/?name=string&is_active=true&limit=20&offset=0' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

successful operation

Bodyapplication/json
countintegerrequired
nextstring or null, (url)
previousstring or null, (url)
resultsArray of objects(esper_cloud_api_EnterprisePolicy)required
Response
{
  "count": 0,
  "next": "string",
  "previous": "string",
  "results": [
    { … }
  ]
}