/eprel/products/search

POST /api/eprel/products/search

Price: 20 credits

Search one EPREL product group, the EU register every product carrying an EU energy label must be entered into. Narrows by energy class, supplier or trademark, model identifier, commercial name and GTIN, and by the technical fields the group's own regulation defines — compartment volumes and dimensions for refrigerators, tyre size, load index and wet-grip class for tyres, panel technology and resolution for displays — passed as filters under the registry's own field names. Orders by energy class, supplier, model identifier, registration number or the on-market and publication dates. Returns the same full model record as the single-product lookup.

How to use it

One `product_group` per call — the registry has no cross-group search, and the same appliance often appears under two groups because a newer regulation replaced an older one (refrigeratingappliances2019 supersedes refrigeratingappliances, lightsources supersedes lamps); the repealed group still holds its own models, so cover both when completeness matters. Call eprel/product_groups first to see which `filters` keys and energy-class letters a group publishes: a key from the wrong group is rejected rather than ignored, which is deliberate, because the registry itself would silently return the unfiltered set. Withdrawn and superseded registrations are excluded unless `include_old_products` is set, which typically adds a tenth to the matches. A single call reaches at most 10000 models however many match, so to cover one of the larger groups split it by supplier, energy class or a numeric range rather than raising `count`.

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 to search. Each group is a separate register under its own EU regulation, and a search never spans more than one. Groups whose regulation was repealed are still queryable and hold the models registered under it (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", "lightsources", "tyres")
• energy_class array nullable — Energy classes to keep. The letters differ by group and are listed per group by eprel/product_groups; older regulations add AP, APP and APPP above A. Groups whose regulation grades more than one thing publish named class filters instead, such as energyClassWash and energyClassWashAndDry on washer-dryers, which go in filters (examples: ["A","B"], ["APPP"])
• supplier string nullable — Supplier or trademark name (examples: "Liebherr", "LG Electronics"; minLength: 1)
• model_identifier string nullable — Supplier's model identifier (examples: "GBB567PZCZB"; minLength: 1)
• commercial_name string nullable — Commercial name the model is marketed under (examples: "DC-100"; minLength: 1)
• gtin string nullable — GTIN barcode of the model (examples: "8690842762512"; minLength: 1)
• include_old_products boolean — Include models whose registration is withdrawn or superseded. Off by default, matching what the public registry search shows (default: false)
• filters object nullable — Group-specific filters, keyed by the registry's own field name. Every group publishes a different set; eprel/product_groups lists the accepted keys, their form and their range for one group. Numeric fields take a Min and a Max key, booleans take true or false, and a key the chosen group does not publish is rejected (examples: {"capFreezeNetMax":"120","capFreezeNetMin":"100"}, {"applianceType":"WINE_STORAGE"})
  • * string
• sort string nullable — Field to order by. Unset leaves the registry's own order (one of: "energyClass", "modelIdentifier", "supplierOrTrademark", "onMarketStartDateTS", "publishedOnDateTS", "eprelRegistrationNumber")
• order string — Direction for sort (default: "DESC"; one of: "ASC", "DESC")
• count integer required — Max number of results to return (min: 1; max: 10000)

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 — A filter key or energy-class letter the chosen product_group does not publish. eprel/product_groups lists what it accepts. 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 — Nothing in that product group matched the filters. 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.