Skip to content

FousmyCintas

Turn myCintas into an API

Read invoices from Pay, the wearers under Employee Uniforms and the products on My Services from myCintas with one API call each. A workflow can hand new invoices to accounts payable every morning and send you the week's wearer changes.

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

What you can build on myCintas

  • Get invoices for an account

    Build this

    Opens Pay, selects the account and reads its invoices for a From-To date range, with the amount of each and its PDF.

    Takes
    Sold To number, from date, to date
    Returns
    Account number, account name, invoice number, invoice date, amount, PDF link
  • List uniform wearers

    Build this

    Opens Manage, selects the account and reads every wearer under Employee Uniforms, with the open requests listed on each wearer's page.

    Takes
    Sold To number
    Returns
    Wearer name, open requests
  • Get facility services on an account

    Build this

    Reads the products on the account's My Services page: material number, description, service frequency and quantity.

    Takes
    Sold To number
    Returns
    Material number, description, frequency, quantity
  • Stop a uniform wearer

    Build this

    Finds a wearer under Employee Uniforms, chooses Stop Wearer and sends the change with Submit Request.

    Takes
    Sold To number, wearer name
    Returns
    Wearer name, request submitted, submitted at

Automate myCintas 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 Cintas invoices to accounts payable

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    For each Sold To number, get the invoices dated yesterday and today from Pay.
    Step 2
    Keep the invoices that were not there on the last run.
    Step 3
    Post account number, invoice number, date, amount and PDF link to your AP system's webhook.
  • Weekly uniform wearer changes for each account

    Build this
    Starts
    Every Monday at 7:00
    Step 1
    For each Sold To number, list the wearers under Employee Uniforms with their open requests.
    Step 2
    Keep the wearers who are new or gone since the last run, and the open requests that changed.
    Step 3
    Email you the changes, one section per account, to check against your staff list.
  • Monthly check of facility services products

    Build this
    Starts
    On the 1st of every month at 9:00
    Step 1
    For each Sold To number, get the products on My Services.
    Step 2
    Keep the products whose frequency or quantity changed since the last run, or that are new.
    Step 3
    Post material number, description, frequency and quantity 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 invoices for an account” 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": "account.cintas.com/get_invoices",
    "input": {
      "sold_to_number": "000123456789",
      "from_date": "2026-10-01",
      "to_date": "2026-11-11"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "account_number": "000123456789",
    "account_name": "ACME FABRICATION",
    "invoices": [
      {
        "invoice_number": "4180552301",
        "invoice_date": "2026-11-10",
        "amount": 412.38,
        "pdf_url": "https://account.cintas.com/online/..."
      }
    ]
  }
}

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.

MyCintas’s own options

Cintas does not publish an API or developer documentation for myCintas. Customers manage their program, shop, view and pay invoices and statements, and send requests in myCintas itself, where invoices can be downloaded as PDFs and paid automatically each month with AutoPay.

OptionWhat it coversWhat it takes
AutoPay in myCintasPays your invoices automatically each month from a payment method you save on the Pay page.A myCintas login and a saved payment method; you choose the autopay frequency.
Contact support in myCintasBilling Support for invoices, statements and payments; Service Support for wearers and service details; Website Support for sign-in.A message sent from the How can we help you? page in myCintas.
myCintas by handPay, Manage, TruCount and Shop: invoices and statements, wearers and requests, garment inventory reports and orders.A myCintas login; you select each Cintas account in turn on Pay and Manage.

Read on November 12, 2026: Cintas: log in to Cintas, myCintas: How can we help you?, myCintas Basics (Cintas guide published by a customer).

Signing in to myCintas

myCintas signs you in with an email address or user ID and a password, and the same login opens Shop Cintas, Training Central and LifeREADY. With Fous you sign in once through that page with your own account. The login is sealed with AES-256 and never shown to code or AI agents, and when the session expires Fous signs back in.

Worth knowing

Every task starts by choosing an account
Pay and Manage both ask you to select the account first, and a login can hold several Cintas accounts. Give each method the Sold To number, which is printed on your invoice.
Wearer changes are requests
Adding a wearer (Add Uniform Wearer) or stopping one (Stop Wearer) ends with Submit Request, and the employee's page lists open requests before you submit.
Fire protection bills are paid elsewhere
Cintas has fire protection bills paid through a separate Bill Pay, not through myCintas. Build invoice methods for those bills on that site.
TruCount reports live in their own section
Garment inventory reporting is viewed and downloaded under TruCount, a section of the home page apart from Manage and Pay.

More in Other industries

Other industries: Lowe's Vendor Gateway, Asda Supplier Portal, T-Mobile for Business Account Hub, Johnstone Supply, JAGGAER Supplier Network, Xero bank feeds.

Frequently asked questions

No. Cintas does not publish an API or developer documentation for myCintas. Invoices, statements and wearer requests are handled on the site, and AutoPay pays invoices each month from a payment method you save.

On the site you can download several at a time: search a From-To date range on the billing page and tick the invoices to download. A method you build can read that list for each account and return every invoice with its PDF link as JSON.

Each account is selected separately in Pay and Manage, by its Sold To number. A workflow can loop over your list of Sold To numbers and run the same method for each one.

Your Sold To or customer number and the Ship To ZIP or postal code, both printed on a Cintas invoice. Website Support helps with registration and forgotten usernames or passwords.

No. Fous is an independent product. It works through myCintas with your own account and reads and does only what that account can.

Put myCintas 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 nextBushelNLIS databaseFoodLogiQ ConnectLowe's Vendor GatewayHow methods workHow workflows run

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