Test identities and testers
Synthetic people a sandbox team signs in as, and the real people invited to try a sandbox application.
14 routes
Both are sandbox-only. A test identity is invented; a tester is a real UnifyID account the team invited by its UnifyID.
The guide for this family is Test identities.
GET /v1/developer/applications/{applicationId}/test-identities
GET /v1/developer/applications/{applicationId}/test-identitiesAuthentication- Developer console session
POST /v1/developer/applications/{applicationId}/test-identities
POST /v1/developer/applications/{applicationId}/test-identitiesAuthentication- Developer console session
DELETE /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}
DELETE /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}Authentication- Developer console session
GET /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}
GET /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}Authentication- Developer console session
PATCH /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}
PATCH /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}Authentication- Developer console session
The picture a developer gives a synthetic person.
The body is TestIdentityConfiguration; its fields are checked by the service.
DELETE /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}/avatar
DELETE /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}/avatarAuthentication- Developer console session
GET /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}/avatar
GET /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}/avatarAuthentication- Developer console session
POST /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}/avatar
POST /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}/avatarAuthentication- Developer console session
The picture a developer gives a synthetic person.
POST /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}/reset
POST /v1/developer/applications/{applicationId}/test-identities/{testIdentityId}/resetAuthentication- Developer console session
The picture a developer gives a synthetic person.
GET /v1/developer/applications/{applicationId}/testers
GET /v1/developer/applications/{applicationId}/testersAuthentication- Developer console session
The invitations and their states, with how much of the cap is left.
POST /v1/developer/applications/{applicationId}/testers
POST /v1/developer/applications/{applicationId}/testersAuthentication- Developer console session
The invitations and their states, with how much of the cap is left.
DELETE /v1/developer/applications/{applicationId}/testers/{testerId}
DELETE /v1/developer/applications/{applicationId}/testers/{testerId}Authentication- Developer console session
The invitations and their states, with how much of the cap is left.
POST /v1/developer/applications/{applicationId}/testers/self
POST /v1/developer/applications/{applicationId}/testers/selfAuthentication- Developer console session
POST /v1/developer/applications/{applicationId}/testers/self/challenge
POST /v1/developer/applications/{applicationId}/testers/self/challengeAuthentication- Developer console session
What this does not do
- Responses are not listed. The API declares no response types, so this page describes what to send and who may send it. Recorded response shapes are on the guides.
- This page is generated. It was read from the API at commit
234dba22. Editing it by hand changes nothing; the next sync overwrites it.
Verified against API commit 234dba22 on 2026-10-18. The routes, scopes, checklist, events and limits on these pages are read from that export, not typed.