{"id":6510,"date":"2026-10-28T23:14:43","date_gmt":"2026-10-28T20:14:43","guid":{"rendered":"https:\/\/aesinn.com\/?page_id=6510"},"modified":"2026-10-28T23:14:43","modified_gmt":"2026-10-28T20:14:43","slug":"dpp-yazilimi-secimi-en-18216-en-18222-en-18223-protokol-api","status":"publish","type":"page","link":"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/dpp-yazilimi-secimi-en-18216-en-18222-en-18223-protokol-api\/","title":{"rendered":"When Choosing DPP Software: Protocol and API according to EN 18216, 18222 and 18223."},"content":{"rendered":"<p class=\"wp-block-paragraph\">If you are an IT manager or administrator selecting a software or service provider for a Digital Product Passport (DPP), you need to know how to weigh the claims in the proposals. This article examines the EN 18216, EN 18222, and EN 18223 standards together, which form the technical framework of the passport: data exchange protocols, lifecycle and searchability APIs, and system interoperability. We distinguish what is mandatory, recommended, and what the standard doesn&#039;t say at all by item number. This article is part of the DPP Standards Guide series.<\/p>\n\n\n\n<div class=\"aes-standart-durumu\" style=\"border-left:4px solid #1F4E79;background:#f3f6fa;padding:14px 18px;margin:18px 0 22px 0;font-size:15px;line-height:1.6;color:#222;\"><strong>Official status of the standard<\/strong><ul style=\"margin:8px 0 6px 18px;padding:0;\"><li>EN 18216:2026 (data exchange protocols), EN 18222:2026 (APIs) and EN 18223:2026 (system interoperability) were published in May 2026 in the Official Journal of the EU. <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/TR\/TXT\/?uri=CELEX:32026D1736\">(EU) 2026\/1736<\/a> It was referred to as a standard harmonized with Commission Implementing Decision No. 14 (July 14, 2026).<\/li><\/ul><span style=\"font-size:13px;color:#555;\">Source: CEN\/CENELEC publication information and the Official Journal of the European Union (EUR-Lex), checked 28 October 2026.<\/span><\/div>\n\n\n\n<div class=\"aes-ortak-notu\" style=\"border-left:4px solid #CE1A1A;background:#f6f6f6;padding:14px 18px;margin:18px 0 22px 0;font-size:15px;line-height:1.6;color:#222;\"><strong>Service note:<\/strong> AES Innovation carries out the EU compliance work described on this page (PPWR, digital product passport, CBAM, etc.) in collaboration with expert solution partners; it does not provide these services directly. These activities are outside the scope of our accreditation (AB-0631-M).<\/div>\n\n\n\n<h2 class=\"wp-block-heading\">What does the standard regulate, and what does it not regulate?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These standards are different layers of the same structure. EN 18216 specifies the channel and format through which data will be transmitted (EN 18216, clauses 4 and 5). EN 18222 defines the application programming interface (API) methods to be used to access, create, and update the passport (EN 18222, clauses 4-8). EN 18223 regulates how the passport&#039;s internal structure will be organized and how the fields will be interpreted (EN 18223, clauses 4 and 5).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Neither specifies which product data the passport should carry; this comes from product group regulations (EN 18223, Entry 0.1 and clause 4.1.2.1). For product-specific data requirements... <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/tekstil-sektorunde-dijital-urun-pasaportu-dpp-espr-veri-gereklilikleri-ve-hazirlik\/\">textile<\/a>, <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/celik-sektorunde-dijital-urun-pasaportu-dpp-espr-kapsaminda-karbon-geri-donusum-ve-izlenebilirlik-verisi\/\">steel<\/a> And <a href=\"https:\/\/aesinn.com\/en\/batarya-pasaportu-nedir-ab-batarya-tuzugu\/\">battery passport<\/a> You can check out our articles.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">How to provide the product identifier <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18219-dpp-benzersiz-tanimlayici-urun-operator-tesis-kimligi\/\">our singular descriptive text<\/a>, This includes where and for how long the data will be stored, as well as archiving and backup rules. <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18221-dpp-veri-saklama-arsiv-yedek-kalicilik\/\">our data storage and archiving article<\/a> This is the subject. For access rights and data integrity. <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18239-dpp-erisim-haklari-ticari-gizlilik\/\">EN 18239<\/a> And <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18246-dpp-veri-imza-butunluk-degisiklik-izi\/\">EN 18246<\/a> You can check out our articles.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Protocol and format: How to present a passport (EN 18216)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">EN 18216 requires that access to the passport be via HTTPS, i.e., HTTP encrypted with TLS (Transport Layer Security), and that the protocol protects the confidentiality and integrity of the data (EN 18216, clause 4).<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>TLS: The minimum threshold is TLS 1.2 (mandatory). TLS 1.3 and above are strongly recommended. TLS 1.0, TLS 1.1, and all versions of SSL are not permitted (clause 4).<\/li>\n\n\n\n<li>HTTP: The minimum version is HTTP\/2 (mandatory), HTTP\/3 is recommended. HTTP\/1.1 and older versions are not permitted (clause 4).<\/li>\n\n\n\n<li>Architecture: REST architectural style is recommended, but not mandatory (item 4).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, an old web server offering only HTTP\/1.1, a shared hosting package, or a caching network (CDN) configuration is not sufficient for the passport.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Which formats are mandatory?<\/h3>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Format<\/th><th>Situation<\/th><th>Article<\/th><\/tr><\/thead><tbody><tr><td>JSON<\/td><td>Mandatory; the only mandatory format for machine-readable change.<\/td><td>EN 18216, clause 5(a)<\/td><\/tr><tr><td>HTML<\/td><td>It must be aesthetically pleasing and comply with the accessibility requirements of EN 301549:2021.<\/td><td>EN 18216, clauses 5 and 5(d)<\/td><\/tr><tr><td>XML<\/td><td>Optional, with HTTP content handshake.<\/td><td>EN 18216, clause 5(b)<\/td><\/tr><tr><td>JSON-LD<\/td><td>Optional; if used, it should be able to be processed by a standard JSON parser.<\/td><td>EN 18216, clause 5(c)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Content negotiation is when the client specifies which format it wants in the HTTP request, and the server responds accordingly. JSON-LD (JSON for linked data) is the only option in the standard (clause 5(c)).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is uploading the PDF sufficient?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The mandatory formats are JSON and accessible HTML (EN 18216, clause 5); EN 18223 also requires the passport to be serialized as a JSON object during data exchange (EN 18223, clause 5.2.4). Documents such as user manuals or certificates are linked to the passport as a related resource, associated with its file type (MIME type) and address (EN 18223, clause 4.1.2.7). Therefore, a PDF can be an attachment to the passport, but not the passport itself.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">API: Which operations are mandatory (EN 18222)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Which method will be provided by whom is specified in EN 18222 clause 4.1. Below, \u2019creator\u201c is the economic operator or its main DPP service provider that created the passport; \u201dbackup\u201c is the service provider that hosts the backup copy when one exists.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Method<\/th><th>What does he do?<\/th><th>Level<\/th><th>Article<\/th><\/tr><\/thead><tbody><tr><td>ReadDPPById<\/td><td>The passport reader uses the passport ID to scan the passport.<\/td><td>Required: creating and backup<\/td><td>4.1, 4.2<\/td><\/tr><tr><td>ReadDPPbyProductId<\/td><td>It reads the current (active) passport with the product identifier.<\/td><td>Required: creating and backup<\/td><td>4.1, 4.3<\/td><\/tr><tr><td>ReadDPPIdsByProductIds<\/td><td>It returns passport IDs in bulk for multiple product identifiers.<\/td><td>Required: creating and backup<\/td><td>4.1, 4.5<\/td><\/tr><tr><td>UpdateDPPById<\/td><td>It partially updates the passport.<\/td><td>Mandatory: if the creator, authorized third parties have the right to update.<\/td><td>4.1, 4.7<\/td><\/tr><tr><td>ReadDataElement, UpdateDataElement<\/td><td>Reads or updates a single data element.<\/td><td>Recommended: create a backup for reading; create one for updating, under the same conditions.<\/td><td>4.1, 6.2, 6.3<\/td><\/tr><tr><td>CreateDPP, DeleteDPPById, ReadDPPVersionByIdAndDate<\/td><td>Creating, deleting, reading a version from a specific date.<\/td><td>Recommended: primary provider and backup.<\/td><td>4.1, 4.4, 4.6, 4.8<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Each method also has a defined REST equivalent; for example, reading with a passport ID is a GET request to the path v1\/dpps\/{dppId} (clause 8.2, Table 16). The v1\/ prefix in the paths indicates the API version; updating this prefix is mandatory with a new API version (clause 8.1).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The backup provider must also offer the three mandatory reading methods (clause 4.1). In our assessment, a static page accessed via a QR code alone does not meet these requirements; the backup should also be a queryable service, not just a file repository.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When is updating mandatory, and how does the archive work?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The partial update method becomes mandatory if authorized third parties, such as service providers, dealers, or recyclers, have the right to update only a portion of the passport (clause 4.1). It is recommended that if even one part of the update fails, the entire process will be considered a failure, leaving no changes to the passport (clause 4.7).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The standard does not include a separate \u201carchive\u201d method; archiving is a mandatory side effect of updating. All changes to the passport must be archived according to EN 18221 (EN 18222, clause 4.7; EN 18223, clause 4.2). A method is defined for retrieving the version from a specific date for access; its input is the passport ID and a UTC-based timestamp (EN 18222, clause 4.4).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\u201cWhat does &quot;searchability&quot; mean?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The searchability mentioned in the standard&#039;s title is not free-text searching as in a search engine. The standard lists read methods that can be used to establish search functionality, primarily those that retrieve the current passport using the product identifier and return passport IDs corresponding to multiple product identifiers (clauses 4.1, 4.3, 4.5). Searching by keyword, category, or filter is not defined. Therefore, your choice of product identifier directly determines how your API will be queried.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Authentication and error responses<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">EN 18222 defines status code 401 for a request with missing or incorrect credentials, and 403 for a request denied authorization, and recommends returning a result object explaining the reason for the failed request (clause 7.2, Table 15). However, EN 18222 does not define a specific authentication method (OAuth 2.0, API key, client certificate, etc.). OAuth 2.0 and OpenID Connect are only mentioned as examples in Annex B of EN 18216 for informational purposes. Authentication principles are the subject of the access rights standard EN 18239; these are... <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18239-dpp-erisim-haklari-ticari-gizlilik\/\">in our article on access rights<\/a> We are addressing it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Seven header fields that must be present in every passport (EN 18223)<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">EN 18223 lists the common header fields that every passport copy must include (EN 18223, clause 4.1.2.1, Table 1). The seven fields indicated with a cardinality of 1 in the table are:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>digitalProductPassportId: The identifier of the passport instance. It should be globally unique, and it is recommended that it be based on a URI\/URL structure (clause 4.1.2.1).<\/li>\n\n\n\n<li>uniqueProductIdentifier: Product identifier; formatted according to EN 18219.<\/li>\n\n\n\n<li>Granularity: The level of the identifier; model, batch, or individual item (clause 4.1.2.2).<\/li>\n\n\n\n<li>dppSchemaVersion: The reference standard on which the passport schema is based.<\/li>\n\n\n\n<li>dppStatus: The status of the passport as a digital source.<\/li>\n\n\n\n<li>lastUpdated: The date and time of the last update; UTC-based, in ISO 8601-1:2019 format.<\/li>\n\n\n\n<li>economicOperatorId: The identifier of the economic operator; formatted according to EN 18219. Standards are not clear on this point, as EN 18219 links the operator identifier to situations required by legislation.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Facility ID and content specification IDs are optional; product-specific data follows the header as a data element (Table 1). Passport ID and product identifier are separate fields; local time generating systems must convert the timestamp to UTC.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Semantic interoperability and \u201ccertified\u201d claims<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Semantic interoperability refers to the ability of systems from different companies to understand the same domain in the same way (EN 18223, clause 3.2). EN 18223 establishes this not with a single sector ontology, but with a decoupled approach: Data points and their definitions are managed separately (clause 4.3).<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>It is recommended that each data point be linked to a machine-read definition held in a dictionary repository; the link is established using the dictionaryReference attribute (item 4.3).<\/li>\n\n\n\n<li>Each definition appears only once in a database and has its own unique identity; this is necessary to prevent ambiguity in references (clause 4.3).<\/li>\n\n\n\n<li>It is recommended to base the management of the repository on legislation; however, the repository must also accommodate definitions not included in the legislation when necessary (article 4.3). In our interpretation, this opens the door to your own data fields.<\/li>\n\n\n\n<li>Data elements belong to specific classes: collection, single-valued, multi-valued, related source, and multilingual element (clauses 4.1.2.4-4.1.2.8).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">At the technical level, the element ID in the compressed representation becomes the JSON key; metadata such as dictionary reference and data type are considered defined in an external dictionary (clause 5.2.2). The fully extended JSON is in Appendix A; the default format in API responses is the compressed representation (EN 18222, clause 8.1). JSON-LD, RDF, or OWL are not mentioned in EN 18223; the claim that \u2019JSON-LD is required for interoperability\u201c is not based on the standard.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">\u201cWhat does &quot;EN 18223 certified&quot; mean?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">EN 18223 does not contain conformity assessment, test procedures, test sets, or certification clauses; nor is a schema file (JSON Schema or XSD) provided for verification. Therefore, statements such as \u2019EN 18223 certified\u201c or \u201dapproved software\u201c have no basis in the standard. Such a claim is based not on a test defined in the standard, but on a test determined by the supplier or a third party; inquire about which test was used for verification.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Harmonized standard status is not a certificate; the presumption of conformity arises only to the extent that it is covered by the standards and the solution genuinely conforms to the standard.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Decisions you need to make as a producer<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Will you host it yourself or will a service provider host it? If you host it on your own infrastructure, you are responsible for TLS and HTTP versions and forced read methods (EN 18216, clause 4; EN 18222, clause 4.1).<\/li>\n\n\n\n<li>Will third parties be responsible for updates? If you authorize service providers, dealers, or recyclers to perform updates on a site-by-site basis, then a partial update method becomes mandatory (EN 18222, clauses 4.1 and 4.7).<\/li>\n\n\n\n<li>Granularity: The model, batch, or individual product level decision defines both the header field and the API queries (EN 18223, clause 4.1.2.2; EN 18222, clause 4.3).<\/li>\n\n\n\n<li>Additional formats: XML and JSON-LD are optional; if there is no specific recipient request, it is sufficient to start with JSON and accessible HTML (EN 18216, clause 5).<\/li>\n\n\n\n<li>Glossary and your own fields: Determine which glossary repository you will use and how you will define your non-regulatory fields (EN 18223, clause 4.3).<\/li>\n\n\n\n<li>ERP\/PLM mapping: The standard doesn&#039;t regulate this, but mapping your product master data to this class structure is one of the most labor-intensive steps in implementation.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Questions to ask the DPP software supplier<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Checklist for comparing bids: Items on the first list are outside the standard, items on the second list are non-standard but important for the contract.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Questions based on standard requirements.<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Do your DPP endpoints completely reject TLS 1.0, TLS 1.1, and SSL connections, and is TLS 1.3 enabled? (EN 18216, clause 4)<\/li>\n\n\n\n<li>Is your minimum HTTP version HTTP\/2, are HTTP\/1.1 requests closed, or is HTTP\/3 supported? (EN 18216, clause 4)<\/li>\n\n\n\n<li>Do you provide both JSON for machine viewing and HTML for human viewing? Which browsers and platforms has the HTML view been tested on according to EN 301549:2021? (EN 18216, clause 5)<\/li>\n\n\n\n<li>Are ReadDPPById, ReadDPPByProductId, and ReadDPPIdsByProductIds working on both your end and the backup provider&#039;s end? (EN 18222, clause 4.1)<\/li>\n\n\n\n<li>Do you provide the REST paths (v1\/dpps\/\u2026, v1\/dppsByProductId\/\u2026, v1\/dppsByProductIds) exactly as specified in the standard? (EN 18222, clause 8.2, Table 16)<\/li>\n\n\n\n<li>Do you allow authorized third parties to update specific fields; does partial updating work on an &quot;all or nothing&quot; basis, and are all changes archived? (EN 18222, clauses 4.1 and 4.7)<\/li>\n\n\n\n<li>Is there a method to retrieve a passport version from a specific date? (EN 18222, clause 4.4)<\/li>\n\n\n\n<li>Do your error responses return status codes and a descriptive result object as shown in Table 15? (EN 18222, clause 7.2)<\/li>\n\n\n\n<li>Do your passports contain the seven mandatory header fields in Table 1, and is the passport ID globally unique? (EN 18223, clause 4.1.2.1)<\/li>\n\n\n\n<li>Is it possible to link each data point to a dictionary definition (DictionaryReference), and to define our own non-regulatory fields? (EN 18223, clause 4.3)<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Non-standard but necessary questions<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Which authentication method are you using (OAuth 2.0, API key, client certificate) and how does this method align with the policies in EN 18239? EN 18222 does not define a method.<\/li>\n\n\n\n<li>Are you publishing a machine-readable OpenAPI definition? EN 18222 does not provide such a file.<\/li>\n\n\n\n<li>\u201cWhich test did you use to verify your claim of being &quot;EN 18223 compliant&quot;? The standard does not include a test procedure.<\/li>\n\n\n\n<li>Do you offer any tools or services for mapping this data model from our ERP\/PLM system?<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">First steps for preparation<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Have your IT team test the TLS and HTTP version support of your web server, hosting, and CDN environment.<\/li>\n\n\n\n<li>Decide on the product identifier and granularity before API design.<\/li>\n\n\n\n<li>Find the equivalents for seven header fields (EN 18223, Table 1) in the ERP\/PLM; list the missing fields such as passport ID, schema version, and status.<\/li>\n\n\n\n<li>Verify that timestamps are generated in UTC and ISO 8601-1 format.<\/li>\n\n\n\n<li>Identify the third parties who will update the passport and the fields they will update.<\/li>\n\n\n\n<li>Include the above questions in the tender specifications and obtain written answers.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Information Note<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">This content is for informational purposes only and does not replace the standard text; in practice, the current and complete text of the standard should be used. AES is not an approved or certification body; it does not issue, verify, or certify Digital Product Passport documents, and does not offer any passport software or Registration System services.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">AES&#039;s T\u00dcRKAK accreditation covers only the periodic inspection of electrical installations (AB-0631-M). The above information does not constitute a binding legal or technical opinion; each specific case should be evaluated within its own context.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Related Services and Content<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18219-dpp-benzersiz-tanimlayici-urun-operator-tesis-kimligi\/\">Unique Identifier in DPP: Product, Operator and Facility according to EN 18219<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18220-iso-iec-18004-dpp-qr-kod-veri-tasiyici-secimi-baski-kalitesi\/\">QR Code and Data Carrier for DPP: EN 18220 and ISO\/IEC 18004 Guidelines<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18239-dpp-erisim-haklari-ticari-gizlilik\/\">Who Sees What in DPP? Access Rights and Commercial Privacy with EN 18239<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18246-dpp-veri-imza-butunluk-degisiklik-izi\/\">Trusting DPP Data: Signature, Integrity, and Change Trace with EN 18246<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18221-dpp-veri-saklama-arsiv-yedek-kalicilik\/\">Where and for how long is DPP data stored? Archiving and backup according to EN 18221.<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/dpp-hazirlik-kontrol-listesi-en-standartlarina-gore-uretici-kararlari\/\">DPP Preparation Checklist: Manufacturer Decisions According to Eight EN Standards<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/dijital-urun-pasaportu-teknik-altyapisi-en-standartlari-veri-tasiyici-ve-ab-kayit-sistemi\/\">Digital Product Passport Technical Infrastructure: EN Standards, Data Carrier and EU Registration System<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/espr-ve-dijital-urun-pasaportu-dpp-ihracatci-ureticiler-icin-kapsamli-rehber\/\">ESPR and Digital Product Passport (DPP): A Comprehensive Guide for Exporting Manufacturers<\/a><\/li>\n\n<li><a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/\">Digital Product Passport (DPP) Services<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently Asked Questions<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Is it sufficient to publish the passport only as a PDF?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The mandatory formats are JSON for machine-friendly formats and human-accessible HTML (EN 18216, clause 5). PDFs can be linked as associated resources in a document such as a manual or certificate (EN 18223, clause 4.1.2.7).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Our server is running on HTTP\/1.1 and TLS 1.2; is that sufficient?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">TLS 1.2 is sufficient as a minimum, TLS 1.3 is strongly recommended. HTTP\/1.1 is insufficient; the minimum version is HTTP\/2 (EN 18216, clause 4).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is JSON-LD mandatory?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. JSON-LD is an optional format; if used, it must be processable by a standard JSON parser (EN 18216, clause 5(c)).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Which API methods are absolutely essential?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Passport ID reading, product identifier reading, and batch ID verification are required; at the originating party and, if applicable, at the backup provider (EN 18222, clause 4.1). Partial updating is also mandatory if authorized third parties have the right to update (clauses 4.1 and 4.7).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Will users be able to search for my passport using keywords?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The standard does not define free-text search. Searchability consists of reading methods that enable passport retrieval using the product identifier (EN 18222, clauses 4.1, 4.3 and 4.5).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does the standard require the use of OAuth 2.0?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. EN 18222 defines status codes 401 and 403 for unauthorized requests (clause 7.2, Table 15), but it does not define a specific authentication method. OAuth 2.0 in EN 18216 Annex B is merely an example for informational purposes. Authentication principles are the subject of EN 18239.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">My supplier says &quot;EN 18223 certified&quot;; what does that mean?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">EN 18223 does not define conformity testing, test sets, or certification; there is no such provision in the standard. The basis of the claim is the written problem.<\/p>","protected":false},"excerpt":{"rendered":"<p>PDF y\u00fcklemek DPP de\u011fildir: EN 18216, EN 18222 ve EN 18223 pasaportun hangi protokol ve formatla sunulaca\u011f\u0131n\u0131, hangi API y\u00f6ntemlerinin zorunlu oldu\u011funu ve her pasaportta hangi ba\u015fl\u0131k alanlar\u0131n\u0131n bulunaca\u011f\u0131n\u0131 belirler. DPP yaz\u0131l\u0131m\u0131 se\u00e7ecek BT sorumlusu ve y\u00f6netici i\u00e7in madde numaral\u0131 bir kontrol listesi.<\/p>","protected":false},"author":1,"featured_media":6509,"parent":4959,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"_kad_blocks_custom_css":"","_kad_blocks_head_custom_js":"","_kad_blocks_body_custom_js":"","_kad_blocks_footer_custom_js":"","_kadence_starter_templates_imported_post":false,"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","slim_seo":{"title":"EN 18216, 18222, 18223: DPP Protocol, API, Data Model","description":"When choosing DPP software, here's what EN 18216, 18222, and 18223 require: HTTPS and TLS versions, JSON and HTML, mandatory API methods, seven header fields, and supplier queries."},"_pplb_hide_from_list":false,"footnotes":""},"class_list":["post-6510","page","type-page","status-publish","has-post-thumbnail","hentry"],"acf":[],"taxonomy_info":[],"featured_image_src_large":["https:\/\/aesinn.com\/wp-content\/uploads\/dpp-api-aes-kart-1024x1024.png",1024,1024,true],"author_info":{"display_name":"Emre Metin","author_link":"https:\/\/aesinn.com\/en\/author\/yonetim\/"},"comment_info":"","_hostinger_reach_plugin_has_subscription_block":false,"_hostinger_reach_plugin_is_elementor":false,"_links":{"self":[{"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages\/6510","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/comments?post=6510"}],"version-history":[{"count":1,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages\/6510\/revisions"}],"predecessor-version":[{"id":6521,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages\/6510\/revisions\/6521"}],"up":[{"embeddable":true,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages\/4959"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/media\/6509"}],"wp:attachment":[{"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/media?parent=6510"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}