Overview
User profiles bind a human (email + display name) to an agent within an organization. They are the foundation for human-in-the-loop flows where an agent acts on behalf of a person. Before an agent can operate on behalf of a profile, the human must enroll by accepting a signed, time-bound enrollment token. Profiles are scoped to an organization. All profile-management endpoints require the caller to have anorganization_id in their authentication context. The enrollment acceptor endpoint is public and does not require authentication because the signed token itself is the credential.
Base URLs
Protected profile endpoints:The profile object
Enrollment flow
- An administrator creates a profile with
POST /beta/user-profiles. - The administrator requests an enrollment URL with
POST /beta/user-profiles/:id/enrollment-url. The URL contains a signed token that expires after 48 hours. - The human visits the URL and submits the token to
POST /beta/enroll. - The profile’s
enrollment_statusbecomesenrolledandconsent_given_atis recorded. - Tokens are single-use; replaying an enrollment URL returns
400 Bad Request.
Endpoints
List profiles
Response
Create a profile
Request body
Response
400 Bad Request.
Get a profile
Response
Update a profile
Request body
At least one field must be provided.Response
Delete a profile
204 No Content.
Create an enrollment URL
Response
400 Bad Request.
Accept enrollment
The enrollment acceptor is public and does not require anAuthorization header. The signed token authenticates the request.
Request body
Response
400 Bad Request.