StudioHomepage
ServicesAuthenticationHTTP APIAuthorization server

Start an authorization with a form

POST
/oauth/authorize

The authorization endpoint with the request in a form body, as OpenID Connect Core §3.1.2.1 allows. The parameters and the behavior are the same as for GET.

Request Body

application/x-www-form-urlencoded
  1. body

The authorization request parameters (RFC 6749 §4.1.1).

response_type*string
client_id*string
redirect_uri*string
Formaturi
state?string
Lengthlength <= 1024
code_challenge*string
code_challenge_method*string
scope?string
resource?string
Formaturi
organization_id?string
login_hint?string
nonce?string
Lengthlength <= 255
prompt?string
max_age?string
Match^[0-9]+$

Response Body

A redirect. It sends the browser to sign in or to the consent page, or back to redirect_uri with the result. A success has code, state and iss. An error has error, error_description, state and iss (RFC 6749 §4.1.2, RFC 9207). First-party applications get status 302. Third-party applications get status 303.

curl -X POST 'https://auth.spiraldb.com/oauth/authorize' \  -H 'Content-Type: application/x-www-form-urlencoded' \  -d 'response_type=code&client_id=string&redirect_uri=http%3A%2F%2Fexample.com&code_challenge=string&code_challenge_method=S256'
Empty