/eprel/products

POST /api/eprel/products

Price: 1 credit

Look up one model in EPREL, the EU register every product carrying an EU energy label must be entered into, by its registration number and product group. Returns the energy class and the scale it is measured on, the model identifier and supplier or trademark, the registration status and version, on-market start and end dates, the countries the model is declared available in, the supplier's registered organisation and contact address, any supplier notes, and the full technical record the group's regulation requires — compartment volumes, dimensions, noise, consumption, tyre grip and rolling-noise classes, panel technology, and so on, under the field names the registry publishes.

How to use it

A bare registration number will not resolve on its own — the registry only serves a model under its own product group, so pass `product_group` too. A number that is valid under a different group answers 412, not someone else's product, so a wrong guess is safe but costs a call; if the group is unknown, the only route is to try the plausible ones. Energy classes are not comparable across groups: read `energy_class_range` to see which scale the letter belongs to, because an A on a A-G scale and an A on an A-E scale mean different things, and older regulations use APP/APPP for what is now A. The regulation-specific measurements live in `attributes` under the registry's own field names, which differ by product group; the same names are what `eprel/products/search` accepts as `filters`.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• product_group string required — Product group the registration number belongs to. The registry has no group-less lookup, so this must match the group the model was registered under (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", "tyres")
• registration_number string required — EPREL registration number of the model, as printed on the energy label QR code (examples: "2836291", "296927", "2384029"; minLength: 1)

Response

• @type string (default: "EprelProduct")
• id string required
• url string required
• product_group string required
• model_identifier string nullable
• supplier string nullable
• energy_class string nullable
• energy_class_range string nullable
• energy_label_id string nullable
• implementing_act string nullable
• status string nullable
• form_type string nullable
• registrant_nature string nullable
• is_blocked boolean nullable
• is_last_version boolean nullable
• is_visible_to_uk_msa boolean nullable
• has_generated_label boolean nullable
• uploaded_labels array (default: [])
• version_id string nullable
• version_number number nullable
• product_model_core_id string nullable
• trademark_id string nullable
• trademark_owner string nullable
• trademark_verification_status string nullable
• organisation_verification_status string nullable
• availability_in_eu_eea_countries string nullable
• available_in_countries array (default: [])
• available_in_eu_eea_countries array (default: [])
• available_in_other_countries array (default: [])
• on_market_start_at integer nullable
• on_market_end_at integer nullable
• on_market_first_start_at integer nullable
• first_published_at integer nullable
• published_at integer nullable
• exported_at integer nullable
• imported_at integer nullable
• contact_id string nullable
• contact object nullable
  • @type string (default: "EprelContact")
  • id string nullable
  • service_name string nullable
  • email string nullable
  • phone string nullable
  • web_url string nullable
  • street string nullable
  • street_number string nullable
  • address_block string nullable
  • postal_code string nullable
  • city string nullable
  • municipality string nullable
  • province string nullable
  • country string nullable
  • status string nullable
  • order_number integer nullable
  • is_default boolean nullable
  • is_specific boolean nullable
  • contact_reference string nullable
  • contact_by_reference_id string nullable
• organisation object nullable
  • @type string (default: "EprelOrganisation")
  • id string nullable
  • name string nullable
  • display_name string nullable
  • first_name string nullable
  • last_name string nullable
  • person_type string nullable
  • web_url string nullable
  • is_closed boolean nullable
  • close_status string nullable
  • closed_at integer nullable
• additional_infos array (default: [])
  • @type string (default: "EprelAdditionalInfo")
  • id string nullable
  • language string nullable
  • order_number integer nullable
  • text string nullable
• attributes object (default: {})

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 — No model with that registration number is registered under that product group. 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.