FousPierPASS
Check your PierPASS TMF status through an API
Read the Traffic Mitigation Fee status of your import containers and your claimed export booking numbers from PierPASS with one API call each. A workflow can check the day's containers each morning and email you the ones without a TMF release.
Works with your own PierPASS account. Fous is an independent product.
What you can build on PierPASS
Check TMF status of containers
Build thisLooks up the containers you name in your PierPASS account and reads each one's status, the TMF due and whether the Pay tab is open.
- Takes
- Container numbers
- Returns
- Container number, size, status, TMF amount, pay available, paid date, release sent
List claimed export bookings
Build thisReads the export booking numbers claimed in your PierPASS account, with each booking's containers, status and fee.
- Takes
- Claimed since (optional)
- Returns
- Booking number, claimed date, containers, status, TMF amount, paid
Claim an export booking number
Build thisEnters an export booking number into your PierPASS account so its containers can enter the terminal.
- Takes
- Booking number
- Returns
- Booking number, claimed, status
Pay the TMF for containers
Build thisSelects the containers you name, opens Pay and pays the Traffic Mitigation Fee from your PierPASS prepaid account.
- Takes
- Container numbers
- Returns
- Container number, TMF amount, paid, payment reference
Automate PierPASS 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 list of containers not yet released
Build this- Starts
- When your system calls the workflow's webhook with the day's container numbers
- Step 1
- Check the TMF status of each container number your system sent.
- Step 2
- Keep the containers with no TMF release sent to the terminal.
- Step 3
- Email you the list with each container's status and TMF amount.
Export bookings not yet claimed
Build this- Starts
- When your system calls the workflow's webhook with new export booking numbers
- Step 1
- List the export booking numbers claimed in your PierPASS account.
- Step 2
- Keep the booking numbers your system sent that are not in that list.
- Step 3
- Post them to your system's webhook so someone claims them before the containers arrive.
TMF releases, posted to your drayage system
Build this- Starts
- Every 30 minutes on weekdays
- Step 1
- Check the TMF status of the containers you are tracking.
- Step 2
- Keep the containers whose TMF release was sent since the last run.
- Step 3
- Post each container number, paid date and TMF amount 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 “Check TMF status of containers” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "pierpass-tmf.org/check_tmf_status",
"input": {
"container_numbers": [
"ACMU4821937",
"NWDU7730415",
"GLBU2219864"
]
}
}'
{
"status": "completed",
"data": {
"containers": [
{
"container_number": "ACMU4821937",
"size": "40",
"status": "Active",
"tmf_amount": 81.26,
"pay_available": false,
"paid_date": "2026-11-12",
"release_sent": true
}
]
}
}
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.
PierPASS’s own options
PierPASS collects the Traffic Mitigation Fee through the web portal at pierpass-tmf.org: you register a company account, claim export booking numbers and pay there. The PierPASS and WCMTOA sites describe no API or data feed. What the account adds is email notifications on account events and payment by prepaid account or credit agreement.
| Option | What it covers | What it takes |
|---|---|---|
| Email notifications | Emails on events in your account, such as Containers Released (TMF Paid), to people inside or outside your company. | A registered PierPASS account; you choose the recipients for each event. |
| Prepaid account or credit agreement | Paying the TMF from a prepaid balance or on credit instead of by card or eCheck each time. | An account at pierpass-tmf.org; WCMTOA members may require collateral from credit customers. |
| The PierPASS portal by hand | Claiming export booking numbers, paying the TMF by card, debit card or eCheck, and checking container status. | A company account registered at pierpass-tmf.org, with one logon for each user. |
Read on November 12, 2026: PierPASS registration, WCMTOA Marine Terminal Operator Schedule No. 1, Supplemental Schedule A: TMF payment procedures.
Signing in to PierPASS
PierPASS signs you in with a Login ID and a password, and the same Login ID and password also sign you in to PortCheck. A company can set up several logons on its account. With Fous you sign in once through PierPASS's own sign-in with your own account; the login is sealed with AES-256, code and AI agents never see it, and when a session expires Fous signs back in.
Worth knowing
- Claim export bookings before the gate
- The booking number for an export container must be claimed in your PierPASS account before the container arrives. A container whose booking number is not claimed is not permitted to enter the terminal.
- Export fees are due before the next Tuesday
- For exports paid by card, debit card or eCheck, the TMF is due before the Tuesday after the container enters the terminal. Exports cannot be delivered while payment on past containers is not current.
- Import fees are paid before the container leaves
- Unless other arrangements are made, the TMF on an import container must be paid before it leaves the terminal. Once paid, PierPASS sends a TMF release to the terminal.
- Refunds have a 30-day window
- If you paid the TMF on a container that is exempt from it, you can ask PierPASS for a refund within 30 days of the payment date.
More in Logistics: ocean carriers, terminals and ports
- myDCLI
- PayCargo
- APM Terminals TERMPoint
- Georgia Ports WebAccess
- 易港通
- INTTRA
- CMA CGM eBusiness
- COSCO SHIPPING Lines eBusiness
- Maersk.com
- myMSC
- ONE eCommerce
- ShipmentLink
- eModal
- PortTruckPass
- DAKOSY
- Destin8
- Portbase
- Forecast by Tideworks
- 1-Stop Vehicle Booking System
Other industries: WEX fleet card portal, Exostar, LR Class Direct, RTBA Online, myCintas, AlbertsonsNet for Suppliers.
Frequently asked questions
Not that its sites describe. The TMF is claimed and paid in the web portal at pierpass-tmf.org, and the account can email you or your drayage company on events such as Containers Released (TMF Paid). Prepaid accounts and credit agreements change how you pay, not where.
US$40.63 per 20-foot container and US$81.26 for every other container size, under the WCMTOA schedule revised on August 1, 2026. It applies to import and export containers moving through the Los Angeles and Long Beach terminals of WCMTOA members.
Yes. The PierPASS account lets you add people outside your company to the Containers Released (TMF Paid) notification, so they get an email when the TMF is paid and a release has been sent to the terminal.
By Visa, MasterCard or American Express credit card, a Visa or MasterCard debit card, an electronic check through TeleCheck, a prepaid account or a credit arrangement. The ocean carrier moving the cargo may not pay it for you.
No. Fous is an independent product. It signs in to PierPASS with your own account and reads or does only what that account can.
Put PierPASS 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 nextForecast by Tideworks1-Stop Vehicle Booking SystemmyDCLIWEX fleet card portalHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of PierPASS (PierPASS, Inc.). 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.