Overview
The authorization flow starts when your agent needs permissions from a user (principal). You create an authorization request, redirect the user to the consent URL, and receive a callback with an authorization code.Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
AgentID | string | Yes | The agent requesting authorization |
PrincipalID | string | Yes | The user granting authorization |
Scopes | []string | Yes | Permissions being requested |
ExpiresIn | string | No | Grant duration (e.g. "24h", "7d") |
RedirectURI | string | No | Where to redirect after consent |
CodeChallenge | string | No | PKCE S256 code challenge |
CodeChallengeMethod | string | No | Must be "S256" when using PKCE |
Response
| Field | Type | Description |
|---|---|---|
AuthRequestID | string | Unique request identifier |
ConsentURL | string | URL to redirect user for consent |
AgentID | string | Agent ID |
PrincipalID | string | Principal (user) ID |
Scopes | []string | Requested scopes |
ExpiresIn | string | Requested duration |
ExpiresAt | string | ISO 8601 expiry timestamp |
Status | string | "pending", "approved", "denied", "expired" |
CreatedAt | string | ISO 8601 creation timestamp |