FousGeorgia Ports WebAccess
Turn Georgia Ports WebAccess into an API
Check container availability, read container details and history, and pull truck transactions with their trouble messages from Georgia Ports WebAccess with one API call each. Or have a workflow check your import list before dispatch every morning.
Works with your own Georgia Ports WebAccess account. Fous is an independent product.
What you can build on WebAccess
Check container availability
Build thisRuns Containers > Availability Inquiry for your container numbers and reads which ones are available for pickup and any status messages.
- Takes
- Facility (GCT or OT), container numbers, trucking company or ANY
- Returns
- Equipment ID, available or not, pickup date, status messages
Get container details and history
Build thisReads Containers > Container Detail and Container History for one container: line, category, status, position and every recorded event.
- Takes
- Facility, container number
- Returns
- Line, category, status, position, size, type, height, history events with dates
Get truck transactions and trouble messages
Build thisReads Gate > Truck Transactions for a date range, with the trouble messages and gate documents listed for each transaction.
- Takes
- Facility, start date, end date, trucking company ID (optional), equipment ID (optional)
- Returns
- Transaction number, date, trucking company, truck ID, equipment ID, trouble messages, documents
Pre-advise an import delivery
Build thisFills in Gate > PreGate Deliver Import with your trucking company code and container number, submits it and reads the PIN WebAccess returns.
- Takes
- Facility, trucking company code, container number, truck license number (optional)
- Returns
- PIN, container number, facility, error messages
Automate WebAccess 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.
Import containers ready for pickup, before dispatch
Build this- Starts
- Every weekday at 6:00 (America/New_York)
- Step 1
- For each container on your import list, check container availability at its facility.
- Step 2
- Keep the containers that are available now and were not available on the last run.
- Step 3
- Email you the list with equipment ID, facility and any status messages.
Yesterday's gate trouble messages, sent to dispatch
Build this- Starts
- Every day at 7:00 (America/New_York)
- Step 1
- Get yesterday's truck transactions for your trucking company at each facility.
- Step 2
- Keep the transactions that have trouble messages.
- Step 3
- Post transaction number, truck ID, equipment ID and the messages to your webhook.
Containers discharged to the yard, posted to your TMS
Build this- Starts
- Every hour
- Step 1
- For each container on your import list, get container details.
- Step 2
- Keep the containers whose position changed since the last run.
- Step 3
- Post equipment ID, line, status and position to your TMS 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 container availability” would look like.
curl https://api.fous.com/v1/runs \
-H "Authorization: Bearer $FOUS_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"method": "webaccess.gaports.com/check_container_availability",
"input": {
"facility": "GCT",
"containers": [
"ACMU4829176",
"NWDU3051184"
],
"trucking_company": "ANY"
}
}'
{
"status": "completed",
"data": {
"facility": "GCT",
"pickup_date": "2026-11-12",
"containers": [
{
"equipment_id": "ACMU4829176",
"available": true,
"status_messages": []
},
{
"equipment_id": "NWDU3051184",
"available": false,
"status_messages": [
"Container has not been released by the line"
]
}
],
"count": 2
}
}
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.
WebAccess’s own options
On its Customer Experience page, the Georgia Ports Authority lists API connectivity for automated exchange of operational data with ocean carriers, truckers, BCOs and tech providers, with no documentation or request process. For PINs, its WebAccess manual describes a file transfer set up with GPA's IT team. Everything else is WebAccess itself.
| Option | What it covers | What it takes |
|---|---|---|
| API connectivity | Automated exchange of operational data between the port's systems and ocean carriers, truckers, BCOs and third-party tech providers. | Not described further: the port's page gives no documentation, scope or request process. |
| Automated PINs by file transfer | Pre-advise import deliveries and empty receivals from comma-delimited files. The PINs are emailed back to the addresses you supply. | Set up with GPA's IT team, with files named after your trucking company code from Express. |
| Notify | An email when a container or chassis event you requested happens. Pending and Recent tables list your requests. | A WebAccess account. Each event must be requested before it happens. |
| WebAccess by hand | Availability Inquiry, Container Detail and History, EDO/Booking Detail, pre-advise forms and gate reports, one facility at a time. | A WebAccess account, which needs a SCAC code registered with the UIIA. |
Read on November 12, 2026: GPA Customer Experience, WebAccess Truckers Manual (PDF), Customer Experience FAQs (PDF).
Signing in to WebAccess
WebAccess first asks which facility you want, then for your username and password. The sign-on and password come from GPA after you register, within up to 24 business hours. With Fous you sign in once through WebAccess'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
- Each facility is separate
- Reporting in WebAccess is facility specific, and a PIN carries a terminal prefix such as GCT or OT. A container pinned at the wrong facility returns an error, so a method takes the facility as an input.
- PINs last 72 hours
- A pre-advise PIN is valid for 72 hours. WebAccess does not pre-fill the pre-advise forms, and container numbers go in without spaces and with the check digit.
- Notify only looks forward
- A Notify email covers only an event you requested before it happened. For events already past, such as an earlier gate-out, read Container History instead.
- Position letters
- In Container Detail, a V position means the container is still on the vessel, Y in the yard, T on a truck and R on a train.
More in Logistics: ocean carriers, terminals and ports
- myDCLI
- PayCargo
- APM Terminals TERMPoint
- 易港通
- INTTRA
- CMA CGM eBusiness
- COSCO SHIPPING Lines eBusiness
- Maersk.com
- myMSC
- ONE eCommerce
- ShipmentLink
- eModal
- PortTruckPass
- DAKOSY
- Destin8
- Portbase
- PierPASS
- Forecast by Tideworks
- 1-Stop Vehicle Booking System
Other industries: TQL Carrier Dashboard, Net-Inspect, Satair Market, CRMLS, KinderConnect, Scintilla.
Frequently asked questions
Not a public one. The Georgia Ports Authority lists API connectivity for carriers, truckers, BCOs and tech providers, but its page gives no documentation or request process. Automated PINs by file transfer are set up with GPA's IT team, and everything else is done in WebAccess.
In WebAccess, open Containers > Availability Inquiry and enter your container numbers in the Equipment ID field. An available container shows a green check mark, an unavailable one a red X, with messages when there is a problem with its status.
No. GPA does not charge for storage. The charges come from the ocean carrier, and you settle them with the carrier.
A SCAC code registered with the UIIA. You fill in the WebAccess registration form on gaports.com with your company type, SCAC code and cargo interest, and GPA sends a sign-on and password within up to 24 business hours.
No. Fous is an independent product. You use it with your own WebAccess account, and a method reads and does only what that account can.
Put Georgia Ports WebAccess 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 next易港通INTTRACMA CGM eBusinessTQL Carrier DashboardHow methods workHow workflows run
Fous is an independent product: it is not affiliated with, endorsed by or sponsored by the operator of Georgia Ports WebAccess (Georgia Ports Authority). 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.