Skip to content

ESPER API REFERENCE (1.0.0)

Introduction

Welcome to Esper’s API documentation. The Esper API allows users to accomplish operations outside of the console. Some common uses for our APIs include observing device information and console activity, installing and updating apps, uploading files, and sending files to devices. Our users have also used the API to automate app updates, perform bulk actions, and more.

Esper API endpoints use REST-based architecture and return JSON responses.

See our documentation for:

Authentication

You need to create an API Key to interact with our APIs. Learn more about generating an API Key. You can also learn more about Esper and sign up for an account at esper.io/signup.

Some endpoints also require an Enterprise ID. This ID can be found in the API Management section of the Esper console.

Pagination

Responses may be paginated. Use the following parameters to query the data. A full list of parameters can be found on the endpoint’s documentation page.

ParameterData TypeExplanation
limitintegerLimit the data returned. Default = 20.
offsetintegerOffset to the first item returned. Default = 0.
orderingstringOrder the results set by the field name. Varies by endpoint.
nextstringPaginate to the next response set.
previousstringPaginate to the last set response.

Errors

We use standard HTTP status codes for success or failure. A typical error response may look something like this:

{
  "errors": [],
  "message": "error message",
  "status": 400
}
  • errors - List of error details
  • message - Error description
  • status - HTTP status code

Some common status codes and messages are:

NumberMessageExplanation
200OKThe request succeeded.
201Resource creationA resource was created.
401UnauthorizedThe API key is invalid.
404Not foundThe resource was not found.
429Rate limit exceededToo many requests. Wait a moment and try again.
500Server errorInternal error. Wait a moment and try again. If the issue persists, contact Esper.

See how our systems are doing by checking our status page.

Rate Limits

To ensure quality of service for all customers, we enforce rate limits for API requests. Most customers won’t hit this limit with normal use. In case you experience 429 or rate limit exceeded errors, we recommend the following:

  • Try sending requests in batches.
  • Begin with about 20 requests at a time and building up from there.
  • Ensure your scripts are efficient and don’t contain redundant calls.
  • Reach out to your account manager to discuss your options.
Download OpenAPI description
Languages
Servers
Mock server
https://develop-api.esper.io/_mock/openapi
https://{foo}-api.esper.cloud/api

Company Settings

Operations

Application

Operations

Application V1

Operations

AndroidDevice

Operations

Device Group

Operations

Token (Deprecated)

Operations

Commands V2

Operations

Enterprise Policy

Operations

Geofence

Operations

Content

Operations

User (Deprecated)

Operations

User

Operations

Blueprint (Deprecated)

Operations

Directory Record

Operations

Tile Icon

Operations

Alerts

Operations

Alarms

Operations

Wallpapers

Operations

Device Telemetry

Operations

Daily and Custom Reports

Operations

SSO Connections

Operations

Roles

Operations

Personal Access Token

Operations

Blueprints API

Operations

Custom Actions API

Operations

System

Operations

Pipelines

Operations

Stages

Operations

Target Lists

Operations

Targets

Operations

Device Groups

Operations

Operation Lists

Operations

Operations

Operations

Pipeline Runs

Operations

Stage Runs

Operations

Target Runs

Operations

Device

Operations

Device Heartbeat

Operations

Device Apps

Operations

Device Enrollment in EMM

Operations

Operations

Operations

DeviceOperations

Operations

Get all DeviceOperations for a specific Operation

Request

Security
apiKey
Path
operationsIdstring(uuid)required

ID of the Operation

Example: 5743470f-7dcc-4a92-8a4b-f41b1cea69ed
Query
limitinteger
offsetinteger
stateinteger

Following are the Device Operation States and their corresponding integer values

DEVICE_OPERATION_CREATED     = 10
DEVICE_OPERATION_INITIATED   = 20
DEVICE_OPERATION_DISPATCHED  = 30
DEVICE_OPERATION_PROCESSING  = 40
DEVICE_OPERATION_SUCCESS     = 50
DEVICE_OPERATION_FAILURE     = 60
DEVICE_OPERATION_CANCELLED   = 70
DEVICE_OPERATION_TIMEOUT     = 80
DEVICE_OPERATION_COMPLETED   = 90
orderingstring

Field to order the results by. Prefix with '-' to reverse the order.

Enum"created_at""state""updated_at"
curl -i -X GET \
  'https://develop-api.esper.io/_mock/openapi/v0/operations/5743470f-7dcc-4a92-8a4b-f41b1cea69ed/devices/?limit=0&offset=0&state=0&ordering=created_at' \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

Device Operation information for the Operation

Bodyapplication/json
contentobject
Response
application/json
{ "content": { "count": 0, "previous": "string", "next": "string", "results": [ … ] } }

Get a Operations for a device

Request

Security
apiKey
Path
deviceIdstring(uuid)required

ID of the Device

Example: 17d384d3-29bd-4dd4-af64-d02b9d6d54ee
curl -i -X GET \
  https://develop-api.esper.io/_mock/openapi/v0/devices/17d384d3-29bd-4dd4-af64-d02b9d6d54ee/operations/ \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

Operations information for the Device

Bodyapplication/json
countinteger
previousstring
nextstring
resultsArray of objects(OperationWithStats)
Response
application/json
{ "count": 0, "previous": "string", "next": "string", "results": [ { … } ] }

Get a specific DeviceOperations for a specific Operation (Device Operation Status)

Request

Security
apiKey
Path
operationsIdstring(uuid)required

ID of the Operation

Example: 5743470f-7dcc-4a92-8a4b-f41b1cea69ed
deviceIdstring(uuid)required

ID of the Device

Example: 17d384d3-29bd-4dd4-af64-d02b9d6d54ee
curl -i -X GET \
  https://develop-api.esper.io/_mock/openapi/v0/operations/5743470f-7dcc-4a92-8a4b-f41b1cea69ed/devices/17d384d3-29bd-4dd4-af64-d02b9d6d54ee/ \
  -H 'Authorization: Bearer <YOUR_TOKEN_HERE>'

Responses

Device Operation information for the Operation

Bodyapplication/json
contentobject(DeviceOperationWithStats)
Response
application/json
{ "content": { "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "operation_id": "cb4ede3c-a5d1-45e3-a9d2-fe83accbce52", "device_id": "3bafab7b-4400-4bcf-8e6e-09f954699940", "state": "CREATED", "reason": "", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z", "device_operation_activity": [ … ] } }

MultiOS Remote Viewer

Operations

Device V2

Operations

VPP License Management

Operations

VPP App Management

Operations

Tenant Apps

Operations

Apple App Store

Operations

App List

Operations

Webclips

Operations

Provisioning Profiles

Operations

Esper Apps

Operations

Tenant Esper Apps

Operations

Command Request

Operations

Command Status

Operations

Converge

Operations

Converge Command

Operations

DEP Sync Request

Operations

ABM Provisioning

Operations

APNs certificate

Operations

DEP Tokens

Operations

VPP Token Management

Operations

Google Enterprise

Operations

FoundryBuilds

Operations

FoundryDeviceModels

Operations

FoundryEvents

Operations

Reports API

Operations

Query API

Operations

Ingest API

Operations