Overview
Theclient.Employees client provides access to legacy employee operations:
Migration Guide
If you’re currently using the Employees API, you should migrate to the Team Members API:| Employees API | Team Members API |
|---|---|
client.Employees.List() | client.TeamMembers.Search() |
client.Employees.Get() | client.TeamMembers.Get() |
Employee object | TeamMember object |
Methods (Deprecated)
List
Lists all employees for a location.Filter employees by location ID.
Specifies the EmployeeStatus to filter the employee by. Possible values:
ACTIVE, INACTIVE.The number of employees to be returned on each page.
The token required to retrieve the specified page of results.
The list of employees.
The token to be used to retrieve the next page of results.
Get
Retrieves an employee by ID.UUID for the employee that was requested.
The requested employee.
Employee Object (Deprecated)
UUID for this object.
The employee’s first name.
The employee’s last name.
The employee’s email address.
The employee’s phone number in E.164 format (e.g., “+12125554250”).
A list of location IDs where this employee has access to.
Specifies the status of the employee. Possible values:
ACTIVE, INACTIVE.Whether this employee is the owner of the merchant. Each merchant has one owner employee with full authority over the account.
A read-only timestamp in RFC 3339 format.
A read-only timestamp in RFC 3339 format.
Why Migrate to Team Members?
The Team Members API provides several advantages over the deprecated Employees API:- More comprehensive data model: Includes wage settings, job assignments, and location assignments
- Better search capabilities: Search and filter team members by multiple criteria
- Bulk operations: Create and update multiple team members at once
- Improved status tracking: Better handling of active/inactive states
- Integration with other APIs: Works seamlessly with the Labor API for shift management
