Approve an OAuth authorization request.
POST /oauth/authorize
Approves only the permissions displayed and selected by the user. Sensitive custom permissions require a separate confirmation.
Access
Section titled “Access”Use a credential with the authentication scheme documented in the API contract.
Provider access, workspace membership, and agent grants are enforced separately. A token does not expand access to a repository or resource. Set up developer access.
Request body
Section titled “Request body”Optional. Supported content types: application/x-www-form-urlencoded.
Call the endpoint
Section titled “Call the endpoint”Replace path placeholders and your credential. For body operations, create request.json using the required fields above; this command does not invent resource identifiers or consent.
curl --request POST \ 'https://commentary.dev/oauth/authorize' \ --header 'Authorization: Bearer <your-token>' \ --header 'Content-Type: application/x-www-form-urlencoded' \ --data-binary @request.jsonResponses
Section titled “Responses”| Status | Meaning | Payload |
|---|---|---|
302 |
Redirect to the client with an authorization code or error. | See response headers or body contract |
Recover from errors
Section titled “Recover from errors”Use the returned status and error body. Correct invalid fields before retrying; reconnect or narrow the target for authentication and permission errors. For conditional writes, reload the latest version before preparing a new request. Respect rate-limit headers and retry only when the operation’s idempotency contract permits it.
Contract and related guidance
Section titled “Contract and related guidance”Operation ID: approveOAuthAuthorizeRequest. Download the OpenAPI contract for complete constraints and code generation. Browse endpoints.