Get an employee number
/api/v1/employees
{basePath}/employees?OrgShortName=tfoinc&LocRef= fdmnh144&EmployeeId=5
API returns a specific employee.
Request
- application/json
-
EmployeeId(required): integer(int64)
Employee ID number.
-
locRef(required): string
The location identifier.
-
orgShortName(required): string
The organization identifier.
-
If-Modified-Since: string
Standard http caching header (http caching link).
-
If-None-Match: string
Standard http caching header (http caching link).
Response
- application/json
200 Response
-
ETag: string
The current entity-tag for the selected representation. See RFC 7232 Section 2.3 (https://tools.ietf.org/html/rfc7232#section-2.3).
-
Last-Modified: string
A timestamp indicating the date and time at which the origin server believes the selected representation was last modified. See RFC 7232 Section 2.2 (https://tools.ietf.org/html/rfc7232#section-2.2).
object-
employeeNumber(required):
integer(int32)
Minimum Value:
1Employee number.Example:42
304 Response
400 Response
object-
details:
string
A human-readable explanation specific to this occurrence of the problem.Example:
The OrgShortName value is required. -
instance:
string
A URI reference that identifies the specific occurrence of the problem. It may or may not yield further information if dereferenced.Example:
required_value_missing -
title:
string
A short, human-readable summary of the problem type.Example:
Required value not specified. -
type:
string
A URI reference that identifies the problem type. When this member is not present, its value is assumed to be "about:blank".Example:
error:validation
{
"type":"error:validation",
"title":"Required value not specified.",
"details":"The OrgShortName value is required.",
"instance":"required_value_missing"
}401 Response
-
WWW-Authenticate: string
Bearer authentication challenge. When token validation fails, the header may include error and error_description parameters.
The following conditions and HTTP response examples are illustrative and not exhaustive. Error descriptions may vary.
No token provided: No access token is provided, or the Authorization request header is missing. The response header is WWW-Authenticate: Bearer, without error or error_description parameters.
Example:
HTTP/1.1 401 Unauthorized WWW-Authenticate: BearerExpired token: The access token has expired. The timestamp in this example is illustrative.
Example:
HTTP/1.1 401 Unauthorized WWW-Authenticate: Bearer error="invalid_token", error_description="The token expired at '05/19/2026 17:16:29'"Signing key not found: The token cannot be validated because its signing key was not found. For example, the token's key ID (kid) does not match a key in the JSON Web Key Set (JWKS) used for validation.
Example:
HTTP/1.1 401 Unauthorized WWW-Authenticate: Bearer error="invalid_token", error_description="The signature key was not found"Invalid signature: The token signature is invalid. For example, the token may have been modified.
Example:
HTTP/1.1 401 Unauthorized WWW-Authenticate: Bearer error="invalid_token", error_description="The signature is invalid"For the missing-token, signing-key-not-found, and invalid-signature examples above, the response body is empty. The authentication error details are provided in the WWW-Authenticate response header.
The response may include an additional WWW-Authenticate header containing a bare Bearer challenge alongside the challenge shown in these examples.
403 Response
404 Response
Examples
Example Request Body
Not applicable for this endpoint.
Example Response Body
The following example shows the contents of the response body in JSON format:
{
"employeeNumber": 42
}