Skip to content

FousQapter

Get your Qapter estimates into your own systems

Read an estimate's Checkliste, its Gesamtbetrag and Teilesuche results from Qapter with one API call each. A workflow can read each estimate your claims system names and post its positions, repair costs and vehicle value back to that system.

Start building freeBook a demo

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

What you can build on Qapter

  • Get an estimate's Checkliste

    Build this

    Reads the Checkliste (checklist) of one estimate: each position under its Leitnummer (guide number) and each AV (Ausführungsvariante, equipment variant) taken in.

    Takes
    Estimate reference
    Returns
    Leitnummer, description, repair method, part number, price, labour units, mutation flag, selected AVs

  • Get an estimate's total and total-loss figure

    Build this

    Reads the Gesamtbetrag (total) panel of one estimate: repair costs, vehicle value and where the total-loss bar stands against its thresholds.

    Takes
    Estimate reference
    Returns
    Total excluding VAT, repair costs, vehicle value, total-loss percentage, bar colour, warning and alarm thresholds

  • Find a part with Teilesuche

    Build this

    Searches Teilesuche (parts search) in an open estimate by Leitnummer, description or part number and reads the results.

    Takes
    Estimate reference, Leitnummer, description or part number
    Returns
    Leitnummer, description, part number, plausible flag, and model and subtype for a part-number search

  • Add a non-standard position to an estimate

    Build this

    Opens Neue Position hinzufügen (add new position), fills the NSP Manuelle Eing. (manual entry) tab with the position you give and adds it to the calculation.

    Takes
    Estimate reference, repair method, description, part number, optional labour units, price, comment and mandatory AVs
    Returns
    Leitnummer, description, repair method, price, new estimate total

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

  • Estimate lines handed to your claims or shop system

    Build this
    Starts
    When your system calls the workflow's webhook with an estimate reference
    Step 1
    Get the estimate's Checkliste: every position and the selected AVs.
    Step 2
    Get the estimate's Gesamtbetrag with repair costs and vehicle value.
    Step 3
    Post the positions and totals as one JSON record to your system's webhook.

  • Estimates near a total loss, flagged for review

    Build this
    Starts
    Every weekday at 16:00
    Step 1
    For each estimate reference you list, get the Gesamtbetrag and the total-loss figure.
    Step 2
    Keep the estimates whose total-loss bar is yellow or red.
    Step 3
    Email you the list with total, vehicle value and percentage.

  • Estimate lines changed since the last run

    Build this
    Starts
    Every weekday at 7:30
    Step 1
    For each open estimate you list, get the Checkliste.
    Step 2
    Keep the positions added or changed since the last run.
    Step 3
    Post them, with the estimate reference, to your Slack or claims system 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 an estimate's Checkliste” 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": "audatexsolutions.com/get_estimate_checklist",
    "input": {
      "estimate": "ACME-2026-0412"
    }
  }'
Example response
{
  "status": "completed",
  "data": {
    "estimate": "ACME-2026-0412",
    "positions": [
      {
        "leitnummer": "0471",
        "description": "Front bumper cover",
        "repair_method": "E",
        "part_number": "NW-0807221-A",
        "price": 412.6,
        "labour_units": 18,
        "mutation": false
      }
    ],
    "selected_avs": [
      "Parking sensors front"
    ],
    "currency": "EUR",
    "count": 2
  }
}

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.

Qapter’s own options

Solera has an API address, na.api.solera.com, but it opens on a sign-in for an Audatex User ID and password and does not describe publicly what it covers. In Qapter itself you read and print the Checkliste and the Gesamtbetrag on screen, one estimate at a time.

OptionWhat it coversWhat it takes
Solera's API sitena.api.solera.com, a sign-in page titled Solera | Audatex. What it covers is not described publicly.An Audatex User ID and password.
Qapter by handThe Checkliste of positions and AVs, which you can filter and print, the Gesamtbetrag, Bildansicht (photo view) and Teilesuche, per estimate.An Audatex account with Qapter. In Germany, Qapter opens from AudaExpertWeb or AudaFusionWeb.

Read on November 12, 2026: Solera API sign-in, Anleitung: Qapter Online (Audatex Germany), Audatex Authentication Central.

Signing in to Qapter

In North America, Qapter users sign in at Audatex Authentication Central with a Username and Password, or with Sign In with Company. With Fous you sign in once through that sign-in with your own account. The login is sealed with AES-256 and code and AI agents never see it. When a Username and Password session expires, it is signed back in.

Worth knowing

Labels here come from the German guide
Audatex Germany's published guide names the screens Checkliste, Gesamtbetrag, Teilesuche and Bildansicht. Qapter opens there from AudaExpertWeb or AudaFusionWeb, and your country's edition may word its labels differently.
Mandatory AVs come first
If mandatory AVs are missing when Qapter starts, or later while damage is being entered, a pop-up asks you to add them. A method that adds positions needs those AVs among its inputs.
Totals exclude VAT by default
The current total is shown in EUR with decimals and without VAT by default. The total-loss bar turns yellow at the warning threshold, 80 % by default, and red at the alarm threshold, 100 % by default.
Three fields are required for an NSP
A non-standard position needs a repair method, a description (Bezeichnung) and a part number. The Leitnummer can be assigned automatically, and labour units, price and comment are optional.

More in Automotive: aftermarket and fleet

Other industries: RouteOne, Silae, GCPay, FTD Mercury, 千牛卖家中心, VA Enrollment Manager.

Frequently asked questions

Not one with public documentation. Solera has an API address, na.api.solera.com, but it opens on a sign-in for an Audatex User ID and password and does not describe publicly what it covers. In Qapter itself you read each estimate on screen.

Yes, it is on the Gesamtbetrag panel. Its detail shows the repair costs and the vehicle value, and a bar compares the total with the vehicle value, turning yellow at 80 % and red at 100 % by default. A method can read those figures for each estimate.

In North America, at Audatex Authentication Central (audatexsolutions.com), which names Qapter on its sign-in page. The claims.solera.com Login page links there under Audatex, beside APU Solutions, HyperQuest and LYNX Services.

On screen, the Checkliste lists every position and AV in the estimate, and you can filter it and print it. With Fous, a method you build can read the same list and return it as JSON for your own system.

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

Put Qapter 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 nextMitchell Cloud EstimatingPartsTraderAuto IntegrateRouteOneHow methods workHow workflows run

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