/eprel/products/fiche

POST /api/eprel/products/fiche

Price: 5 credits

Resolve the product information sheet for one registered model and return a direct, publicly fetchable link to the PDF, with the media type and byte size the registry served. This is the standardised sheet the energy-labelling regulations require a supplier to publish alongside the label, listing the model's declared parameters in full. Available in the 24 official EU languages plus Norwegian and Turkish.

How to use it

The link is checked before it is returned: the registry builds an address for any input and its web server answers 200 with an HTML page rather than a 404 when the PDF behind it does not exist, so a sheet the registry cannot render comes back as 412 here instead of as a link to a web page. Pick the language the answer is for — the sheet is a translation of the same declared values, so `language` changes the wording and the units notation, not the measurements. The values themselves are already structured on the product record, so fetch the sheet when a citable regulatory document is wanted rather than to read numbers out of it.

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 (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", "electronicdisplays")
• registration_number string required — EPREL registration number of the model (examples: "2836291", "296927"; minLength: 1)
• language string — Language to render the sheet in: the 24 official EU languages plus Norwegian and Turkish (default: "EN"; one of: "BG", "CS", "DA", "DE", "EL", "EN", "ES", "ET", "FI", "FR", "GA", "HR", "HU", "IT", "LT", "LV", "MT", "NL", "NO", "PL", "PT", "RO", "SK", "SL", "SV", "TR")

Response

• @type string (default: "EprelDocument")
• id string required
• url string required
• product_id string required
• product_group string required
• document_type string required
• artwork_format string nullable
• language string nullable
• content_type string nullable
• size_bytes integer 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 model is not registered under that product group, or the registry has no information sheet for it in that language. 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.