Skip to content

FousRepairLink

Get your RepairLink Shop orders through an API

Read your Sent Orders with each dealer's status and notes, or a dealer's pricing and availability for a VIN, with one API call. A workflow can check Sent Orders through the day and post every dealer response to your repair order system.

Start building freeBook a demo

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

What you can build on RepairLink Shop

  • Get sent orders

    Build this

    Reads Sent Orders under Orders/Carts: each order's cart name, PO#, dealer, status, estimated delivery and the notes or responses from the dealer.

    Takes
    Sent since (optional), dealer (optional)
    Returns
    Cart name, PO#, dealer, sent date, status, estimated delivery, dealer notes, parts and quantities

  • Look up parts by VIN at a dealer

    Build this

    Selects the vehicle by VIN on the Automotive tab, picks the dealer in Select Dealer and searches by Keyword or Part Number for that dealer's pricing and availability.

    Takes
    VIN, part numbers or keyword, dealer
    Returns
    Vehicle, dealer, part number, description, price, availability, program or dealer discount, VIN recall alert

  • Get payment transaction history

    Build this

    Reads Transaction History under Payments: the charges to your payment method, filtered by Date Range, Dealer Name and Type (Sale or Return).

    Takes
    Date range, dealer name (optional), type (optional)
    Returns
    Date, dealer name, type, amount, dealer note, receipt link

  • Save a cart from a parts list

    Build this

    Adds part numbers in Add Parts to List for a VIN and dealer, sets quantities, Cart Name, PO# and a Note, and clicks Save Cart without ordering.

    Takes
    VIN, dealer, part numbers and quantities, cart name, PO#, note (optional)
    Returns
    Cart name, dealer, parts, quantities, prices, availability, cart total

Automate RepairLink Shop 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.

  • Dealer responses on sent orders, into your repair orders

    Build this
    Starts
    Every 30 minutes
    Step 1
    Get the sent orders from the last 14 days.
    Step 2
    Keep the orders whose status, estimated delivery or dealer notes changed since the last run.
    Step 3
    Post each one, with PO#, dealer, status, estimated delivery and notes, to your shop system's webhook.

  • Weekly payment transactions, handed to accounting

    Build this
    Starts
    Every Monday at 7:00
    Step 1
    Get the payment transaction history for the previous 7 days.
    Step 2
    Group the sales and returns by dealer name.
    Step 3
    Email you the totals per dealer and post every transaction to your accounting webhook.

  • Dealer pricing for a repair order's parts

    Build this
    Starts
    When your system calls the workflow's webhook with a VIN, a dealer and part numbers
    Step 1
    Look up each part number for the VIN at the dealer your system names.
    Step 2
    Mark the parts the dealer has no availability for.
    Step 3
    Post the prices, availability, discounts and any recall alert back to your 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 sent 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": "www.repairlinkshop.com/get_sent_orders",
    "input": {
      "sent_since": "2026-11-09"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "orders": [
      {
        "cart_name": "2019 Ford F-150 front brakes",
        "po_number": "RO-4471",
        "dealer": "Northwind Ford",
        "sent_date": "2026-11-11",
        "status": "New",
        "estimated_delivery": null,
        "dealer_notes": null,
        "parts": "1 x PN-48211"
      }
    ],
    "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.

RepairLink Shop’s own options

RepairLink Shop is free for repair shops, and OEC documents no API for them. Its automation is an integration with shop management programs, which retrieve pricing and submit orders from inside that software, plus email or text notifications of dealer responses and a CSV export of payment transactions.

OptionWhat it coversWhat it takes
Shop management software integrationPricing and order submission from inside Mitchell 1, NAPA TRACS, Protractor, R.O. Writer, Shop Boss, Shopmonkey, Shop-Ware, Tekmetric or VIP Shop Management.One of those programs, set up with your RepairLink Shop account.
Manage NotificationsEmail to one or two addresses, and text to up to two mobile phones, when a dealer sends a new note, a new photo or a response.The shop's RepairLink Shop administrator sets it up under Account Management.
Transaction History exportExports the charges to your payment method as a CSV file, filtered by date range, dealer name and type.A payment method stored with Payments Powered by OEC.
RepairLink Shop by handVIN parts lookup, dealer pricing and availability, carts, orders, and Sent Orders with status and dealer notes.A free shop account and at least one dealer added to your dealer list.

Read on November 12, 2026: Using Shop Management Software With RepairLink Shop, Setting Up Text/Email Notifications in RepairLink Shop, RepairLink Shop product page.

Signing in to RepairLink Shop

RepairLink Shop asks for a username and password, and can remember the username. Each user has personal credentials that the shop's administrator creates, and the administrator can switch a user's right to submit orders off. With Fous you sign in once through RepairLink Shop'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

Sent orders are kept for 60 days
Sent orders and saved carts stay on the Orders/Carts management window for up to 60 days, then are removed. To keep a longer history, a workflow can post each order to your own system as it changes.
One administrator, per-user ordering rights
A shop has one administrator, who sees every saved cart while users see only their own. A user whose Submit orders toggle is Off can still save carts, so a method only does what that user may.
Cart limits and no returns
A cart holds at most 100 unique part lines and 999 of one SKU, and an uploaded list holds up to 25 parts. Returns cannot be processed in RepairLink Shop, and Canada-only models are not available.
VIN recall alerts are refreshed every 30 days
Recall alerts cover GM and Ford in the U.S. and Canada and Mercedes-Benz in the U.S., following the shop's country. They refresh every 30 days, so a recall already done may still show.

More in Automotive: aftermarket and fleet

Other industries: USS CIS, Paycom, United Rentals Total Control, IndiaMART Seller Panel, 千牛卖家中心, UCAS adviser portal.

Frequently asked questions

Not for repair shops: OEC documents no API for them. Shop management programs such as Mitchell 1, Tekmetric and Shopmonkey integrate with RepairLink Shop to retrieve pricing and submit orders, and the site itself offers dealer-response notifications and a CSV export of payment transactions.

Under Orders/Carts, then Sent Orders. That is where RepairLink Shop shows status updates, estimated delivery times and notes or responses from your dealer. A new order starts with the Status New.

Yes. In the shopping cart, Choose File imports a list of parts from a .CSV or TXT file, up to 25 parts, and Add Parts to List adds one part number at a time.

Sent orders and saved carts older than 60 days are removed automatically. To keep them, copy them into your own system before then, for example with a workflow that posts each order to your webhook as it changes.

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

Put RepairLink 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.

Start building freeBook a demo

Read nextpartslink24PartsTechSilverDATUSS CISHow methods workHow workflows run

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