---
title: "GET /rest/v1/employees/{id}"
method: GET
path: "/rest/v1/employees/{id}"
---

# GET /rest/v1/employees/{id}

`GET /rest/v1/employees/{id}`

Fetches a single employee.

## Path parameters

- `id` string, required — The `ID` scalar type represents a unique identifier, often used to refetch an object or as key for a cache. The ID type appears in a JSON response as a String; however, it is not intended to be human-readable. When expected as an input type, any string (such as `"4"`) or integer (such as `4`) input value will be accepted as an ID.

## Response `default`

Employee!

- object
  - `data` Employee, required — An employee belonging to a location.
    - `id` string, required — The `ID` scalar type represents a unique identifier, often used to refetch an object or as key for a cache. The ID type appears in a JSON response as a String; however, it is not intended to be human-readable. When expected as an input type, any string (such as `"4"`) or integer (such as `4`) input value will be accepted as an ID.
    - `name` string, required — The `String` scalar type represents textual data, represented as UTF-8 character sequences. The String type is most often used by GraphQL to represent free-form human-readable text.
    - `email` string — A field whose value conforms to the standard internet email address format as specified in HTML Spec: https://html.spec.whatwg.org/multipage/input.html#valid-e-mail-address.
    - `locationIds` String[]
    - `defaultLocationId` string — The `String` scalar type represents textual data, represented as UTF-8 character sequences. The String type is most often used by GraphQL to represent free-form human-readable text.
    - `createdAt` string, date-time, required — A date-time string at UTC, such as 2007-12-03T10:15:30Z, compliant with the `date-time` format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.
    - `updatedAt` string, date-time, required — A date-time string at UTC, such as 2007-12-03T10:15:30Z, compliant with the `date-time` format outlined in section 5.6 of the RFC 3339 profile of the ISO 8601 standard for representation of dates and times using the Gregorian calendar.
  - `meta` object
    - `messages` string[] — Optional scope information.

---

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