Get your eVA orders and bid leads through an API

What you can build on eVA

• Get orders

  Build this

  Reads the orders listed under Orders, Acknowledge Orders in your eVA supplier account, with the Bill To details of each order.

  Takes

  Placed since (optional)

  Returns

  Order ID, PO or PCO, buying entity, bill to, items, total, attachments

• Get bid opportunities from My Leads

  Build this

  Reads My Leads and, for each opportunity, the Info and Items tabs and the list of files under Documents.

  Takes

  Type (optional: Quick Quote, IFB or RFP)

  Returns

  Opportunity number, title, type, buying entity, buyer, closing date, items, documents

• List draft responses in Manage RFx's

  Build this

  Reads Sourcing, Manage RFx's and returns the responses you saved but have not submitted, which eVA marks in progress.

  Takes

  Nothing

  Returns

  RFx number, title, label, validity end date, status, closing date

• Submit a Quick Quote response

  Build this

  Opens a Quick Quote from My Leads, selects Respond Online, fills in Response Information and each item's Unit Price, then selects Validate & Submit.

  Takes

  Opportunity number, unit price per item, response label, validity end date

  Returns

  Opportunity number, response total, submitted at, confirmation message

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

• New eVA orders, sent to your order desk

  Build this

  Starts

  Every weekday at 7:30

  Step 1

  Get the orders listed under Orders, Acknowledge Orders.

  Step 2

  Keep the orders that were not there on the last run.

  Step 3

  Post each order's ID, PO or PCO, buying entity, Bill To, items and total to your ERP webhook.

• Morning summary of new bid leads

  Build this

  Starts

  Every weekday at 8:00

  Step 1

  Get the opportunities in My Leads with their Info and Items tabs.

  Step 2

  Keep the opportunities that were not there on the last run.

  Step 3

  Group them by type and closing date and email you the summary.

• Draft responses still waiting to be submitted

  Build this

  Starts

  Every weekday at 14:00

  Step 1

  List the draft responses in progress under Manage RFx's.

  Step 2

  Stop when there are none.

  Step 3

  Email you each draft with its RFx number, title and closing date.

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 orders” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "supplier.cgieva.com/get_orders",
    "input": {
      "placed_since": "2026-11-09"
    }
  }'

{
  "status": "completed",
  "data": {
    "orders": [
      {
        "id": "PO-2026-118204",
        "order_type": "PO",
        "buying_entity": "Northwind County Public Schools",
        "bill_to": "Accounts Payable, 210 Main Street, Richmond, VA 23219",
        "items": "24 Each of Classroom chair, stackable",
        "total": 2856,
        "currency": "USD",
        "attachments": [
          "Delivery instructions.pdf"
        ]
      }
    ],
    "count": 1
  }
}

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.

EVA’s own options

eVA's supplier pages document no API. Every order is in your eVA supplier account, and an email notification goes to your ordering address. Suppliers configured to receive orders into their own system get them by cXML. Bids, quotes, catalogs and account changes are done in eVA itself.

Read on November 12, 2026: eVA Update: How to Access Your eVA Orders, eVA Supplier Training Materials, eVA Account Maintenance for Suppliers.

Signing in to eVA

eVA signs suppliers in at supplier.cgieva.com with a user name and password. Each contact on your account has their own login: you create the contact, eVA emails an invitation, and the contact sets a password and accepts the MOA the first time. With Fous you sign in once through eVA's own sign-in with your own account, and the login is sealed with AES-256.

Worth knowing

The email is not the whole order

The notification carries a copy of the order, but attachments and decrypted purchase card details are only in your eVA supplier account. Confirming orders send no email at all.

PCO or PO decides how you are paid

An ID starting with PCO is paid by the buyer's purchase card, shown under Delivery & Payment, Pcard details; ask the buyer for the CVV. A PO means you invoice the Bill To address on the order.

Payments do not run through eVA

For an unpaid invoice you contact the buying entity named in the Bill To details. eVA Customer Care does not process those payments. eVA sends you its own invoice under its fee schedule.

Some account changes need approval

Changes to your TIN, tax address, company name or organization type go through an Information Change Request to eVA Vendor Support. The Addresses and Qualifications tabs update without one.

More in Government: US state and local procurement

• PASSPort
• AASHTOWare Project Civil Rights & Labor
• BidNet Direct
• Bonfire
• OpenGov Procurement
• PlanetBids
• Cal eProcure
• COMMBUYS
• MyFloridaMarketPlace Vendor Information Portal
• NC eProcurement
• SFS Vendor Portal

Other industries: Maryland Tax Connect, GDOL Employer Portal, Airgas, e-staffing, ABC Order, HealthEquity employer portal.