Skip to main content
Most v1 resources carry a UUID string in their id field, such as 1a2b3c4d-5e6f-7890-abcd-ef1234567890. Store it as a string and send it unchanged. The table below lists the few identifiers that aren’t UUIDs. Path parameters are named per resource: app_uuid, entitlement_uuid, account_uuid, workflow_id, user_id, group_id, task_id, access_policy_id, and plain id on access requests. Whatever the suffix, each one takes that resource’s id, so workflow_id takes a UUID, as app_uuid does. Fields that point at another object follow the same rule. app_id on an entitlement or an access request is the app’s id, and entitlement_ids on Create Access Request takes entitlement ids.

​
Values that aren’t UUIDs

You can’t fetch a single activity log entry or identity event by ID. An activity log entry carries event_hash instead of an id, and no endpoint takes an identity event’s id.

​
Malformed IDs

If you send a malformed value in a body field that must be a UUID, the call returns 400. code is validation_error, and errors names the field. A well-formed ID in the path that matches nothing in your organization returns 404.