Skip to content

FousEPA Central Data Exchange

Pull your EPA CDX submission records into your systems

Build methods that read your CDX Submission History, Inbox messages and program service roles, one API call each. Then have a workflow read the Inbox each weekday at 7:00 and email you new submission confirmations.

Start building freeBook a demo

Works with your own EPA Central Data Exchange account. Fous is an independent product.

What you can build on CDX

  • Get submission history

    Build this

    Reads the Submission History tab in MyCDX and opens each Submission ID for its Submission Details.

    Takes
    Submitted since, program service (optional)
    Returns
    Submission ID, program service, submitted date, source, status, details

  • Read new CDX Inbox messages

    Build this

    Reads the Inbox tab in MyCDX, where RMP submission confirmations and Electronic Signature Agreement copies arrive, and opens each message.

    Takes
    Received since (optional)
    Returns
    From, subject, received date, message text, attachment names

  • Check program service role statuses

    Build this

    Reads the services table on the MyCDX tab: each program service, role and its Status, plus the system messages beside it.

    Takes
    Nothing
    Returns
    Program service, role, status, system messages

  • Request a new role in a program service

    Build this

    Opens Manage Your Program Services, selects List Roles for a program service and sends Request a New Role.

    Takes
    Program service, role, additional information the role asks for
    Returns
    Program service, role, status after the request

Automate CDX 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.

  • New CDX Inbox messages, each weekday morning

    Build this
    Starts
    Every weekday at 7:00
    Step 1
    Read the CDX Inbox messages received since yesterday.
    Step 2
    Keep the messages that were not there on the last run.
    Step 3
    Email you each message's sender, subject, received date and text.

  • Weekly submission history for your compliance records

    Build this
    Starts
    Every Monday at 8:00
    Step 1
    Get the Submission History transactions from the last 7 days.
    Step 2
    Group them by program service with an AI step.
    Step 3
    Post each submission ID, program service, date and status to your compliance system's webhook.

  • Role approvals that changed

    Build this
    Starts
    Every day at 9:00
    Step 1
    Check the status of each program service role on the MyCDX tab.
    Step 2
    Keep the roles whose status changed since the last run.
    Step 3
    Email you the program service, role and new status.

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 submission history” 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": "cdx.epa.gov/get_submission_history",
    "input": {
      "submitted_since": "2026-11-01",
      "program_service": "CEDRI"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "submissions": [
      {
        "submission_id": "_7f3c2a91-0d4e-4b8a-9c61-2e5f80a1b347",
        "program_service": "CEDRI: Compliance and Emissions Data Reporting Interface",
        "submitted": "2026-11-09T14:22:05-05:00",
        "source": "CROMERR",
        "status": "Completed",
        "details": "Acme Coatings, Plant 2: semiannual compliance report"
      }
    ],
    "count": 1
  }
}

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.

CDX’s own options

CDX is EPA's site for electronic reporting: you register for a program service, take a role and submit and sign in its web screens. EPA's Exchange Network moves data between EPA, states, tribes and territories over nodes, and Submission History lists node transactions too. EPA's CDX pages describe no general API for the companies that sign in.

OptionWhat it coversWhat it takes
Exchange Network nodesEnvironmental data exchanged between EPA, states, tribes and territories; node transactions appear in Submission History.A node run by an Exchange Network partner. EPA's grant program funds eligible states, federally recognized tribes and territories.
CDX by handProgram services and roles on the MyCDX tab, the Inbox, My Profile and Submission History, with each program's own reporting screens.A CDX account for each person, linked to Login.gov. In CEDRI, Certifiers also need identity proofing and an Electronic Signature Agreement.

Read on November 12, 2026: CDX Frequently Asked Questions, CDX CSPP Registration User Guide, Environmental Information Exchange Network.

Signing in to CDX

CDX signs you in with your CDX User ID and password together with the Login.gov account linked to it, and EPA asks you to set up two or more authentication methods on Login.gov. Each account belongs to one person. With Fous you sign in through CDX's own sign-in with your own account: the login is sealed with AES-256, and code and AI agents never see it.

Worth knowing

One account per person
A CDX account belongs to one person and cannot be shared or transferred. If its linked Login.gov account is lost or deleted, CDX will not relink it and the CDX account becomes defunct.
Preparers prepare, Certifiers sign
In CEDRI a Preparer, who may be a contractor, cannot sign or submit. A Certifier needs identity proofing and an Electronic Signature Agreement, which by paper can take up to 2 weeks.
20 minutes of inactivity ends a session
eDisclosure, RMP and SWIPR sign you out after 20 minutes of inactivity, and SWIPR users cannot extend it. A challenge question error while submitting needs a 20-5-1 reset.
Older transactions sit in an archive
Submission History shows transactions for a set timeframe. Older ones are reached through its Search tab, and in SWIPR you see only the reports you submitted yourself.

More in Government: US federal

Other industries: eVA, Maryland Tax Connect, GDOL Employer Portal, Airgas, e-staffing, ABC Order.

Frequently asked questions

Not a general one for the companies that sign in, as far as EPA's CDX pages describe. Data moves between EPA, states, tribes and territories over Exchange Network nodes, and node transactions appear in Submission History. Registration, roles and signing run in CDX's web screens.

In the Submission History tab of MyCDX: click a Submission ID to open its details. Older transactions are in the archive under the Search tab. Your Electronic Signature Agreement is kept in Submission History, and a copy arrives by email titled "Electronic Signature Agreement".

Yes, as a Preparer. In CEDRI contractors may register as Preparers, who prepare reports but cannot sign or submit them. The Certifier, who signs and submits, must be the facility's authorized representative, owner or operator, and contractors may not hold that role.

From MyCDX, click Add Program Service, select the program, choose a role and request access; you do not need a new account. To add a role in a program you already have, go to Manage Your Program Services, click List Roles, then Request a New Role.

No. Fous is an independent product. You use it with your own CDX account, and a method reads and does only what that account can.

Put EPA Central Data Exchange 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 nextSAM.govCM/ECFEFTPSeVAHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of EPA Central Data Exchange (US Environmental Protection Agency). 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.