Read your TRACS vouchers and certifications by API

What you can build on TRACS

• Get vouchers for a HAP contract

  Build this

  Runs the Voucher Query under Voucher/Tenant Queries for one HAP contract number and reads the vouchers it lists, most recent first.

  Takes

  HAP contract number

  Returns

  Voucher date, status, flags

• Check certifications for a HAP contract

  Build this

  Runs the Certification Query for one HAP contract and reads the current certifications in TRACS, with the Active Tenants and any discrepancies.

  Takes

  HAP contract number

  Returns

  Tenant name, active tenant or not, current certification, has discrepancies

• Get a tenant's discrepancies and history

  Build this

  Opens one tenant from the Certification Query and reads the Discrepancies (TRACS error messages) and the Certification History List.

  Takes

  HAP contract number, tenant name

  Returns

  Error messages, certifications in the history list

• Read new iMAX messages

  Build this

  Opens iMAX and reads the messages in your mailbox, such as the error descriptions TRACS returns the day after a transmission.

  Takes

  Received since (optional)

  Returns

  Sender, date received, message text

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

• Voucher status for each HAP contract, the day after you transmit

  Build this

  Starts

  Every weekday at 8:00

  Step 1

  For each HAP contract you name, get the vouchers from the Voucher Query.

  Step 2

  Keep the vouchers whose status or flags changed since the last run.

  Step 3

  Email you the changes, one section per contract.

• Certification discrepancies before the next voucher

  Build this

  Starts

  Every Monday at 7:00

  Step 1

  For each HAP contract, check certifications with the Certification Query.

  Step 2

  For each tenant with discrepancies, get the error messages.

  Step 3

  Post contract number, tenant name and error messages to your compliance system's webhook.

• New iMAX messages, posted to your team

  Build this

  Starts

  Every weekday at 9:00

  Step 1

  Read the iMAX messages received since yesterday.

  Step 2

  Stop when there are none.

  Step 3

  Post sender, date received and message text to your Slack 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 vouchers for a HAP contract” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "hudapps.hud.gov/get_vouchers",
    "input": {
      "hap_contract_number": "XX00M000001"
    }
  }'

{
  "status": "completed",
  "data": {
    "hap_contract_number": "XX00M000001",
    "vouchers": [
      {
        "voucher_date": "2026-12",
        "status": "Received",
        "flags": []
      }
    ],
    "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.

TRACS’s own options

HUD offers no API for TRACS. Tenant certifications (HUD-50059) and monthly vouchers go to TRACS as MAT files from TRACS-compliant software, transmitted through iMAX. What TRACS holds is read by hand in its Voucher and Tenant queries in HUD Secure Systems.

Read on November 12, 2026: TRACS Tip Sheet (HUD Exchange), Guide to HUD Secure Systems Access (HUD Exchange), PHFA general voucher submission requirements.

Signing in to TRACS

TRACS and iMAX are reached through HUD Secure Systems, where each person signs in with their own user ID (the M-ID) and password, and a coordinator assigns which systems, roles and properties they can see. With Fous you sign in once through Secure Systems' own sign-in with your own M-ID. The login is sealed with AES-256, and a method reads only what your roles allow.

Worth knowing

Errors arrive the day after you transmit

TRACS returns error descriptions through iMAX the day after a transmission, and a transmitted voucher shows in the Voucher Query from the next business day. A morning check fits that rhythm.

Access is per person and per property

Each person has one M-ID. A coordinator gives the TRACS query roles and assigns properties, and users must be recertified in those systems. HUD asks for two to five coordinators per business partner.

Your contract administrator sees it first

Where a contract administrator handles your contract, vouchers go to its iMAX address, and Secure Systems shows a voucher only once it has been approved and sent to HUD.

Compliance and due dates affect payment

A TRACS compliance rate under 90% can delay payment, according to one contract administrator. Another, PHFA, wants vouchers by the 10th of the month before the payment month.

More in Government: US federal

• BSA E-Filing System
• FINRA Gateway
• PostalOne
• USPS Business Customer Gateway
• Invoice Processing Platform
• FMCSA Drug & Alcohol Clearinghouse
• Wide Area Workflow
• E-Verify
• EPA Central Data Exchange
• SAM.gov
• CM/ECF
• EFTPS
• FBI NICS E-Check
• FLAG
• HUD Secure Systems
• USCIS online account
• IRIS Taxpayer Portal
• Motus
• USPTO Patent Center
• EDGAR Filer Management
• COD
• IRS e-Services
• IRS Tax Pro Account
• EIV
• USPTO Trademark Center
• SSA Business Services Online
• NetDMR

Other industries: Cal eProcure, NCDOR eBusiness Center, Sunbiz, ODP Business Solutions, ShiftWise Flex, PCSE Online.