Get your Procore RFIs, submittals and invoices by API

What you can build on Procore

• Get RFIs in your Ball In Court

  Build this

  Reads the RFIs log of one project, filtered on Ball In Court, with each RFI's status, due date and impacts.

  Takes

  Project, Ball In Court (optional), status (optional)

  Returns

  RFI number, subject, status, responsible contractor, RFI Manager, date initiated, due date, ball in court, schedule impact, cost impact

• Get submittals waiting for your response

  Build this

  Reads the Submittals log of one project, filtered on Ball In Court, with each submittal's spec section, type, submit-by and due dates.

  Takes

  Project, Ball In Court (optional), status (optional)

  Returns

  Spec section, submittal number, title, type, status, responsible contractor, submit by, received date, due date

• Check subcontractor invoice statuses

  Build this

  Reads the Subcontractor tab of the project's Invoicing tool for your contracts, with each invoice's billing period, invoice status and payment status.

  Takes

  Project, billing period (optional)

  Returns

  Invoice number, contract, billing period, invoice status, payment status, amount this period

• Respond to an RFI

  Build this

  Opens one RFI in the project's RFIs tool, adds a response in the Responses card on the General tab and saves it.

  Takes

  Project, RFI number, response text

  Returns

  RFI number, subject, response added at, ball in court

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

• RFIs in your Ball In Court, every project

  Build this

  Starts

  Every weekday at 7:00

  Step 1

  For each project you name, get the RFIs with you in the Ball In Court.

  Step 2

  Keep the RFIs that were not there on the last run, or whose due date is today or past.

  Step 3

  Email you the list, one section per project, with subject and due date.

• Submittals due this week, grouped by project

  Build this

  Starts

  Every Monday at 7:00

  Step 1

  For each project, get the submittals with you in the Ball In Court.

  Step 2

  Keep the ones with a submit by or due date in the next 7 days.

  Step 3

  Email you the list, grouped by project and spec section.

• Invoice status changes, posted to your accounting system

  Build this

  Starts

  Every weekday at 17:00

  Step 1

  For each project, check the subcontractor invoice statuses for the current billing period.

  Step 2

  Keep the invoices whose invoice status or payment status changed since the last run.

  Step 3

  Post invoice number, project, billing period and both statuses 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 RFIs in your Ball In Court” would look like.

curl https://api.fous.com/v1/runs \
  -H "Authorization: Bearer $FOUS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "method": "login.procore.com/get_rfis_in_ball_in_court",
    "input": {
      "project": "Northwind Medical Office Building",
      "status": "Open"
    }
  }'

{
  "status": "completed",
  "data": {
    "project": "Northwind Medical Office Building",
    "rfis": [
      {
        "number": "112",
        "subject": "Duct routing conflict at level 3 corridor",
        "status": "Open",
        "responsible_contractor": "Acme Mechanical",
        "rfi_manager": "Globex Builders project engineer",
        "date_initiated": "2026-11-06",
        "due_date": "2026-11-13",
        "ball_in_court": "Acme Mechanical",
        "schedule_impact": "TBD",
        "cost_impact": "No"
      }
    ],
    "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.

Procore’s own options

Procore has an API used through apps that an admin installs into a company's Procore account. An app that acts for a signed-in user sees the same projects and information as that person, and a service-account app gets the permissions an administrator approves. By hand, RFIs can also be answered by replying to the RFI email.

Read on November 12, 2026: How do integrations with Procore access my company's data?, Respond to an RFI, Invoicing tool user guide.

Signing in to Procore

Procore's sign-in at login.procore.com asks for your email address, then your password. Where MFA is turned on, it adds a code from an authenticator app or SMS, asked again every 7 days, or every 12 hours for Procore Pay users. With Fous you sign in through Procore's own sign-in with your own account. The login is sealed with AES-256, and your code and AI agents never see it.

Worth knowing

Invoices need an invoice contact and a period

Only invoice administrators or invoice contacts on a commitment can create subcontractor invoices. The commitment must be Approved, and the invoice goes in before the Open billing period's Due Date.

A sent invoice is locked

Send sets an invoice to Under Review. After that an invoice contact cannot edit it unless an invoice administrator sets it to Revise & Resubmit.

Ball In Court moves only on a response

An RFI stays in your Ball In Court until you submit a response. On a submittal, the Ball In Court moves to the next workflow step only when every required user in the current step has responded.

MFA asks again on a fixed interval

Where MFA is on, Procore asks for the code again every 7 days, every 12 hours for Procore Pay users, and after a logout for inactivity. It is mandatory for Procore Pay users.

More in Construction

• BuildingConnected
• LCPtracker
• Autodesk Build
• SOKA-BAU Online-Service
• United Rentals Total Control
• Hyphen SupplyPro
• Trimble Unity Construct
• GCPay
• Oracle Textura Payment Management
• Payapps

Other industries: IndiaMART Seller Panel, Meesho Supplier Panel, Common App for Recommenders, CenterPoint Energy My Account, myCoke, Absa Access.