Skip to content

Fous340B ESP

Get your 340B ESP account eligibility through an API

Build methods that read At Risk and Suspended accounts, claims submission results and contract pharmacy designations from 340B ESP, one API call each. Or have a workflow check Purchase Validation each weekday and email you the accounts that newly went At Risk.

Start building freeBook a demo

Works with your own 340B ESP account. Fous is an independent product.

What you can build on 340B ESP

  • Get At Risk and Suspended accounts

    Build this

    Reads the Accounts section of the Purchase Validation module, grouped into Suspended Accounts, At Risk Accounts and All Other Accounts.

    Takes
    Status (optional), manufacturer (optional)
    Returns
    Manufacturer, pharmacy, account status, unvalidated purchases, unvalidated WAC

  • Check claims submission results

    Build this

    Reads a Claims Data module's list of submitted files and, for each, the Non-Conforming Claims Issue Summary.

    Takes
    Submission module, submitted since (optional)
    Returns
    Date, status, claims, % conforming, non-conforming issues

  • List contract pharmacy designations

    Build this

    Reads the Single Contract Pharmacy Designations report, for one covered entity and one manufacturer when you name them.

    Takes
    Covered entity (optional), manufacturer (optional)
    Returns
    Manufacturer, entity (340B ID), pharmacy, address, HIN, type

  • Designate a contract pharmacy

    Build this

    In the Entity Profile, picks the manufacturer, selects Make Designation, confirms the policy, chooses the Designated Pharmacy and saves the designation.

    Takes
    Covered entity, manufacturer, contract pharmacy
    Returns
    Covered entity, manufacturer, pharmacy, saved or not

Automate 340B ESP 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.

  • Accounts newly At Risk or Suspended

    Build this
    Starts
    Every weekday at 7:00
    Step 1
    Get the At Risk and Suspended accounts from Purchase Validation.
    Step 2
    Keep the accounts that were not At Risk or Suspended on the last run.
    Step 3
    Email you each one with manufacturer, pharmacy, unvalidated purchases and unvalidated WAC.

  • Claims submissions with non-conforming claims

    Build this
    Starts
    Every weekday at 9:00
    Step 1
    Check the claims submission results in Pharmacy Submissions since yesterday.
    Step 2
    Keep the files in Complete status with % Conforming below 100.
    Step 3
    Post each file's date, claims, % Conforming and non-conforming issues to your webhook.

  • Weekly check of contract pharmacy designations

    Build this
    Starts
    Every Monday at 8:00
    Step 1
    For each covered entity you name, list its contract pharmacy designations.
    Step 2
    Keep the designations added or gone since the last run.
    Step 3
    Email you the changes, one section per covered entity.

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 At Risk and Suspended accounts” 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": "340besp.com/get_at_risk_and_suspended_accounts",
    "input": {
      "status": "At Risk"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "covered_entity": "Acme Community Health",
    "accounts": [
      {
        "status": "At Risk",
        "manufacturer": "Globex Therapeutics",
        "pharmacy": "Northwind Pharmacy, Springfield",
        "account_type": "Individual Contract Pharmacy",
        "unvalidated_purchases_units": 340,
        "unvalidated_wac": 18412.5
      }
    ],
    "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.

340B ESP’s own options

340B ESP offers an API and SDKs to partners such as TPAs and consultants. A partner gets its tokens from 340B ESP Support, and a covered entity's Admin adds the partner's access token in Settings. Covered entities themselves upload Excel or CSV claims files in the Claims Data modules and can download their account data as Excel, their designations and each submission's data.

OptionWhat it coversWhat it takes
Partner API and SDKPartners submit and retrieve a covered entity's data, such as eligibility and claims, on its behalf.Partner onboarding with 340B ESP Support, an access token and a private token, and an Admin granting Read Eligibility or Read and Write Submissions.
DownloadsThe Purchase Validation Download File in Excel, the Designation File across your covered entities, and the Submission Data of each submission.A registered 340B ESP account with access to the covered entity.
340B ESP by handClaims Data uploads with column mapping templates, Purchase Validation, Submission Balances, the Entity Profile and the Reports module.A registered 340B ESP account for your covered entity.

Read on November 12, 2026: Partner access tokens in 340B ESP, How to add a partner to your covered entity, Purchase Validation overview.

Signing in to 340B ESP

You sign in to 340B ESP with the credentials you create once your account is verified. Two-factor authentication with the phone number you gave at registration is optional and recommended, and too many failed attempts lock the account until support restores access. With Fous you sign in once through 340B ESP'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

Only conforming claims count
Only conforming claims add submitted units to the Submission Balances ledger. Claims outside the manufacturer's required submission window may remain non-conforming and add no units.
Read results once a submission is Complete
A submitted file shows Processing first and Complete once 340B ESP is done with it. Read its % Conforming and Non-Conforming Claims Issue Summary after it shows Complete.
SDK claims are in the Reports module
Claims a TPA submits through the 340B ESP SDK do not appear in the Claims Data modules. The Pharmacy Claims Details and Medical Claims Details reports show both direct and SDK claims.
HRSA decides which pharmacies appear
Only contract pharmacies Active in HRSA can be designated, and HRSA designations update quarterly. Under a 40-mile geo-restriction, pharmacies farther away cannot be selected.

More in Healthcare

Other industries: Navigate, PACER, ACE Secure Data Portal, Fidelity Wealthscape, 易港通, Highway.

Frequently asked questions

Yes, for partners such as TPAs and consultants. A partner gets an access token and a private token from 340B ESP Support, and your Admin adds the access token in Settings with Read Eligibility or Read and Write Submissions. As a covered entity you upload Excel or CSV claims files and download files in the portal.

The claims may not be linked to its purchases, or may not count. Unassigned Identifiers can keep purchases and claims from reaching the right account, non-conforming claims add no units, and some manufacturers mark a contract pharmacy At Risk because its associated CE Pharmacies and Clinics account is.

Submit the same claim detail again with a negative unit amount.

In part. The Entity Profile shows one covered entity at a time, chosen with Switch. The Designation File in the Covered Entities module covers all entities you are registered to. With Fous, a workflow can loop over your covered entities and call the same method for each.

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

Put 340B ESP 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 next340B OPAISHenry Schein online orderingAAH HubNavigateHow methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of 340B ESP (Second Sight Solutions). 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.