Skip to content

FousWEX Benefits employer portal

Turn the WEX Benefits employer portal into an API

Read an employee's enrollments and election amounts, or a COBRA qualified beneficiary's payments, from LEAP with one API call each. Or have a workflow check this week's COBRA payments and email you the ones that just posted.

Works with your own WEX Benefits employer portal account. Fous is an independent product.

What you can build on LEAP

  • Get an employee's enrollments

    Build this

    Finds the employee under the Employees tab in Benefits Administration and reads each plan on the Enrollments tab, with its election and estimated payroll amount.

    Takes
    Employee name or employee number
    Returns
    Employee number, division, plan, effective date, annual election, payroll frequency, estimated payroll amount
  • Look up a COBRA qualified beneficiary

    Build this

    Opens COBRA Administration, uses Find Member, and reads the QB's Profile, Payments and Premiums due sections.

    Takes
    Last name, SSN (optional)
    Returns
    Name, qualifying event, COBRA dates, plans, last payment, payment history, premiums due
  • Update an employee's election amount

    Build this

    Opens the employee's Enrollments tab, edits the enrollment, picks the update type in Update Enrollment, enters Effective Date and Election, and clicks Add.

    Takes
    Employee number, plan, update type, effective date, new annual election
    Returns
    Employee number, plan, effective date, annual election, estimated payroll amount
  • Add a new employee

    Build this

    Uses Add Employee under the Employees tab to enter the personal and employment information, then clicks Add Employee.

    Takes
    Name, birth date, SSN, address, email, employee number, hire date, payroll frequency and its effective date, division
    Returns
    Employee number, hire date, division

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

  • COBRA payments posted this week

    Build this
    Starts
    Every Friday at 16:00
    Step 1
    For each qualified beneficiary on your list, look up the QB in COBRA Administration.
    Step 2
    Keep the payments that were not there on the last run.
    Step 3
    Email you the list with each QB's name, plan, payment and premiums still due.
  • Election amounts checked against payroll deductions

    Build this
    Starts
    When your payroll system calls the workflow's webhook with employee numbers and deductions
    Step 1
    For each employee number, get the employee's enrollments in Benefits Administration.
    Step 2
    Keep the employees whose estimated payroll amount differs from the deduction you sent.
    Step 3
    Post them, with plan, annual election and both amounts, to your payroll webhook.
  • Changed COBRA profiles, every Monday

    Build this
    Starts
    Every Monday at 8:00
    Step 1
    For each qualified beneficiary on your list, look up the QB's profile and premiums due.
    Step 2
    Keep the QBs whose plans or premiums due changed since the last run.
    Step 3
    Email you each change with the QB's name, plans and premiums due.

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 an employee's enrollments” 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": "employerbenefits.wexhealth.com/get_employee_enrollments",
    "input": {
      "employee_number": "456123"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "employee_number": "456123",
    "division": "Acme Distribution",
    "enrollments": [
      {
        "plan": "Health Care FSA 2026",
        "effective_date": "2026-01-01",
        "annual_election": 2400,
        "payroll_frequency": "Biweekly",
        "estimated_payroll_amount": 92.31
      },
      {
        "plan": "Dependent Care FSA 2026",
        "effective_date": "2026-03-01",
        "annual_election": 5000,
        "payroll_frequency": "Biweekly",
        "estimated_payroll_amount": 192.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.

LEAP’s own options

WEX runs a developer portal for its health and benefits platform, but its documentation is not publicly readable. LEAP shows the data transmission with your HRIS or payroll, employees normally arrive on a file, and COBRA QB and newly covered employee files can be imported. Everything else is done on LEAP's screens.

OptionWhat it coversWhat it takes
WEX H&B Developer PortalWEX's developer documentation for its health and benefits platform. Its pages are not publicly readable.Access through WEX, since the pages are not publicly readable.
HRIS and payroll data transmissionThe data exchanged between your HRIS or payroll and WEX, including the employee file. LEAP lets you view each data transmission.A data feed between your HRIS or payroll system and WEX.
COBRA file importsImporting qualified beneficiary or newly covered employee files in the COBRA employer online account.Access to COBRA Administration in LEAP.
LEAP by handEmployees, enrollments, contributions, reports, invoices and COBRA records, one employee or QB at a time.A LEAP username and password, with the access your team's administrator grants.

Read on November 12, 2026: LEAP employer benefits portal, Guide to the COBRA employer online account, WEX H&B Developer Portal.

Signing in to LEAP

LEAP signs you in with a username and password, and one login reaches both Benefits Administration and COBRA Administration. WEX documents no second step. With Fous you sign in once through LEAP's own sign-in with your own account: the login is sealed with AES-256, and an expired session is signed back in.

Worth knowing

Key-in is the fallback to the file
WEX's guide says to key in an employee only when the file does not pass them through. If you make employer contributions to a Medical or Dependent Care FSA, key-in is not an option.
An election, once entered, stays
Once an election amount is entered for a plan during enrollment, the plan cannot be removed from the employee in LEAP. You have to contact your WEX or program contact.
Your plan setup decides the fields
Fields your plan does not require do not appear when you add an employee. Payroll frequency and division lists appear only if you have more than one of them.
COBRA records are found one at a time
In COBRA Administration, QB, newly covered employee and Direct Bill records are found with Find Member by last name or SSN, so a method takes the member as an input.

More in Insurance

Other industries: TyMetrix 360, myDHLi, Fidelity Plan Sponsor WebStation, ONE eCommerce, NCR Power Traffic, Mercedes-Benz Supplier Portal.

Frequently asked questions

Not a public one. WEX runs a developer portal for its health and benefits platform, but its documentation is not publicly readable. LEAP shows the data transmission with your HRIS or payroll, and COBRA QB and newly covered employee files can be imported. The rest is done on LEAP's screens.

Open COBRA Administration in LEAP, select Find Member and search by last name or SSN. The QB's Profile shows the last payments, the Payments section the full payment history, and Premiums due what is due through the end of COBRA.

Yes, with Add Employee under the Employees tab, then Add New Enrollment. WEX's guide treats this key-in method as a fallback for when the file does not pass the employee through, and it is not an option if you make employer contributions to a Medical or Dependent Care FSA.

In each record's Communications section in COBRA Administration. A newly covered employee's record holds the General Rights Notice that was sent, and a QB's record holds the letters sent to the participant, which you can download.

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

Put WEX Benefits employer portal 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.

Read nextNIPRAflac Business ServicesNational General agent portalTyMetrix 360How methods workHow workflows run

Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of WEX Benefits employer portal (WEX). 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.