Skip to content

FousTransport4

Get your Transport4 nominations and tickets through an API

Read your nominations, their cycle, phase and tankers, and your measurement tickets from Transport4 with one API call each. Or have a workflow check each morning which batches still have no receipt tanker before the carrier's deadline.

Start building freeBook a demo

Works with your own Transport4 account. Fous is an independent product.

What you can build on Transport4

  • Inquire nominations

    Build this

    Reads Inquire Nominations for one carrier, filtered by product, cycle or requested event dates, with each batch's receipt and delivery events.

    Takes
    Carrier, product (optional), cycle (optional), requested event dates (optional)
    Returns
    Batch Id, shipper, product, SCD, cycle, phase, status, and for the receipt and the delivery: location, volume, units, S/C, tanker, requested event date

  • Get measurement tickets

    Build this

    Reads the tickets the carrier issued for your batches, including corrected tickets that supersede an earlier one.

    Takes
    Carrier, issued since (optional), Batch Id (optional)
    Returns
    Ticket number, Batch Id, product, location, volume, units, tanker

  • Get a location's schedule

    Build this

    Reads the receipt or delivery schedule for one location: which batches arrive or leave, when, and how much.

    Takes
    Carrier, location, receipt or delivery, date range
    Returns
    Batch Id, product, event type, volume, units, tanker, scheduled date

  • Enter the receipt tanker on a nomination

    Build this

    Finds one nomination in Inquire Nominations and enters the supply source on its receipt event: location, supplier and tanker.

    Takes
    Carrier, Batch Id, receipt location, supplier, tanker
    Returns
    Batch Id, event type, location, S/C, tanker, status

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

  • Batches with no receipt tanker, before the cut-off

    Build this
    Starts
    Every weekday at 7:00
    Step 1
    For each carrier you name, inquire nominations with requested event dates in the next 7 days.
    Step 2
    Keep the receipt events that have no tanker.
    Step 3
    Email you the list by carrier, with Batch Id, product, location, volume and requested event date.

  • Nominations whose status changed

    Build this
    Starts
    Every hour on weekdays
    Step 1
    For each carrier, inquire nominations for the current and next cycle.
    Step 2
    Keep the nominations whose status, cycle or phase changed since the last run.
    Step 3
    Post each one to your scheduling system's webhook with Batch Id, status, cycle and phase.

  • New tickets, posted to your inventory system

    Build this
    Starts
    Every day at 18:00
    Step 1
    For each carrier, get the measurement tickets issued since yesterday.
    Step 2
    Stop when there are none.
    Step 3
    Post ticket number, Batch Id, product, location, volume, units and tanker 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 “Inquire nominations” 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": "app.transport4.com/inquire_nominations",
    "input": {
      "carrier": "Northwind Pipeline",
      "product": "062",
      "cycle": "31"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "carrier": "Northwind Pipeline",
    "nominations": [
      {
        "batch_id": "NWP-ACM-062-311-E",
        "shipper": "ACM",
        "product": "062",
        "scd": "E",
        "cycle": "31",
        "phase": "1",
        "status": "Accepted",
        "receipt": {
          "location": "GX",
          "volume": 25,
          "units": "Mbarrels",
          "s_c": "Globex Refining",
          "tanker": "Globex Refining",
          "requested_event_date": "2026-11-14"
        },
        "delivery": {
          "location": "NW",
          "volume": 25,
          "units": "Mbarrels",
          "s_c": "Acme Terminals",
          "tanker": "Acme Terminals",
          "requested_event_date": "2026-11-19"
        }
      }
    ]
  }
}

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.

Transport4’s own options

Transport4 is the online Shipper Information System that pipeline carriers such as Buckeye use for nominations, schedules and tickets. Its Push options send schedules automatically and an email or EDI copy of every ticket. T4 Mobile shows nominations, schedules and tickets on a phone. The carrier documentation and app listing we read describe no developer API.

OptionWhat it coversWhat it takes
Push options for ticketsAn email or an EDI copy of every ticket, sent automatically.Chosen by the Transport4 user. Suppliers and consignees receive tickets only through Transport4.
Push options for schedulesReceipt and delivery schedules for a terminal's own locations, sent automatically one to three times a day.A Transport4 user set up for that terminal.
T4 MobileNominations, schedules and tickets, with profiles, nomination and schedule notifications, and nomination changes for Buckeye shippers.Your Transport4 account, on iPhone or iPad.
Transport4 by handNomination entry, Inquire Nominations, copying a nomination, schedules, tickets and Alerts, under each carrier's own rules.Access requested from the Transport4 help desk, with each carrier approving it.

Read on November 12, 2026: Buckeye Shipping Information Notebook, Section 2: Nominating and Scheduling, T4 Mobile on the App Store, Buckeye Shipping Information Notebook, Section 6.4: Batch and Ticket Numbers.

Signing in to Transport4

Access starts with a request to the Transport4 help desk naming your company administrator, who assigns your company's Transport4 user accounts, and the carriers you need: each carrier must approve. With Fous you sign in once through Transport4's own sign-in with your own account: the login is sealed with AES-256, code and AI agents never see it, and an expired session is signed back in.

Worth knowing

One Batch Id per nomination entry
Each nomination entry gets one Batch Id, so a group of nominations cannot go in as one entry. The batch data (shipper, product, cycle and SCD) cannot be changed in Transport4 after the carrier assigns it.
Cycle and phase arrive minutes later
On Buckeye, a new nomination can take several minutes before it is assigned a cycle and phase. Read it again before you use its cycle and phase.
Supply source three business days ahead
On Buckeye, the final confirmed supply source is due three business days before lifting: for a Monday batch, by 23:59 pipeline time the prior Tuesday. A batch without one is rejected through Transport4.
Corrected tickets carry a letter
On Buckeye, a corrected measurement ticket keeps its number with a fifth character from A to Z: an A ticket supersedes the original, a B ticket supersedes the A ticket. Keep only the latest one.

More in Energy and utilities

Other industries: Transgourmet Webshop, Westpac Corporate Online, U.S. Bank Access Online, BIR eFPS, FBR IRIS, GetYourGuide Supplier Portal.

Frequently asked questions

Not one described in the carrier documentation or app listing we read. What they describe is Push: schedules sent automatically one to three times a day, and an email or EDI copy of every ticket. With Fous you can build methods on the Transport4 web application with your own account.

It depends on the carrier. Buckeye asks for nominations in Transport4 no later than the 15th of the month before the shipment month, and handles later requests on a best-efforts basis only. Late changes may carry a penalty under its Item No. 140.

Transport4's Alert blinks when Buckeye rejects a nomination, and a batch is presumed accepted unless the scheduler says otherwise in Transport4. A workflow that inquires nominations every hour can report each status change to you.

Yes, through Push options: Transport4 can send an email or EDI copy of every ticket automatically. Suppliers and consignees receive tickets only through Transport4. A workflow can also read new tickets each day and post them to your own system.

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

Put Transport4 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.

Start building freeBook a demo

Read nextSmart Meter TexasSmartHubMy WMTransgourmet WebshopHow methods workHow workflows run

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