Account & settings
Connect and manage API access
Request approval for your application, then manage its OAuth access, credentials and webhooks for this account.

In this guide
Connecting accounting software?
QuickBooks, Xero and other accounting import connections are managed in Recipients → Imports → Integrations.
Before you start
Account administrator access
Authority changes require security verification.
The permissions you need
Identify the application, filers and filing actions.
A secure place for secrets
New credentials and signing secrets are shown once.
View all setup requirements
- You must be an account administrator and complete security verification for every authority-changing action.
- Know which application, filers, and filing actions the integration actually needs; grant the smallest practical set.
- Prepare a secure password manager or secret vault before creating or rotating credentials and webhook secrets.
- For webhooks, prepare a public HTTPS endpoint that can answer the verification request and return a 2xx response to accepted deliveries.
- Keep accounting-provider import connections under Recipients > Imports > Integrations; they are separate from API Access.
- State E-File is not offered in service permissions. State Reporting File remains available. Existing connections show the services currently available; disabling or narrowing a connection remains possible.
- Your approved account limits apply across its API applications. Individual application limits may be lower; approval does not enable order submission.
Choose an API access task
Start with application approval, or manage an existing connection.
Request and set up OAuth
Use this when your application needs access to your E-File Magic account.
Describe your application
Open Settings → API Access and choose Request API access. Requests can be submitted while OAuth service is unavailable.
Enter the application name and purpose. Choose Background integration for server-to-server client credentials, or User-authorized integration for authorization code with PKCE and an exact HTTPS callback.
- Background integration
- Server-to-server client credentials.
- User-authorized integration
- Authorization code with PKCE and an exact HTTPS callback.
Submit the request and track approval
Choose the permissions needed, review the summary and submit after security verification.
Track the status under Applications. If changes are requested, open the feedback, update your request and submit it again.
Set up OAuth after approval
After approval and service enablement, choose Set up OAuth. Copy the client ID and one-time secret into your server’s secret vault.
Copy the client ID and one-time secret immediately into your server’s secret vault.
Narrow access and set limits
Review Credentials & access: narrow the approved scopes, choose selected filers if needed and set conservative limits. Initial setup allows approved scopes across this account’s filers and keeps order submission off.
Approval does not enable order submission. Configure order permissions separately when needed.
Follow the integration guide for tokens
Follow the Integration guide to obtain short-lived OAuth access tokens. Client credentials use the service client ID; user authorization uses the application client ID.
The approved application has OAuth access limited to its own customer account and approved permissions.
Configure a signed webhook
Use this to receive filing lifecycle events at your server.
Choose the destination and events
Enter a public HTTPS endpoint, optionally choose one connection, and select event subscriptions.
Add the endpoint and save its secret
Choose Add endpoint, complete security verification, and immediately store the one-time signing secret.
Verify endpoint ownership
Choose Verify after your endpoint can answer the ownership challenge.
Monitor delivery attempts
Monitor Webhook attempts. Only 2xx responses count as success.
Replay a corrected terminal delivery
For a terminal delivery, fix the destination first and then choose Replay to create a new audited attempt.
Your verified endpoint receives signed events for the events you enabled. Failed deliveries are retried when the error allows it.
Stop integration access
Use this when a credential or integration may be compromised.
Select the affected connection
Select the affected connection.
Revoke the affected access
Revoke the individual credential if only one credential is affected, or choose Revoke connection to stop the whole integration.
Complete security verification
Complete security verification.
Review delegated authorizations
Review delegated authorizations and revoke any that should no longer remain active.
Review webhook security
Rotate or disable associated webhook endpoints when their signing secret or destination may also be affected.
Future token use fails the live authorization checks for the revoked authority.
Page details and controls
Applications
Lists only this account’s applications and requests, including pending, approved, changes requested, suspended and disabled states. View request shows permissions and applicant feedback. Load more retrieves the next page.
Request API access
Describe the application, choose background or user-authorized OAuth, select named permission checkboxes, then review and submit after security verification. Only user authorization requires a callback URL. Back preserves the draft; cancelling a changed draft asks before discarding it.
Credentials & access
After approval, Set up OAuth creates the connection and appropriate credentials. Copy the client ID and one-time secret to your server vault. Manage filer boundaries, permissions, quotas, service credentials and delegated user grants here.
Order permissions
Order submission starts off. Enable it separately with allowed services, funding and per-order/daily caps; the connection must also hold the approved orders.submit scope.
Webhooks
Configure and verify signed lifecycle delivery for this account, manage secrets and replay terminal deliveries.
Integration guide
Explains approval, account boundaries, background client-credentials tokens, PAR/S256-PKCE user authorization, refresh tokens, exact issuer endpoints and safe credential storage.
Manage an approved connection
Use Edit permissions and Save permissions to change allowed operations; Edit boundary sets allowed filer IDs. Edit limits and Save limits adjust traffic limits. Activate connection and Suspend connection change its availability. Save order policy applies allowed services, funding and order limits. Rotate secret replaces a credential; Revoke authorization removes a delegated grant. For a webhook, review its Endpoint URL, and use Replay delivery only after resolving a terminal delivery problem.
Actions and controls
- Refresh the page to load the latest availability, connection, credential, authorization, order-policy, and webhook state.
- Submit an account-owned application through the Application details, Permissions and Review walkthrough; read EFM feedback and resubmit when changes are requested.
- After approval, choose Set up OAuth to create credentials limited to this account. Choose background client credentials or user-authorized OAuth with an exact callback URL.
- Select a connection and restrict its status, allowed filers, permissions, traffic limits, security posture, funding source (deposit, approved terms, or an active saved payment method), and order caps.
- Create, rotate, or revoke a service credential. A newly issued secret is shown once and must be copied immediately.
- Review and revoke delegated user authorizations.
- Enable billable API order submission only after selecting allowed services and nonzero limits.
- Add, verify, rotate, or disable signed webhook endpoints, and replay terminal deliveries as new audited attempts.
- Review an agent connection created by an approved human authorization and revoke it when access is no longer wanted.
- Choose View saved payment method status when an integration needs to know whether a payment method and default are configured. It does not grant payment or access to card or bank numbers.
If you get stuck
Set up OAuth is disabled.
The application must be approved and OAuth service must be available for this account. Pending requests can still be viewed and requests for changes can be resubmitted. Refresh to load current status.
I lost a one-time secret.
It cannot be displayed again. Rotate the credential or webhook secret, copy the replacement immediately, and update your integration before the overlap window ends.
A webhook will not verify or has terminal deliveries.
Confirm the URL is public HTTPS, DNS does not resolve to a private destination, the verification response is correct, and delivery responses are 2xx. After correcting the endpoint, replay the terminal delivery.
A webhook delivery remains pending during a burst.
Check the delivery's current status before replaying it. Allow an automatic retry to finish first; replay only after you have corrected the problem at your endpoint.
API order submission is denied.
Confirm API order authorization is enabled, the connection has orders.submit, the filer and services are allowed, the funding source is configured, and the order stays within every per-order and daily limit.
Can my approved application access another customer account?
No. This application and its OAuth credentials are bound to the account that submitted the request. There is no shared application catalog.