Pull your WEX fleet card data into your own systems

What you can build on WEXOnline

• Get a driver's transactions

  Build this

  Opens Cards > View Driver, selects the driver and reads View Transactions for the period you give, up to the 30 days the screen shows.

  Takes

  Driver, start date, end date

  Returns

  Date, card, vehicle, merchant, product, quantity, amount

• Run an exception report

  Build this

  Builds a search under Transactions > Add Exception Report for one account, by date, driver, card, vehicle, merchant, product or department, and reads the results.

  Takes

  Account, date range, filters (optional)

  Returns

  Date, driver, card, vehicle, merchant, product, quantity, amount, department

• List invoices

  Build this

  Reads Payments > View Invoices, narrowed with the Advanced Search Filter, for the account and dates you give.

  Takes

  Account, invoice date from, invoice date to

  Returns

  Invoice number, account, invoice date, due date, amount due

• Suspend or terminate a card

  Build this

  Opens Cards > View Cards, selects the card and uses Change Status to set it to Suspended or Terminated.

  Takes

  Card number (last digits), new status

  Returns

  Card, driver or vehicle, previous status, new status

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

• Morning exception report, sent to you

  Build this

  Starts

  Every weekday at 7:00

  Step 1

  Run the exception report for yesterday on each account, with the multiple daily purchases filter.

  Step 2

  Stop when nothing matches.

  Step 3

  Email you the transactions grouped by driver, with card, merchant, product, quantity and amount.

• New invoices, handed to accounts payable

  Build this

  Starts

  Every day at 8:00

  Step 1

  List the invoices of the last 7 days from Payments > View Invoices.

  Step 2

  Keep the invoices that were not there on the last run.

  Step 3

  Post invoice number, account, invoice date, due date and amount due to your ERP webhook.

• Weekly fuel spend per driver, for job costing

  Build this

  Starts

  Every Monday at 6:00

  Step 1

  For each driver you name, get last week's transactions.

  Step 2

  Have an AI step total quantity and amount per driver and per product.

  Step 3

  Post the totals and the transaction rows 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 driver's transactions” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "go.wexonline.com/get_driver_transactions",
    "input": {
      "driver": "D-0104",
      "start_date": "2026-11-02",
      "end_date": "2026-11-08"
    }
  }'

{
  "status": "completed",
  "data": {
    "driver": "D-0104",
    "transactions": [
      {
        "date": "2026-11-03T06:42:00",
        "card": "...4417",
        "vehicle": "Truck 12",
        "merchant": "Northwind Fuel Stop, Columbus OH",
        "product": "Diesel",
        "quantity": 58.2,
        "amount": 211.85
      }
    ],
    "count": 1,
    "total_amount": 435.11
  }
}

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.

WEXOnline’s own options

WEX documents a Fleet Management API for partners and large fleets: accounts, cards, drivers and vehicles, authorizations, statement payments and fuel sites. You start with your WEX account team, which creates your account, sets up a testing environment and issues a client_id and client_secret. Otherwise you have WEXOnline, where transaction and invoice lists export to CSV or Excel.

Read on November 12, 2026: WEX Fleet Management API, Getting started with the Fleet API, WEX customer support: fleet accounts.

Signing in to WEXOnline

WEXOnline signs you in with the email address on your user and your password. If you only know your old username, you enter it with your password to find that email. With Fous you sign in once through WEXOnline's own sign-in with your own user, and the login is sealed with AES-256, never returned by the API or written to logs.

Worth knowing

Driver transactions show 30 days

View Transactions under Cards > View Driver shows a 30-day period for one driver. To search across drivers by date, card or vehicle, build an exception report.

Suspended or Terminated

Change Status offers Suspended when a lost card might be found, and Terminated to deactivate it for good. A replacement is a separate reissue with a reason: lost, damaged or stolen.

Authorization profiles set what a card buys

Each card follows an authorization profile, either Fuel Only or Custom Control, listed under Cards > View Auth Profiles. A new card needs a profile when you add it.

One active API token per client

On WEX's Fleet API, generating a new token invalidates the previous one for the same credentials, and an expired token returns 401. Reuse a token until then.

More in Logistics: trucking, rail and parcel

• Carrier 360 by J.B. Hunt
• Navisphere Carrier
• RXO Connect
• TQL Carrier Dashboard
• Highway
• RMIS
• MyCarrierPortal
• Triumph Payments portal
• C3 Reservations
• Kroger One Network portal
• NCR Power Traffic
• Opendock
• Walmart Scheduler 2.0
• One Network
• CassPort
• TIMOCOM
• Trans.eu
• DAT One
• Truckstop
• B2クラウド
• AccessNS
• BNSF Customer Portal
• MyUP
• ShipCSX
• Transporeon
• Toll Collect Kunden-Portal

Other industries: Exostar, LR Class Direct, RTBA Online, myCintas, AlbertsonsNet for Suppliers, Coles Supplier Portal.