Returns company settings. Formerly known as get your enterprise information.
ESPER API REFERENCE (1.0.0)
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:
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.
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.
| Parameter | Data Type | Explanation |
|---|---|---|
| limit | integer | Limit the data returned. Default = 20. |
| offset | integer | Offset to the first item returned. Default = 0. |
| ordering | string | Order the results set by the field name. Varies by endpoint. |
| next | string | Paginate to the next response set. |
| previous | string | Paginate to the last set response. |
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 detailsmessage- Error descriptionstatus- HTTP status code
Some common status codes and messages are:
| Number | Message | Explanation |
|---|---|---|
| 200 | OK | The request succeeded. |
| 201 | Resource creation | A resource was created. |
| 401 | Unauthorized | The API key is invalid. |
| 404 | Not found | The resource was not found. |
| 429 | Rate limit exceeded | Too many requests. Wait a moment and try again. |
| 500 | Server error | Internal error. Wait a moment and try again. If the issue persists, contact Esper. |
See how our systems are doing by checking our status page.
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
Overview
Languages
Servers
Mock server
https://api.esper.io/_mock/openapi
https://{foo}-api.esper.cloud/api
- Mock serverhttps://api.esper.io/_mock/openapi/v1/enterprise/{enterprise_id}/
- https://develop-api.esper.cloud/api/v1/enterprise/{enterprise_id}/
curl -i -X GET \
'https://api.esper.io/_mock/openapi/v1/enterprise/{enterprise_id}/' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>'successful operation
A short 10-char representation of the enterprise, separated by hyphens. Field is optional, as system will auto-generate a value if none is provided.
Registered Name of the enterprise
Registered address of the enterprise.
City, State, Country location of the enterprise
Person who is the point of contact for the enterprise
Contact email address of the enterprise
This field will have details about emm enrollment if the enterprise is emm enrolled
Response
application/json
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "short_code": "string", "registered_name": "string", "registered_address": "string", "location": "string", "zipcode": "string", "contact_person": "string", "contact_number": "string", "contact_email": "user@example.com", "wifi_lte_toggle_flag": true, "emm": { "google_enterprise_id": "string" }, "created_on": "2019-08-24T14:15:22Z", "updated_on": "2019-08-24T14:15:22Z" }
Security
apiKey
Registered address of the enterprise.
City, State, Country location of the enterprise
Person who is the point of contact for the enterprise
Contact email address of the enterprise
- Mock serverhttps://api.esper.io/_mock/openapi/v1/enterprise/{enterprise_id}/
- https://develop-api.esper.cloud/api/v1/enterprise/{enterprise_id}/
curl -i -X PATCH \
'https://api.esper.io/_mock/openapi/v1/enterprise/{enterprise_id}/' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: */*' \
-d '[object Object]'successful operation
A short 10-char representation of the enterprise, separated by hyphens. Field is optional, as system will auto-generate a value if none is provided.
Registered Name of the enterprise
Registered address of the enterprise.
City, State, Country location of the enterprise
Person who is the point of contact for the enterprise
Contact email address of the enterprise
This field will have details about emm enrollment if the enterprise is emm enrolled
Response
application/json
{ "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08", "name": "string", "short_code": "string", "registered_name": "string", "registered_address": "string", "location": "string", "zipcode": "string", "contact_person": "string", "contact_number": "string", "contact_email": "user@example.com", "wifi_lte_toggle_flag": true, "emm": { "google_enterprise_id": "string" }, "created_on": "2019-08-24T14:15:22Z", "updated_on": "2019-08-24T14:15:22Z" }