Get Employee

Returns a single employee record as a JSON object (or XML when Accept: application/xml). The id field is always present and is returned as a string; every other field is included only when explicitly named in the fields query parameter. With no fields parameter, the response contains only id — there is no implicit default field set. Field names come from List Fields (list-fields), which also exposes custom-field aliases usable here. By default only currently effective values from historical tables (job title, compensation, employment status, etc.) are returned; pass onlyCurrent=false to include future-dated values. Field-level permissions are applied silently: any requested field the authenticated caller cannot view is omitted from the response with no marker — an absent field may indicate either that it was not requested or that the caller lacks permission to view it. The maximum number of fields per request is 400. Use this for fetching arbitrary fields on a single known employee. For batch lookups or directory-style listings across employees, use List Employees (list-employees) instead. For complex filtering, multi-field predicates, or tabular reports, use Get Data from Dataset (v2) (get-data-from-dataset-v2) instead.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The employee ID. The sentinel value 0 resolves to the employee record bound to the authenticated user, when one exists; if the credentials are not bound to an employee (for example an integration-style account), 0 returns only {"id": "0"} with no other fields. List Employees (list-employees) does not accept this sentinel.

Query Params
string

Comma-separated list of fields to include in the response. Three reference forms are accepted and may be mixed in a single request: standard field names (e.g. firstName, workEmail), numeric field IDs (e.g. 1349), and custom-field aliases (e.g. customStartDate). Discover all three via List Fields (list-fields) — its response includes id, name, and alias for every available field. Example mixing all three: firstName,1349,customStartDate. When omitted, the response includes only id. Bracket-array (fields[]=...) and repeated-key (fields=a&fields=b) forms are not supported on this endpoint — use the comma-separated form. Unknown or unauthorized fields are silently dropped from the response.

boolean
Defaults to true

When true (the default), returns only currently effective values from historical tables (job, compensation, employment status, etc.). When false, future-dated history rows are also returned.

Headers
string
enum

This endpoint can produce either JSON or XML.

Allowed:
string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

400

The fields parameter contained more than 400 entries.

401

Unauthorized.

403

The authenticated user does not have permission to view this employee.

404

No employee was found for the supplied ID.

Language
Credentials
:
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json