Skip to content

FousBushel

Pull your Bushel tickets and contracts into your systems

Read your scale tickets, contract balances and a location's cash bids from your grain buyer's Bushel-powered portal with one API call each. Or have a workflow check the day's loads every evening of harvest and list each new ticket's net units and moisture.

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

What you can build on Bushel

  • Get scale tickets

    Build this

    Reads the Scale Tickets list, filtered by Commodity, time range, Account and delivery Location, with each ticket's weights, grade factor and splits.

    Takes
    Commodity (optional), from date, to date, account (optional), location (optional)
    Returns
    Ticket number, date and time, commodity, delivery location, gross weight, tare weight, net weight, net units, shrink units, grade factor, split owners and percentages
  • Get contract balances

    Build this

    Reads the Contracts list, open contracts first, with each contract's type, delivery period, delivered and remaining quantity and pricing status.

    Takes
    Status (Open or Closed, optional), commodity (optional), crop year (optional)
    Returns
    Contract number, type, commodity, delivery location, delivery period, contracted, delivered, remaining, priced and unpriced quantity, pricing status, signature status
  • Get cash bids for a location

    Build this

    Reads Cash Bids for one delivery location, as the portal shows them at that moment.

    Takes
    Location
    Returns
    Location, commodity, delivery period, cash price, and basis and futures where shown
  • Sign a contract with eSign

    Build this

    Opens a contract waiting for your signature and signs it with eSign, then reads back its signature status.

    Takes
    Contract number
    Returns
    Contract number, commodity, contracted quantity, signature status

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

  • The day's scale tickets, every evening of harvest

    Build this
    Starts
    Every day at 19:00
    Step 1
    Get the scale tickets dated today, for every commodity and location.
    Step 2
    Keep the tickets that were not there on the last run.
    Step 3
    Email you the list with ticket number, location, net units, the grade factor shown and shrink units.
  • Open contracts left to deliver or price, weekly

    Build this
    Starts
    Every Monday at 7:00
    Step 1
    Get the contract balances with status Open.
    Step 2
    Keep the contracts with a remaining or unpriced quantity above zero.
    Step 3
    Email you the list sorted by delivery period, with remaining and unpriced quantity.
  • Morning cash bids, posted to your own system

    Build this
    Starts
    Every weekday at 8:30
    Step 1
    For each delivery location you name, get the cash bids.
    Step 2
    Keep the bids that changed since the last run.
    Step 3
    Post location, commodity, delivery period, cash price and basis where shown 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 scale tickets” 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": "bushelpowered.com/get_scale_tickets",
    "input": {
      "commodity": "Soybeans",
      "from": "2026-10-20",
      "to": "2026-10-21"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "tickets": [
      {
        "ticket_number": "418273",
        "date_time": "2026-10-21T14:32",
        "commodity": "Soybeans",
        "delivery_location": "Northwind Elevator, Main",
        "gross_weight_lb": 79840,
        "tare_weight_lb": 29420,
        "net_weight_lb": 50420,
        "net_units_bu": 836.12,
        "shrink_units_bu": 4.21,
        "moisture_pct": 13.4,
        "split_owners": "Acme Farms 100%"
      }
    ]
  }
}

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.

Bushel’s own options

Bushel's developer documentation is for grain companies and the services they work with: an API to push a grain company's data into Bushel, an eSign API, and Connections, a data feed for third-party services that a farmer opts in to. Bushel supplies each integrator's credentials. Nothing in it lets a farmer get credentials for their own tickets and contracts: farmers use their grain buyer's portal or app.

OptionWhat it coversWhat it takes
Connections data feedA historical load of a farmer's data and near-real-time updates, sent to a third-party service's endpoints for the accounts the farmer chose.A consumer ID and secret supplied by Bushel to the integrating service; start by contacting a Bushel representative. Each farmer opts in.
Pushing Data and eSign APIsSending a grain company's own records into Bushel, and contract signing through eSign.For grain companies and integrators working with Bushel.
The portal or app by handScale Tickets, Contracts, Commodity Balances, Cash Bids, Prepaid & Bookings, Settlements and eSign, for one grain company.An account with each grain buyer's Bushel-powered portal; the app is free.

Read on November 12, 2026: Bushel Connections: getting started, Bushel developer documentation, Bushel FAQ.

Signing in to Bushel

Each grain company has its own Bushel-powered portal and branded app, and Bushel's FAQ says farmers log in with their phone number. With Fous you sign in once through your grain buyer's own portal sign-in with your own account: the login is sealed with AES-256 and never shown to your code or AI agents.

Worth knowing

One portal per grain company
Bushel tells farmers to find the log-in on their agribusiness partner's website or to search the partner's name in the app stores. If you sell to two buyers, you build a method for each portal.
Filters and grade factors vary by buyer
Scale Tickets filter by Commodity, time range, Account and Location, but a filter with fewer than two values is hidden. The grade factor beside each ticket is set per commodity, Moisture by default.
Split tickets show each owner's share
A ticket can be split between accounts, each with a Split Owner and Split Percentage. Ticket details link to related Contracts or Settlements when the grain company provides them.
Priced means futures and basis are both set
A contract's pricing status is Priced, Partial or Unpriced, and a pricing line counts as priced only when both its futures price and basis price are set. Open contracts come first, by nearest delivery date.

More in Other industries

Other industries: Rithum OrderStream, Asda Supplier Portal, AT&T Premier, Travis Perkins, Petronect, CONTPAQi.

Frequently asked questions

Yes, for grain companies and the services Bushel connects. Connections is a data feed for third-party services whose credentials Bushel supplies, and each farmer opts in to share chosen accounts. Grain companies push their own data in through a separate API. There is no key a farmer can request for their own tickets.

Yes. Scale Tickets can be filtered by Commodity, time range, Account and delivery Location, and searched by ticket ID. A method you build on that list returns each ticket's number, weights, net units, shrink and grade factor as JSON for the range you give.

Open Contracts. Each contract shows its contracted, delivered, remaining, priced and unpriced quantity, its delivery period and its pricing status. A closed contract shows a green checkmark below the Remaining bar.

Each grain company runs its own Bushel-powered portal and app, and Bushel points farmers to each partner's own log-in. With Fous you sign in to each portal once and build methods for each, and a workflow can run them on the same schedule.

No. Fous is an independent product. You use it with your own account on your grain buyer's Bushel-powered portal, and a method reads and does only what that account can.

Put Bushel 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 nextNLIS databaseFoodLogiQ ConnectKinderConnectRithum OrderStreamHow methods workHow workflows run

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