Skip to content

FousEDGAR Filer Management

Turn EDGAR Filer Management into an API

Read each filer's Account Details, annual confirmation due date, authorized individuals and delegations from EDGAR Filer Management with one API call each. Or have a workflow check every CIK on Monday and email you whose confirmation falls due.

Start building freeBook a demo

Works with your own EDGAR Filer Management account. Fous is an independent product.

What you can build on EDGAR Filer Management

  • Get a filer's account details

    Build this

    Opens the filer under My Accounts and reads Account Details, with the annual confirmation due date shown at the top of the dashboard.

    Takes
    CIK
    Returns
    Company name, CIK, address, annual confirmation due date

  • List individuals and their roles

    Build this

    Reads Manage Individuals for one filer: every account administrator, user and technical administrator, with their role.

    Takes
    CIK
    Returns
    Name, email address, role

  • List delegations

    Build this

    Reads Manage Delegations and User Groups for one filer: its delegated entities and the filers that delegate to it, with each delegation's status.

    Takes
    CIK
    Returns
    Entity name, CIK, direction (delegated entity or delegating filer), status

  • Invite an individual to a role

    Build this

    Selects Add Individual under Manage Individuals and sends a role invitation to the email address the person uses for Login.gov.

    Takes
    CIK, Login.gov email address, role
    Returns
    Email address, role, invitation status

Automate EDGAR Filer Management with a workflow

A workflow runs your methods as one process, with nobody at the screen. A schedule or a call from your own system starts it, the steps run in order, and the result arrives in your inbox or in the systems you already use.

  • Annual confirmations falling due, every CIK

    Build this
    Starts
    Every Monday at 8:00 Eastern Time
    Step 1
    For each CIK you name, get the filer's account details.
    Step 2
    Keep the filers whose annual confirmation due date is in the next 45 days.
    Step 3
    Email you the list with company name, CIK and due date, soonest first.

  • Changes to authorized individuals, every filer

    Build this
    Starts
    Every weekday at 9:00 Eastern Time
    Step 1
    For each CIK, list the individuals and their roles under Manage Individuals.
    Step 2
    Keep the people added, removed or given another role since the last run.
    Step 3
    Email you the changes, one section per filer.

  • New delegation requests, posted to your system

    Build this
    Starts
    Every weekday at 10:00 Eastern Time
    Step 1
    For each CIK, list the delegations under Manage Delegations and User Groups.
    Step 2
    Keep the Pending or Requested delegations that were not there on the last run.
    Step 3
    Post each one, with entity name, CIK and status, to your webhook.

You can run a workflow by hand on every plan, Free included. Schedules and webhook triggers come with the paid plans, from $29 a month.

Once built, one call from your code

Once you have built a method, it is one POST to /v1/runs from your backend, or a tool an AI agent calls over MCP. This is what “Get a filer's account details” would look like.

Example request
curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "filermanagement.edgarfiling.sec.gov/get_filer_account_details",
    "input": {
      "cik": "0001234567"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "company_name": "Acme Holdings, Inc.",
    "cik": "0001234567",
    "address": {
      "street": "100 Market Street, Suite 400",
      "city": "Wilmington",
      "state": "DE",
      "zip": "19801"
    },
    "annual_confirmation_due_date": "2026-12-31"
  }
}

An example with invented data, not a ready-made endpoint. The method exists in your organization once you build it, and its name, inputs and fields follow your request.

EDGAR Filer Management’s own options

The SEC offers optional EDGAR APIs: a submission API, submission status and operational status APIs, and 11 Filer Management APIs for individuals, roles, delegations, account information and CCCs. To connect, a filer needs at least two technical administrators and a filer API token, and most calls also need a person's user API token. The SEC publishes an API Development Toolkit with specifications and sample code.

OptionWhat it coversWhat it takes
Submission, submission status and operational status APIsSubmit a filing and get an accession number, check a submission's status (accepted, disseminated, suspended) and whether EDGAR is accepting submissions.Two technical administrators and a filer API token valid one year. Submitting also needs a user API token, valid 30 days.
Filer Management APIsAdd, remove and view individuals, change roles, send, request and view delegations, view account information, generate or set a CCC, verify credentials.A filer API token and a user API token. Some calls need that user to be an account administrator for the CIK.
EDGAR Filer Management by handMy Accounts, Account Details, Manage Individuals, Manage Delegations and User Groups, Manage Filer API Token and Annual Confirmation.Login.gov credentials with multifactor authentication and a role for the filer. Open 6:00 to 22:00 Eastern Time on weekdays.

Read on November 12, 2026: Overview of EDGAR APIs (PDF), Create and manage filer and user API tokens, EDGAR Next: improving filer access and account management.

Signing in to EDGAR Filer Management

EDGAR Filer Management signs each individual in with their own Login.gov credentials and multifactor authentication. The second step is the one each person set up at Login.gov: an authentication application, a security key, phone or SMS, backup codes, PIV/CAC, or face or touch on their device. With Fous you sign in through that sign-in with your own account, and the login is sealed with AES-256.

Worth knowing

Open on weekdays, 6:00 to 22:00 Eastern
EDGAR Filer Management can be reached from 6:00 a.m. to 10:00 p.m. Eastern Time, Monday through Friday, except federal holidays. Schedule workflows inside those hours.
A missed confirmation deactivates the account
The deadline is the quarter-end the filer chose, with reminders from six weeks before. After a missed deadline comes a 3-month grace period, then the account is deactivated and the filer must reapply on Form ID.
Role counts and combinations
A filer needs at least two account administrators (one for an individual or single-member company), at most 20. It can have up to 500 users, and one person cannot be both account administrator and user for the same filer.
Invitations expire after 14 days
An invited individual has 14 days to accept. The invitation must go to the email address that person used for Login.gov, or they cannot accept it.

More in Government: US federal

Other industries: eVA, NY Business Online Services, CalSavers, アスクル, Beeline, 340B ESP.

Frequently asked questions

Yes, optional ones. The SEC offers submission, submission status and operational status APIs and 11 Filer Management APIs. You need at least two technical administrators and a filer API token, valid one year, and most calls also take a user API token, valid 30 days, generated on the dashboard.

Your filer probably has fewer than two technical administrators. Each filer must have at least two to connect to the APIs, and the dashboard blocks token creation until it does. Only a technical administrator can create a filer API token, under My Accounts and Manage Filer API Token.

30 days from creation. Each individual can have one active user API token, and creating a new one inactivates the old one. The SEC suggests that your users' tokens expire on different dates, so one expiry does not hold up a filing.

On the quarter-end your filer chose: March 31, June 30, September 30 or December 31. The due date is shown at the top of the filer's dashboard, and any one account administrator can complete it with Annual Confirmation after reviewing individuals, delegations and tokens.

No. Fous is an independent product. You use it with your own EDGAR Filer Management access, and a method reads and does only what your account can.

Put EDGAR Filer Management behind an API call

Describe one job in Studio and see the method it builds, with 100 credits a month and no credit card, or book a demo and bring the sites your team signs in to.

Start building freeBook a demo

Read nextCODIRS e-ServicesIRS Tax Pro AccounteVAHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of EDGAR Filer Management (US Securities and Exchange Commission). The name is used only to say which system this page is about. Something here wrong or out of date? Write to legal@fous.com.