Employees

Entity›Relationship›Relationship.Person.Contact.Employee

An Employee relationship links your own Organisation (parent) to a Person (child), defining that person as an employee of your organisation. Employees are commonly referenced as sales representatives, account managers, and assignees across activities and other relationships.

Use the Relationship_Person_Contact_Employee endpoint to manage your employees. Employees inherit all fields from Relationship and add employee-specific fields.

Not to be confused with "Persons"

An Employee (Relationship_Person_Contact_Employee) is a Relationship — it defines the role a person plays as a member of your organisation. A Person (Relation_Person) is the entity itself — the individual record. The same Person can be both an Employee of your organisation and a Contact at another company.

Creating employees via the API

It is recommended to create employees through the Tribe CRM UI rather than the API. When created through the UI, additional setup (account, permissions, team assignment) is handled automatically. If you need to reference an employee in API calls, use the list or search endpoints below to find their ID.

Endpoints

List Employees

Retrieve a paginated list of employees.

GET/v1/odata/Relationship_Person_Contact_Employee

Single Employee

Retrieve a single employee by its ID.

GET/v1/odata/Relationship_Person_Contact_Employee({id})

With expanded relations:

GET/v1/odata/Relationship_Person_Contact_Employee({id})?$expand=Relation,Person

Get Current Employee

Retrieve the employee record of the currently authenticated user.

GET/v1/odata/GetCurrentEmployee()?$expand=Person

Create Employee

Create an employee by linking an existing or new Person to your organisation.

POST/v1/odata/Relationship_Person_Contact_Employee

• Relation.ID — Your own organisation (parent)
• Person — The new Person fields (created automatically). LastName is mandatory.

Update Employee

Update an existing employee relationship. Provide only the fields to update.

PUT/v1/odata/Relationship_Person_Contact_Employee({id})

Delete Employee

Employees cannot be deleted via the API. Use the Tribe CRM UI to manage employee removal.

Fields

Standard Fields (all entities)

Field	Type	Description
ID	Guid	Primary key (UUID)
_Type	String	Entity type discriminator (Relationship.Person.Contact.Employee)
_Name	String	Computed display name
SortIndex	Double	Sorting order
CreationDate	DateTimeOffset	Date the record was created
LastMutationDate	DateTimeOffset	Date of the last modification
IsActive	Boolean	Whether the record is active
IsClosed	Boolean	Whether the record is closed

Employee Fields

Field	Type	Description
Name	String	Employee display name

Relationships

Relationship	Target Entity	Cardinality	Description
Relation	Relation	N:1	Parent organisation (your company)
Person	Relation.Person	N:1	The employee as a person

Expanding Relationships

GET/v1/odata/Relationship_Person_Contact_Employee({id})?$expand=Person

GET/v1/odata/Relationship_Person_Contact_Employee?$filter=contains(Name,'Halpert')&$select=Name&$expand=Relation($select=ID),Person($select=ID)

Navigating Relationships

GET/v1/odata/Relationship_Person_Contact_Employee({id})/Relation

Filtering Examples

GET/v1/odata/Relationship_Person_Contact_Employee?$filter=contains(Name, '{Name}')&$top={top}

GET/v1/odata/Relationship_Person_Contact_Employee?$filter=contains(Name, '{Name}')&$top={top}

GET/v1/odata/Relationship_Person_Contact_Employee?$filter=CreationDate gt {CreationDate}&$top={top}

GET/v1/odata/Relationship_Person_Contact_Employee?$filter=IsActive eq {IsActive}&$top={top}

Common Use Cases

Employees are frequently referenced when creating or updating other entities:

• Sales Opportunities — as SalesRepresentative
• Customers — as AccountManager
• Activities — as assigned employee

POST /v1/odata/Activity_SalesOpportunity
{
  "Subject": "New deal",
  "SalesRepresentative": {
    "ID": "employee-relationship-id-here"
  }
}