Link SaaS identities to the employees who own them
Link existing SaaS identities (accounts already on an application) to the employees who own them, up to 100 identity → employee pairs per call. Primo links an account to an employee by itself only when the account email equals the employee email; this links the accounts it could not match, such as an alias (firstname.lastname@) of an employee whose HR email is flastname@.
The account keeps its own email, becomes an employee account and leaves the “To link” list. An identity already linked to another employee moves to the one given. A later integration sync keeps the link. Nothing changes in the application itself.
Read the identities to link from getUnlinkedSaasIdentities (its id) and the employees from getEmployees (its id). To record an account Primo does not know yet, use createSaasIdentity instead; to have an admin create a new account, use provisionSaasIdentity.
Writes are independent and best-effort: the call returns 200 with a results manifest reporting ok / error per item — always inspect results rather than relying on the HTTP status to detect partial failures.
Authorizations
Use your Primo API key in the Authorization header as Bearer <API_KEY>.
Body
The identity → employee pairs to link. Each identity may appear at most once and up to 100 pairs per call. Writes are best-effort: inspect the per-item results to learn which succeeded — the HTTP status is 200 even when some items fail.
1 - 100 elementsResponse
Number of identities linked successfully.
-9007199254740991 <= x <= 9007199254740991Number of identities that failed.
-9007199254740991 <= x <= 9007199254740991Per-item outcome, in the same order as the input links.