---
title: "Get your company settings"
method: GET
path: "/v1/enterprise/{enterprise_id}/"
tags: ["esper_cloud_api_Company Settings"]
---

# Get your company settings

`GET /v1/enterprise/{enterprise_id}/`

Retrieves the current company settings for the specified enterprise.Use this endpoint to read enterprise-level configuration including contact information, location details, EMM enrollment status, and the enterprise's display name.About Get Company Settings
This endpoint (formerly "Get Enterprise Information") returns the EnterpriseV1 object for your enterprise — the root configuration record that identifies your organization within Esper. It includes both read-only system fields (id, short_code, created_on, updated_on, emm) and user-editable fields such as name, contact details, and location. The emm field surfaces whether the enterprise is enrolled in Google EMM and, if so, its google_enterprise_id. All editable fields can be updated via PATCH /v1/enterprise/{enterprise_id}/.

**Key Fields**

enterprise_id (path, required) — UUID of the enterprise to retrieve

id (read-only) — UUID of the enterprise record

short_code (read-only) — Auto-generated 10-character identifier for the enterprise

name — Display name of the enterprise

registered_name — Formal legal name of the organization

registered_address — Registered business address

location — City, state, and country of the enterprise

contact_person / contact_number / contact_email — Primary point-of-contact details

wifi_lte_toggle_flag — Whether the data saver mode feature is enabled (only present if the feature is active)

emm — Google EMM enrollment details, including google_enterprise_id; null if not EMM-enrolled

**Common Use Cases**

Reading enterprise metadata to populate an integration's configuration or audit log

Confirming EMM enrollment status and retrieving the linked google_enterprise_id

Retrieving the current values of all editable fields before issuing a PATCH update

**Best Practices**

Use this endpoint to read current state before calling PATCH — it ensures you don't unknowingly overwrite values you didn't intend to change

Treat id, short_code, created_on, updated_on, and emm as read-only; they cannot be updated via PATCH

Cache the enterprise_id at integration setup time rather than fetching it on every request

**Workflow**

Call GET /v1/enterprise/{enterprise_id}/ with the enterprise UUID

Inspect the response for the fields relevant to your use case (e.g., emm for EMM enrollment status, contact_email for contact details)

Use the returned field values as the baseline if you plan to follow up with a PATCH update

## Path parameters

- `enterprise_id` string, uuid, required

## Response `200`

successful operation

- EsperCloudApiEnterpriseV1
  - `id` string, uuid, required — Id of the enterprise
  - `name` string, required — Name of the enterprise
  - `short_code` string, required — 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` string — Registered Name of the enterprise
  - `registered_address` string — Registered address of the enterprise.
  - `location` string — City, State, Country location of the enterprise
  - `zipcode` string — Zip code of enterprise location
  - `contact_person` string, nullable — Person who is the point of contact for the enterprise
  - `contact_number` string, nullable — Contact number of the enterprise
  - `contact_email` string, email — Contact email address of the enterprise
  - `wifi_lte_toggle_flag` boolean — Will only be available if feature is enabled
  - `emm` object, nullable — This field will have details about emm enrollment if the enterprise is emm enrolled
    - `google_enterprise_id` string
  - `created_on` string, date-time — Date and time of when this resource was created
  - `updated_on` string, date-time — Date and time of when this resource was updated

## Other responses

- `401` — Authorization information is missing or invalid.
- `404` — Not Found.
- `500` — Internal server error

---

[API](https://skmtc.net/esper/apis/esper-api-reference.md) · [All operations](https://skmtc.net/esper/apis/esper-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/esper/esper-api-reference/revisions/e1f64cbb488e/schema)