Integrations · Fuel cards and tolls
WEX FleetOne integration: auto-lock fuel cards in Tezify
Ask WEX FleetOne for card-management API access, enter the key and endpoint on the card, and Tezify can lock a driver's card while paperwork is owed and unlock it when the POD is in.
What WEX FleetOne does in Tezify
Tezify can lock a driver's WEX FleetOne card when paperwork is owed. The rule: when a driver is loaded at the shipper for the next load but still owes the POD or BOL for a load already delivered, the fuel card locks. Uploading the missing paperwork unlocks it.
Until the WEX FleetOne keys and endpoint are saved, the lock shows in Tezify only and the card stays active on the network.
Who needs it
Carriers and trucking companies. The WEX FleetOne card shows on the carrier company's Integrations page. In a workspace that also runs a separate brokerage company, the brokerage side does not see it.
What you need from WEX FleetOne
- A WEX FleetOne account.
- WEX Mobility API partner enrollment (fleetapi.wexinc.com).
- The card-management endpoint from your WEX rep, plus either a token or a username and password.
Connect WEX FleetOne to Tezify
- Enroll at fleetapi.wexinc.com, or ask your WEX rep to enroll you.
- In Tezify, open Integrations and find the WEX FleetOne card. The link at the top of this page opens it.
- Paste the endpoint into API base URL. This one is required.
- If WEX gave you a token, paste it into API key / Bearer token. If WEX gave you a username and password, use Username and Password.
- If WEX gave you a client ID and secret instead, tell Tezify support first. That sign-in type is not built yet.
- Tick Active and press Save keys.
Test the connection
Press Check keys are filled in. There is no test call for WEX FleetOne, so this only proves the fields are saved. Then lock one test card from the Fuel page and confirm in WEX FleetOne that it is locked.
Common errors and fixes
| What you see | What to do |
|---|---|
| The lock shows in Tezify, but the card still works. | Both the key and the API base URL are needed. Until both are saved, the lock only shows in Tezify. |
| Card lock is not tried. | The API base URL is empty. Card lock needs it. |
| WEX FleetOne answers 401 or 403. | The key is wrong, expired, or lacks permission. Create a new key, paste it again with no spaces, save, and test. |
| Could not reach WEX FleetOne. | Leave the API base URL blank unless the vendor gave you another one. Then test again in a minute. |
What syncs and how often
- Lock and unlock calls go out when a driver's paperwork status changes. No transactions are pulled from the card network.
Limits
- Card lock only. Fuel transactions are not imported through this card.
- API access is partner-gated. Your card provider must turn it on.
- OAuth client-credential sign-in is not built.
Ready to do it? This lives at /admin/integrations?open=wex-fleetone in Tezify.
Related articles
- IntegrationsFuel card and toll integrations in Tezify
- IntegrationsRelay fuel card integration: auto-lock cards in Tezify
- IntegrationsEFS fuel card integration: auto-lock cards in Tezify
- IntegrationsFuel price email import: refresh truck-stop prices daily
- IntegrationsLive station fuel prices: diesel along the route
- IntegrationsPrePass integration: import toll statements into Tezify