Developers

Price list API

Fetch a repair shop's price list as JSON for the shop's website. The address, fields, price rules, caching and what to do on every response.

Updated

Questions about the API? Email support@repairflow.eu.

What it is

A repair shop that uses Repairflow can publish its price list as JSON. The shop’s website fetches that list and shows brands, devices, repairs and prices with it, with a link on each repair to book online straight away. The list is public and needs no key, but only if the shop switches it on itself.

The API is rolled out shop by shop. A shop switches it on under Settings, Integrations, in the group On your own website, on the Price list API tile. That tile will appear for all shops soon. As long as a shop has not switched it on, its URL answers with a 404 and the code PRICE_LIST_NOT_FOUND. While Repairflow has the API paused, every URL answers with a 503 and the code PUBLIC_API_PAUSED, including the URL of a shop that has switched it on (see the table under What to do on each response).

The address

There is one URL per shop, without query parameters:

GET https://api.repairflow.eu/api/v1/shops/{slug}/price-list

The slug is the shop name in the shop’s booking link, the part after /ssp/. The tile in Repairflow shows the full URL with a button to copy it.

Everything under /api/v1/ is documented and versioned. Other Repairflow paths are internal and not meant to be used.

Example response

{
  "version": 1,
  "shop": { "slug": "voorbeeld-reparatie", "name": "Voorbeeld Reparatie", "bookingUrl": "https://my.repairflow.eu/ssp/voorbeeld-reparatie" },
  "currency": "EUR",
  "pricesIncludeVat": true,
  "disclaimer": { "nl": "Prijzen zijn inclusief btw en arbeid.", "en": null },
  "updatedAt": "2026-11-14T09:12:41.000Z",
  "brands": [
    {
      "name": "Apple",
      "devices": [
        {
          "id": "6650c1f2a9e3b40012ab34cd",
          "slug": "apple-iphone-15",
          "model": "iPhone 15",
          "series": "iPhone 15",
          "bookingUrl": "https://my.repairflow.eu/ssp/voorbeeld-reparatie?device=6650c1f2a9e3b40012ab34cd",
          "repairs": [
            {
              "id": "6650c1f2a9e3b40012ab34ce",
              "slug": "scherm-vervangen",
              "name": "Scherm vervangen",
              "description": "Inclusief nieuwe glasfolie",
              "price": { "type": "from", "amount": 149.0 },
              "options": [
                { "id": "6650c1f2a9e3b40012ab34d1", "label": "Kopie", "price": { "type": "fixed", "amount": 149.0 },
                  "bookingUrl": "https://my.repairflow.eu/ssp/voorbeeld-reparatie?device=6650c1f2a9e3b40012ab34cd&repair=6650c1f2a9e3b40012ab34ce&option=6650c1f2a9e3b40012ab34d1" },
                { "id": "6650c1f2a9e3b40012ab34d2", "label": "Origineel", "price": { "type": "fixed", "amount": 229.0 },
                  "bookingUrl": "https://my.repairflow.eu/ssp/voorbeeld-reparatie?device=6650c1f2a9e3b40012ab34cd&repair=6650c1f2a9e3b40012ab34ce&option=6650c1f2a9e3b40012ab34d2" }
              ],
              "bookingUrl": "https://my.repairflow.eu/ssp/voorbeeld-reparatie?device=6650c1f2a9e3b40012ab34cd&repair=6650c1f2a9e3b40012ab34ce"
            },
            {
              "id": "6650c1f2a9e3b40012ab34d0",
              "slug": "waterschade-onderzoek",
              "name": "Waterschade-onderzoek",
              "description": "",
              "price": { "type": "on_request", "amount": null },
              "options": [],
              "bookingUrl": "https://my.repairflow.eu/ssp/voorbeeld-reparatie?device=6650c1f2a9e3b40012ab34cd&repair=6650c1f2a9e3b40012ab34d0"
            }
          ]
        }
      ]
    }
  ],
  "services": [
    {
      "id": "6650c1f2a9e3b40012ab3500",
      "slug": "computerservice",
      "name": "Computerservice",
      "bookingUrl": "https://my.repairflow.eu/ssp/voorbeeld-reparatie?device=6650c1f2a9e3b40012ab3500",
      "repairs": []
    }
  ]
}

The fields

  • version is the version number of the contract, currently 1.
  • currency is the shop’s currency, EUR by default. pricesIncludeVat is true: all amounts include VAT.
  • disclaimer is the shop’s own text, copied literally, per language. An empty field is null. When both languages are empty, the whole object is null. Show the text next to the prices when it is there.
  • brands holds brands with their devices. A device’s series can be null.
  • services holds service groups, such as computer service. They are built like a device, but with name instead of model and without series.
  • options is always an array, empty when a repair has no quality options.
  • Brands, devices and services without active repairs are left out. Inactive items are never included.
  • The order is that of the shop’s booking page.
  • The list deliberately holds no stock, availability, purchase prices or margins. What is not here cannot be fetched.

Prices

price.type is an outcome, not a setting of the shop. There are three values:

Type Amount Meaning
fixed number, for example 149.0 A concrete amount, including VAT. The list does not reveal how the price was built.
from number Only on a repair with quality options: the lowest fixed amount of its options.
on_request null The shop names no price. Show something like Price on request.

A repair with options is from as soon as at least one option has a fixed amount, and on_request otherwise. The options themselves are fixed or on_request. A price can also be on_request because the shop does not publish prices in its booking settings, and sometimes for other reasons the list does not name. Assume that a price can become on_request and can get an amount later. Amounts have at most two decimals.

id, slug and name

Every device, service group and repair has an id and a slug. Options only have an id. Brands have neither.

  • id never changes. Store it if you want to recognise an item.
  • slug is fixed at first publication and never changes afterwards, not even when the shop renames the item. Use it in your own URL, for example exampleshop.com/repair/apple-iphone-15/. A device slug is made of brand and model, a repair slug of the repair name, and is unique within its device. When two names are equal, the second gets a -2.
  • model, series, name, label and description are the texts to display. They can change, so do not build a URL on them.

This is how you build stable pages: show model and name, use slug in the path and store id as your key.

Make a device or repair inactive instead of deleting it. An inactive item disappears from the list but keeps its slug: when you switch it on again later, the URL on your website works again. When a device is deleted and created again, it gets a new slug and the URL on your website changes. Point this out to the shop too, because a shop can delete a device itself. A typo in a slug is corrected by hand on request. For your site that is a break in the URL.

Booking from your website

bookingUrl is on the shop, on every device and service group, on every repair and on every option. It is a link to the shop’s booking page with the choice already set up:

  • ?device=<id> opens the device.
  • &repair=<id> sets up the repair.
  • &option=<id> also sets up the chosen quality option.

For a repair with options, the link of the repair opens the device without a tick, and the customer picks an option. To set up a choice straight away, use the bookingUrl of the option. A link with a device that no longer exists or is inactive opens the booking page at the first step. A repair or option that no longer exists opens the device without a tick. Use the bookingUrl from the list as it is and do not rebuild it yourself.

When the shop has Online booking switched off, bookingUrl is null everywhere. The prices are still in the list then.

Fetching, caching and ETag

  • The list is public and needs no key or cookie. You can fetch it on the server side and also from the browser: CORS allows any origin (Access-Control-Allow-Origin: *, GET and HEAD only) and the ETag is readable. No cookies or other credentials are sent. Which way suits your site is under Static sites, browsers and rate limits.
  • A 200 and a 304 have Cache-Control: public, max-age=60. Repairflow’s server can also keep the list itself for up to about 60 seconds. A change by the shop is therefore visible within about two minutes for a client that follows this caching. When the shop switches the list off or Repairflow pauses the API, that applies straight away to every new request.
  • The body is compressed (gzip) when you send Accept-Encoding: gzip. Every common HTTP client does that by itself.
  • A 200 and a 304 also have a weak ETag, such as W/"3f9a1c0b7d2e4a58". The ETag depends only on what the list shows. Send it back in If-None-Match: when nothing changed you get a 304 without a body. That is the cheapest way to check. Use the ETag only to see whether the list stayed the same. It says nothing about which version is newer, so do not compare or sort ETags.
  • The response has X-Robots-Tag: noindex. The JSON itself does not belong in search engines, your pages do.
  • Ignore unknown fields. In version 1, fields can be added.

What updatedAt means

updatedAt is the moment Repairflow first delivered the changed list. The change itself happened before that, after the previous delivery. So updatedAt is not the exact moment of the change, and not the moment you last fetched either.

It changes on every change to what the list shows: a price, a name, a new repair, the VAT rate, the disclaimer, Online booking on or off. A change that alters nothing in the list leaves updatedAt and the ETag alone. A response always carries the updatedAt and the ETag of the list in it.

updatedAt is not guaranteed to increase between two responses. Repairflow can deliver the list from more than one server, each with its own cache. In the first minute after a change, a client can therefore get the previous and the new version in turn, and so an earlier updatedAt again. Use updatedAt to show when the list last changed. To know whether something changed, use the ETag.

What to do on each response

Response What it means What you do
200 The list. Use it and store it with its ETag.
304 Nothing changed since your ETag. Keep your copy.
404 with code: PRICE_LIST_NOT_FOUND The shop does not (or no longer) publish, or the slug is wrong. Remove the prices from your site.
404 with code: NOT_FOUND The path under /api/v1/ does not exist. Check your URL and keep your copy.
400 with code: BAD_REQUEST or 413 with code: REQUEST_TOO_LARGE Your request had a body. Send a plain GET without a body and keep your copy.
429 with code: PRICE_LIST_RATE_LIMITED You fetch too often. Keep your last good copy and try again later. Follow Retry-After.
503 with code: PUBLIC_API_PAUSED Temporarily unavailable. Keep your last good copy and try again later, after Retry-After.
Any other 5xx, a 404 without a code, no connection A temporary failure. Keep your last good copy and try again later.

Only a 404 with the code PRICE_LIST_NOT_FOUND means the prices must go. On any response other than 200 or 304, leave the prices on your site, also on a 404 with another code. Otherwise a failure on our side would leave your site without prices.

Errors have the shape { "success": false, "code": "…", "message": "…" }. Read the code, not the message.

Switching off and stored copies

When the shop switches the list off, the server answers 404 straight away on the next request, also when it still kept the list. A client or an intermediate cache can still show the list for at most 60 seconds.

An external site that has stored the data or processed it in a build shows it until it fetches again by itself. Repairflow cannot withdraw those copies. So build your site to fetch regularly and to remove its copy on a 404 PRICE_LIST_NOT_FOUND.

Static sites, browsers and rate limits

A statically built site does not refresh by itself. When and how often the site fetches the list or rebuilds is up to the site. Plan that, for example with a timer or a scheduled build, and choose an interval of minutes to hours, not seconds.

For SEO and for static sites, fetch the list on the server side and keep a copy. The prices are then in the HTML, and your site keeps showing prices when the API briefly does not answer.

Fetching from the visitor’s browser works too. The browser then follows max-age=60 by itself. Keep in mind that the limit per shop counts all visitors of that shop together. A busy site is therefore better off fetching the list on the server side and showing its own copy to visitors.

The limits (they may change, do not build on them):

  • approximately 120 requests per minute per IP address;
  • approximately 120 requests per minute per shop, all IP addresses together;
  • approximately 280 requests per minute in total for the whole API.

A 304, 404 and 503 count too. A site that fetches on the server side a few times an hour stays far below every limit. When you get a 429, keep your last copy and wait at least as long as Retry-After says.

A server-side example

This Node script (Node 20 or later) fetches the list with If-None-Match, stores the last good copy, removes the prices on a 404 PRICE_LIST_NOT_FOUND and leaves the copy alone on every other response. Run it on a timer or before every build and read price-list.json when you build your pages.

import { readFile, writeFile, rm } from 'node:fs/promises';

const URL = 'https://api.repairflow.eu/api/v1/shops/voorbeeld-reparatie/price-list';
const COPY = './price-list.json';
const ETAG = './price-list.etag';

async function read(path) {
  try { return await readFile(path, 'utf8'); } catch { return null; }
}

export async function refreshPriceList() {
  const etag = await read(ETAG);
  let res;
  try {
    res = await fetch(URL, {
      headers: etag ? { 'If-None-Match': etag } : {},
      signal: AbortSignal.timeout(10_000),
    });
  } catch {
    return 'kept'; // no connection: keep the last copy
  }

  if (res.status === 304) return 'unchanged';

  if (res.status === 200) {
    const body = await res.text();
    JSON.parse(body); // invalid JSON throws here
    await writeFile(COPY, body);
    const next = res.headers.get('etag');
    if (next) await writeFile(ETAG, next);
    return 'updated';
  }

  if (res.status === 404) {
    const error = await res.json().catch(() => null);
    if (error?.code === 'PRICE_LIST_NOT_FOUND') {
      await rm(COPY, { force: true }); // the shop no longer publishes
      await rm(ETAG, { force: true });
      return 'removed';
    }
  }

  return 'kept'; // 429, 503, 5xx and everything else: temporary
}

Versions

The contract has a version in the path. In v1 fields are only added: existing fields do not disappear and do not change meaning, and a client ignores fields it does not know. A breaking change comes as /api/v2/…, and v1 stays available for as long as it is used.

Do you have a question, or are you running into something? Email support@repairflow.eu.