E-File Magic

Authorization & tokens

Push an authorization request

Create a one-time pushed authorization request.

POST
/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
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.