Get Employee By Id

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Whether to include the original data Bindbee fetched from the third-party to produce these models.

Which relations should be returned in expanded form. Multiple relation names should be comma separated without spaces.

The third-party API ID of the matching object.

This is the datetime that this object was last updated by Bindbee

The employee's number that appears in the third-party integration's UI.

The ID of the employee's company.

The employee's first name.

The employee's last name.

The employee's preferred first name.

The employee's full name, to use for display purposes. If a preferred first name is available, the full name will include the preferred first name.

The employee's username that appears in the remote UI.

The IDs of the groups that the employee belongs to.

The employee's department

The employee's division

The employee's work email.

The employee's personal email.

The employee's mobile phone number.

The employee's home phone number.

The employee's home address.

The employee's work address.

The employee's pay group

The employee's social security number.

The employee's gender.

The employee's ethnicity.

The employee's filing status as related to marital status

The employee's date of birth.

The date that the employee started working. If an employee was rehired, the most recent start date will be returned.

When the third party's employee was created.

The employment status of the employee. Possible values include: ACTIVE, PENDING, INACTIVE, or - in cases where there is no clear mapping - the original value passed through.

The employee's termination date.

The URL of the employee's avatar image.

The custom fields related to employee

This is the Raw data

The employee's middle name.

The employee's current designation/title

The employee's country code

The employee ID of the employee's manager.