Why do employee IDs differ between connectors?
Updated 2 weeks ago
A Bindbee employee ID identifies an employee within one connector. The same person has a different Bindbee ID in every connector they appear in, and records from one connector only reference IDs from that same connector.
Match an ID to its connector
If a record points to an employee ID you don't recognize, it belongs to a different connector. Look it up with Get Employee by ID, trying the connector token of each of that customer's connectors:
curl --request GET \
--url 'https://api.bindbee.dev/api/hris/v1/employees/<BINDBEE_EMPLOYEE_ID>' \
--header 'Authorization: Bearer <BINDBEE_API_KEY>' \
--header 'X-Connector-Token: <CONNECTOR_TOKEN>'Store the connector alongside each ID, so you always know which connector a record came from.
Match the same person across connectors
Identifier | Use for matching? |
|---|---|
Bindbee | Only within one connector. Store it as your key per connector |
| The source system's own ID. Reliable when both connectors read the same source system, and unique only within a connector |
| Only when it's present, unique and identical in both systems. HR admins can edit it |
Work email | A good match key when both systems hold it |
When no single field is reliable, match on a unique combination of fields, or let your admins map employees between systems in your product.
When IDs change
Relinking keeps the connector and every employee ID.
Moving a connector between environments keeps every ID.
A new connector, including one created after deleting the old one or for a different integration, gives every employee a new ID. Use
remote_idto match old records to new ones.