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

Errors to handle

Use the returned status and code to decide what to correct or retry.

400invalid_request
401unauthorized
503temporarily_unavailable