Skip to content

FousSRS Roof Hub

Turn SRS Roof Hub into an API

Read your open orders, Delivery Cockpit statuses and invoices from SRS Roof Hub with one API call each. Or have a workflow check tomorrow's deliveries every afternoon and send each new invoice with its P.O.# to your accounting.

Works with your own SRS Roof Hub account. Fous is an independent product.

What you can build on Roof Hub

  • Get open orders

    Build this

    Reads your open orders on the Orders page, with each order's requested ship date, P.O.#, job name, delivery address and status.

    Takes
    Date range (optional), status (optional)
    Returns
    Order number, requested ship date, delivery address, P.O.#, job name, status
  • Track deliveries

    Build this

    Reads the Delivery Cockpit: each open delivery's status bar (En-Route, Being Delivered, Delivered), its estimated time of arrival and whether delivery photos are there.

    Takes
    Order number (optional)
    Returns
    Order number, delivery address, delivery status, ETA, delivered at, delivery photos available
  • Get invoices

    Build this

    Reads the Invoices page for a date range: each invoice's number, date, P.O.#, total and payment status.

    Takes
    Date range
    Returns
    Invoice number, invoice date, delivery address, P.O.#, total, payment status
  • Place an order from a template

    Build this

    Starts Create New Order, picks the branch and Job Account, fills the items from one of your order templates, sets delivery or pickup, P.O.# and Job Name, then places it.

    Takes
    Branch, job account, template name, requested ship date, delivery or pickup, P.O.#, job name
    Returns
    Order number, branch, P.O.#, requested ship date, status

Automate Roof Hub 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.

  • Tomorrow's deliveries, checked before the crews go out

    Build this
    Starts
    Every weekday at 16:00
    Step 1
    Get open orders with a requested ship date of tomorrow.
    Step 2
    Track deliveries for those orders to read each one's current status.
    Step 3
    Email you the list by job name, with P.O.#, delivery address and status.
  • Delivered orders, posted to your job management system

    Build this
    Starts
    Every weekday at 18:00
    Step 1
    Track deliveries and keep those with the Delivered status.
    Step 2
    Keep the deliveries that were not Delivered on the last run.
    Step 3
    Post order number, job name, P.O.# and delivered time to your webhook.
  • New invoices, handed to accounting

    Build this
    Starts
    Every Monday at 8:00
    Step 1
    Get invoices dated in the last 7 days.
    Step 2
    Keep the invoices that were not there on the last run.
    Step 3
    Post invoice number, P.O.#, total and payment status to your accounting system's 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 open orders” 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": "roofhub.pro/get_open_orders",
    "input": {
      "from": "2026-11-10",
      "to": "2026-11-20"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "orders": [
      {
        "order_number": "000418273",
        "requested_ship_date": "2026-11-13",
        "delivery_address": "1200 Globex Way, Plano, TX 75024",
        "po_number": "ACME-2291",
        "job_name": "Globex warehouse reroof",
        "status": "Ordered"
      }
    ],
    "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.

Roof Hub’s own options

SRS publishes an API, SRS Integration Partner Services (SIPS), designed for CRM and software partners. It covers orders, deliveries, invoices, pricing and order submission, and SRS reviews each integration in a demo before issuing production credentials. Contractors otherwise use Roof Hub or a connected tool.

OptionWhat it coversWhat it takes
SIPS APIOrder and delivery lists, proof of delivery, invoices and invoice PDFs, customer pricing, catalog, order templates, order submission and webhooks.For CRM and software partners: credentials from SRS API Support, production access after a demo and SRS's approval.
Connected toolsRoof Hub works with project management tools such as AccuLynx, JobNimbus, Leap and GiddyUp.An account with that tool.
Roof Hub by handOrders, the Delivery Cockpit, Invoices with proof-of-delivery photos and invoice PDFs, and live pricing at nearby branches, on the web or the app.A free Roof Hub account, registered with your SRS account number and an SRS invoice.

Read on November 12, 2026: SRS API documentation, SRS API FAQs, Roof Hub.

Signing in to Roof Hub

Roof Hub signs you in with your email address and password, with Remember Me and Forgot Password on the same screen. Each user has their own login, and an Owner or Executive manages the company's users. With Fous you sign in once through Roof Hub'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

Abilities decide what a user sees
An Owner or Executive sets each user's Abilities. If Pricing is turned off for a user, prices are not shown to them, so a method sees prices only when its account may.
Accounts payable needs Trends access
The Accounts Payable panel on the Invoices page is visible only to users with Trends access in their profile. Paying invoices goes through a link to Billtrust, which does not sign you in automatically.
A TBD ship date reads as 12/31/2049
When an order is placed with a TBD ship date, Roof Hub fills in 12/31/2049. Filter it out before treating requested ship dates as real ones.
Job accounts follow the branch
Create New Order lists only the Job Accounts (ship-tos) eligible for the shipping branch, and defaults to the branch closest to the job. Pick the branch first.

More in Trades, field service and facilities

Other industries: BtoBプラットフォーム 請求書, Lexware Office, Walmart Connect Ad Center, partslink24, vAuto Provision, Paylocity.

Frequently asked questions

SRS has one, written for CRM and software partners. SIPS covers orders, deliveries, invoices, pricing and order submission, and SRS approves each integration after a demo. As a contractor you use Roof Hub itself, or a connected tool such as AccuLynx or JobNimbus.

Yes. Each row on the Invoices page has a photo icon for the proof of delivery and a PDF icon for the invoice. Delivered orders in the Delivery Cockpit also carry the delivery photos.

Choose Register at roofhub.pro or in the app and look up your account with your SRS account number, an invoice number and its invoice date. All three are printed on any SRS invoice.

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

Put SRS Roof Hub 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 nextGC ONLINE PLUSEnphase Installer PlatformBunnings PowerPassBtoBプラットフォーム 請求書How methods workHow workflows run

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