Authorization & tokens
Push an authorization request
Create a one-time pushed authorization request.
/oauth/par- Authentication
- OAuth protocol client authentication
- Required scopes
- See authentication requirements
- Idempotency key
- Not required
How to use this endpoint
Confidential Filing API clients must use this step before browser authorization. Public MCP clients may use PAR or their supported direct browser flow. Send the exact intended resource, registered redirect URI, state and S256 PKCE challenge; authenticate with the client’s registered method.
curl --request POST '<origin from OAuth metadata>/oauth/par' \
--user '<client_id>:<client_secret>' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'response_type=code' \
--data-urlencode 'client_id=<client_id>' \
--data-urlencode 'redirect_uri=<registered redirect URI>' \
--data-urlencode 'resource=<resource from OAuth metadata>' \
--data-urlencode 'scope=<approved scopes>' \
--data-urlencode 'state=<random state>' \
--data-urlencode 'code_challenge=<S256 challenge>' \
--data-urlencode 'code_challenge_method=S256'Use the exact endpoint URL from your environment's metadata. Confidential client examples use client_secret_basic; public MCP clients use client_id without a secret.
Request fields
10 fieldsresponse_typeSee descriptionSee description
literal code
client_idSee descriptionSee description
Registered client ID; required in the form for public clients and private_key_jwt, otherwise it may be supplied by HTTP Basic.
redirect_uriSee descriptionSee description
Exact registered redirect URI. Confidential clients require HTTPS; registered public clients may use an admitted literal-loopback HTTP URI.
resourceSee descriptionSee description
Required exact Filing API or MCP resource URI returned by discovery, as permitted for the registered client.
scopeSee descriptionSee description
space-delimited approved scope subset
stateSee descriptionSee description
required opaque client value, max 1024 characters
code_challengeSee descriptionSee description
base64url PKCE challenge, 43..128 characters
code_challenge_methodSee descriptionSee description
literal S256
client_assertion_typeSee descriptionSee description
urn:ietf:params:oauth:client-assertion-type:jwt-bearer when private_key_jwt
client_assertionSee descriptionSee description
short-lived signed assertion with one-time jti when private_key_jwt
Headers (2)
AuthorizationConditional / optional- Use HTTP Basic for client_secret_basic. For private_key_jwt, omit this header and send the registered assertion fields. Public MCP clients use client_id with no Basic header, client secret or assertion. The example builder defaults to a confidential client; remove --user when adapting it for a public client.
Content-TypeRequired- application/x-www-form-urlencoded
curl --request POST '<origin from OAuth metadata>/oauth/par' \
--user '<client_id>:<client_secret>' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'response_type=code' \
--data-urlencode 'client_id=<client_id>' \
--data-urlencode 'redirect_uri=<registered redirect URI>' \
--data-urlencode 'resource=<resource from OAuth metadata>' \
--data-urlencode 'scope=<approved scopes>' \
--data-urlencode 'state=<random state>' \
--data-urlencode 'code_challenge=<S256 challenge>' \
--data-urlencode 'code_challenge_method=S256'Use the exact endpoint URL from your environment's metadata. Confidential client examples use client_secret_basic; public MCP clients use client_id without a secret.
Successful outcomes: created.
{
"request_uri": "urn:ietf:params:oauth:request_uri:<opaque>",
"expires_in": 90
}PAR accepted
Errors to handle
Use the returned status and code to decide what to correct or retry.
- 400
invalid_request - 401
invalid_client - 503
temporarily_unavailable