Archive several SaaS application users
Archive (soft-delete) MULTIPLE SaaS application users in one call — the batch form of archiveSaasApplicationUser, with the same rules per identity. The users are removed from active listings but kept for historical reporting.
Prefer this over calling archiveSaasApplicationUser once per identity: cleaning up the accounts of departed employees across an application is one call here, not one call and one confirmation per account.
To gather the ids of the identities no employee owns across the company, read them from getUnlinkedSaasIdentities in one call instead of reading every application with getSaasById.
Archiving or deleting an identity whose syncedByIntegration is true does not remove the account: the next sync of the integration brings it back. Leave those out and tell the user to remove the accounts in the application itself; Primo drops them at its next sync.
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 IDs to act on, as returned by getSaasById → identities[].id. Each ID may appear at most once and up to 100 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 elements1Response
Number of identities processed successfully.
-9007199254740991 <= x <= 9007199254740991Number of identities that failed.
-9007199254740991 <= x <= 9007199254740991Per-item outcome, in the same order as the input saasApplicationUserIds.