E-File Magic

Authorization & tokens

Authorize in the browser

Begin browser authorization from a valid pushed authorization request. Confidential application requests can start while signed out or with an expired browser session; EFM redirects to its fixed login/consent origin, then requires an authenticated user in the owning account before context or approval. For MCP, the human follows the emailed link and a single Continue chooses normal signup or sign-in. New accounts reuse the verified mailbox, enter and confirm their password in the first-party signup form, then complete business details and affirmative terms/agency consent. Password confirmation is a browser check, not an OAuth/MCP request field. Fresh completed browser authentication can satisfy identity confirmation; older sessions use the normal verification flow. The client owns its callback completion page.

GET
/oauth/authorize
Authentication
Browser sign-in and consent
Required scopes
See authentication requirements
Idempotency key
Not required

Request fields

9 fields
query.client_idSee descriptionSee description

registered client ID

query.request_uriSee descriptionSee description

Required for pushed authorization; omit only for a supported complete direct public MCP request.

query.response_typeSee descriptionSee description

Direct public MCP flow only: code.

query.redirect_uriSee descriptionSee description

Direct public MCP flow only: exact registered return URI.

query.resourceSee descriptionSee description

Direct public MCP flow only: exact MCP resource URI.

query.scopeSee descriptionSee description

Direct public MCP flow only: requested permitted scopes.

query.stateSee descriptionSee description

Direct public MCP flow only: caller-generated state.

query.code_challengeSee descriptionSee description

Direct public MCP flow only: 43-character base64url SHA-256 challenge.

query.code_challenge_methodSee descriptionSee description

Direct public MCP flow only: S256.

cURL request
curl --request GET '<origin from OAuth metadata>/oauth/authorize' \
  --get \
  --data-urlencode 'client_id=<client_id>' \
  --data-urlencode 'request_uri=<request_uri>'

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.