/eprel/product_groups

POST /api/eprel/product_groups

Price: 1 credit

List the product groups of EPREL, the EU energy-label register. Each group is a separate register under its own EU regulation, and every other EPREL endpoint is scoped to one of them. Returns the group's registry code, the path segment the other endpoints take, its display name, the regulation it implements, a periodically-measured model count (the live figure for one group comes from eprel/products/search or eprel/products/stats), the energy-class letters its scale uses, and the search filters it publishes — each with the parameter names to send, whether it is a range, a boolean, a fixed set of values or free text, and the observed bounds of a numeric one.

How to use it

Read this before building a product search: `alias` is what the other EPREL endpoints take as `product_group`, and `filters` is the only place the group-specific filter keys are listed — including whether the group grades on a single energyClass or on several named ones such as energyClassWash. Groups come in pairs where a newer regulation replaced an older one — the repealed group keeps its own models and stays queryable, so a supplier's full history usually spans both. `energy_classes` shows why letters are not comparable across groups: some scales run A-G, others A-E, and the older ones stack AP, APP and APPP above A for what a rescaled group would now call A. Where a filter reports `are_values_complete` false, `values` is a sample of what the register holds rather than the closed set, so treat an absent value as unseen rather than invalid.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product_group string nullable — Restrict the answer to one group. Left unset, every group the registry publishes is returned (one of: "airconditioners", "dishwashers", "dishwashers2019", "electronicdisplays", "hotwaterstoragetanks", "lamps", "lightsources", "localspaceheaters", "ovens", "professionalrefrigeratedstoragecabinets", "rangehoods", "refrigeratingappliances", "refrigeratingappliances2019", "refrigeratingappliancesdirectsalesfunction", "residentialventilationunits", "smartphonestablets20231669", "solidfuelboilerpackages", "solidfuelboilers", "spaceheaterpackages", "spaceheaters", "spaceheatersolardevice", "spaceheatertemperaturecontrol", "televisions", "tumbledriers", "tumbledryers20232534", "tyres", "washerdriers", "washerdriers2019", "washingmachines", "washingmachines2019", "waterheaterpackages", "waterheaters", "waterheatersolardevices"; examples: "refrigeratingappliances2019")
• count integer required — Max number of results to return (min: 1; max: 33)

Response

• @type string (default: "EprelProductGroupInfo")
• id string required
• alias string required
• name string required
• regulation string nullable
• model_count integer nullable — How many models the group held the last time the filter catalogue was refreshed - a periodic measurement, not a live count. eprel/products/search and eprel/products/stats report the live total for the same product_group
• energy_classes array (default: [])
• filters array (default: [])
  • @type string (default: "EprelGroupFilter")
  • name string required
  • form string required
  • params array (default: [])
  • values array (default: [])
  • are_values_complete boolean (default: false)
  • rejects_unknown_value boolean (default: false)
  • observed_min number nullable
  • observed_max number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The registry returned no product groups. Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.