Process the consent-page form submission

POST

/auth/cli/authorize/consent

curl --request POST \
  --url https://mw.omazy.ai/api/v1/auth/cli/authorize/consent \
  --header 'Authorization: <Authorization>' \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --data action=example \
  --data client_id=example \
  --data code_challenge=example \
  --data code_challenge_method=example \
  --data redirect_uri=example \
  --data state=example \
  --data scope=example \
  --data install_id=example \
  --data install_name=example

• Production

Authorizations

• BearerAuth

Request Body^required

Media typeapplication/x-www-form-urlencoded

object

action

required

‘authorize’ to grant, anything else to deny

string

client_id

required

Must match the /authorize call

string

code_challenge

required

Base64url-no-pad SHA256(verifier)

string

code_challenge_method

required

Must be ‘S256’

string

redirect_uri

required

Must exactly match the redirect_uri sent to /authorize

string

state

required

Opaque value echoed back to the client

string

scope

Space-separated scopes; defaults to the client’s registered set

string

install_id

required

Stable identifier for the machine or integration being authorised

string

install_name

Human-readable label shown in the installs list

string

Example^generated

action=example&client_id=example&code_challenge=example&code_challenge_method=example&redirect_uri=example&state=example&scope=example&install_id=example&install_name=example

Responses

302

302 redirect with ?code=&state= or ?error=access_denied

Media type*/*

string

400

Invalid scope or redirect_uri

Media type*/*

string

401

Unauthorized

Media type*/*

object

code

string

message

string