Skip to content

Fous1link Service Network

Get your 1link jobsheets and invoices through an API

Read your 1link jobsheets, fleet authorisations and queries, incoming service bookings and the jobs still showing payment not requested, with one API call each. A workflow can check each morning for authorised jobs not yet invoiced and email you the list.

Works with your own 1link Service Network account. Fous is an independent product.

What you can build on 1link

  • Get jobs with payment not requested

    Build this

    Opens payment not requested on the 1link homepage and reads the list of jobs that have not yet been invoiced through 1link.

    Takes
    Fleet (optional)
    Returns
    Job reference, fleet, vehicle registration, authorised date, authorised amount, status
  • Check jobsheet authorisations and queries

    Build this

    Reads your submitted jobsheets and what each fleet operator replied: authorised, queried or still waiting, with the query text.

    Takes
    Submitted since (optional), fleet (optional)
    Returns
    Jobsheet reference, fleet, vehicle registration, status, authorised amount, query text, last updated
  • Get new service bookings from fleets

    Build this

    Reads the service bookings that fleet operators and their drivers have sent to your site in 1link.

    Takes
    From date, to date
    Returns
    Booking date and time, fleet, vehicle registration, work requested, booking status
  • Raise an invoice for an authorised job

    Build this

    Opens an authorised job in 1link, raises the invoice against the approved job details and submits it, so the job moves to Invoiced.

    Takes
    Job reference, invoice number, invoice date
    Returns
    Job reference, invoice number, invoiced amount, status

Automate 1link 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.

  • Authorised jobs not yet invoiced, every morning

    Build this
    Starts
    Every weekday at 8:00
    Step 1
    Get the jobs listed under payment not requested.
    Step 2
    Keep the jobs whose authorised date is more than 20 days ago, before the authorisation can lapse.
    Step 3
    Email you the list, grouped by fleet.
  • New fleet queries on jobsheets, to the workshop

    Build this
    Starts
    Every 30 minutes
    Step 1
    Check jobsheet authorisations and queries submitted in the last 7 days.
    Step 2
    Keep the jobsheets that were queried and were not queried on the last run.
    Step 3
    Post each one, with fleet, vehicle registration and query text, to your Slack or DMS webhook.
  • New service bookings, into your workshop diary

    Build this
    Starts
    Every 15 minutes
    Step 1
    Get the service bookings from fleets for the next 14 days.
    Step 2
    Keep the bookings that were not there on the last run.
    Step 3
    Post each booking to your DMS or diary 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 jobs with payment not requested” 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": "1link.co.uk/get_jobs_payment_not_requested",
    "input": {
      "fleet": "Acme Leasing"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "jobs": [
      {
        "job_reference": "SN-48213",
        "fleet": "Acme Leasing",
        "vehicle_registration": "AB21 XYZ",
        "authorised_date": "2026-10-19",
        "authorised_amount": 412.6,
        "currency": "GBP",
        "status": "Authorised"
      }
    ],
    "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.

1link’s own options

Since March 2025 epyx offers garage users a free Authorisation and Invoice Interface that moves jobs and invoices between your dealer management system and 1link, so you can submit, gain authorisation and invoice without rekeying. It works only once your DMS provider has built its side. The APIs epyx lists for driver booking are a paid service for fleet operators.

OptionWhat it coversWhat it takes
Authorisation and Invoice InterfaceCreate, submit, gain authorisation and invoice for jobs from your DMS without rekeying them into 1link.Free for garage users. Your DMS provider must build a further interface to it.
Driver booking and APIs (fleet side)A value-added service for fleet operators, listed under booking.Additional fees, arranged through the fleet's epyx account manager.
1link Service Network by handService bookings from fleets, jobsheets built online, fleet authorisations and queries, downtime updates and invoicing.A garage account on 1link Service Network.

Read on November 12, 2026: Interface now available for garages, 1link Service Network for garages, 1link Service Network for fleets.

Signing in to 1link

Garages sign in to 1link Service Network at www.1link.co.uk, where the Sign in link on epyx's site leads. With Fous you sign in once through 1link's own sign-in with your own account: the login is sealed with AES-256, code and AI agents never see it, and an expired session is signed back in.

Worth knowing

Only invoices raised in 1link get paid
Fleet operators can only pay invoices created within 1link Service Network. An invoice raised only in your DMS cannot be matched to the job authorisation, so it is not paid.
Authorisations expire
An authorisation typically expires after 30 days, though this varies by fleet. Invoice before then and you avoid asking the fleet to authorise the job again.
Invoiced means the status says Invoiced
A job is not invoiced until its status changes to Invoiced. Payment not requested on the homepage shows in red while jobs are still waiting to be invoiced through 1link.
The interface depends on your DMS
The free Authorisation and Invoice Interface works only when your DMS provider has built its side of it. epyx says a few DMS companies already provide this.

More in Automotive: aftermarket and fleet

Other industries: OPENLANE, Workday, LCPtracker, SanMar, Walmart Seller Center, EDOF.

Frequently asked questions

Not a public one for garages. epyx offers garage users a free Authorisation and Invoice Interface that links 1link to your dealer management system, once your DMS provider has built its side. The booking APIs epyx lists are a paid service for fleet operators. Otherwise you use 1link by hand.

Often because the invoice was raised in the DMS and not in 1link. Fleets can only pay invoices created in 1link Service Network. Check payment not requested on the homepage: jobs listed there have not been invoiced through 1link, and a job counts as invoiced only when its status is Invoiced.

Typically 30 days, though it varies by fleet. Once it expires you have to ask the fleet to authorise the job again, so invoice authorised jobs promptly.

Yes, with a workflow you build in Fous. It can run every 15 or 30 minutes, read your bookings and jobsheet queries in 1link, keep what was not there on the last run and email you or post it to your own system by webhook.

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

Put 1link Service Network 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 nextDecisiv SRMWORLDPAC speedDIALCollisionLinkOPENLANEHow methods workHow workflows run

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