{"id":6508,"date":"2026-10-28T23:14:41","date_gmt":"2026-10-28T20:14:41","guid":{"rendered":"https:\/\/aesinn.com\/?page_id=6508"},"modified":"2026-10-28T23:14:41","modified_gmt":"2026-10-28T20:14:41","slug":"en-18221-dpp-veri-saklama-arsiv-yedek-kalicilik","status":"publish","type":"page","link":"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18221-dpp-veri-saklama-arsiv-yedek-kalicilik\/","title":{"rendered":"Where and for how long is DPP data stored? Archiving and backup according to EN 18221."},"content":{"rendered":"<p class=\"wp-block-paragraph\">The following questions frequently arise during the preparation of a Digital Product Passport (DPP): Who will maintain the passport data, what will happen to the old versions, and will the passport be lost if the company withdraws from the market? This article explains the answers and deliberate omissions provided by the EN 18221:2026 standard, which regulates the storage, archiving, and persistence of DPP data. 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 18221:2026 (data storage, archiving and persistence) was 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\">EN 18221 is a short standard published in May 2026. Its mandatory provisions are grouped into five sub-clauses: retention, archiving, persistence, digital documents attached to the passport, and duplication to the backup provider (clauses 4.1 to 4.5). All are based on a decentralized architecture; each passport resides in the system of the party that issued it or its service provider (clauses 1 and 4.1).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The spaces left blank by the standard are at least as important as the spaces they regulate:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>It does not impose a specific storage technology; you can use your existing database or cloud infrastructure (clause 4.1). There is no requirement for a technology like blockchain.<\/li>\n\n\n\n<li>It does not specify a period for storage (clause 3.4).<\/li>\n\n\n\n<li>It does not include any provisions regarding the country where the data will be hosted.<\/li>\n\n\n\n<li>It does not regulate the transition from one primary service provider to another; it only addresses replication between the primary and the backup (clause 4.5).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Protocols, formats, and API calls are subject to sister standards; these <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/dpp-yazilimi-secimi-en-18216-en-18222-en-18223-protokol-api\/\">In our article on protocols, APIs and interoperability<\/a> We are addressing it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Who stores passport data, and where?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Short answer: you or a service provider working on your behalf. The storage obligation rests with the party responsible for creating the passport; this task may also be delegated to DPP service providers authorized by that party (clause 4.1). If you choose not to host the passport yourself, the company hosting it on your behalf is called the main DPP service provider (clause 3.3.1).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u201cThe assumption that &quot;the EU stores my passport in a central system&quot; is therefore incorrect; EN 18221 makes no mention of a central EU data repository. A general point outside the standard: the EU DPP registry envisioned by the ESPR is not designed as a repository containing the full contents of the passport, but rather as a register holding identifiers that can help locate the product and the passport. According to EN 18221, the storage of the passport contents is with you or your service provider (clause 4.1).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The following are the expectations from the stored data:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The data must be accurate and complete, reflecting the current status with all relevant changes incorporated (clause 4.1).<\/li>\n\n\n\n<li>The passport must be accessible online throughout its lifespan according to the protocols in EN 18216 (clause 4.1).<\/li>\n\n\n\n<li>The stored data must be able to produce human and machine-readable representations (such as HTML and JSON) as required by EN 18216 (clause 4.1). In our assessment, simply storing the passport as a PDF file does not meet this requirement.<\/li>\n\n\n\n<li>Data is protected against loss, malicious alteration, and unauthorized access using proven reliable technologies; this obligation applies to both the primary and backup providers (clause 4.1).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The standard is silent on data location: there is no provision stating &quot;must be hosted within the EU&quot; or &quot;can be hosted in T\u00fcrkiye.&quot; The standard does not require this; however, if personal data is present in the passport, the KVKK and GDPR rules for international transfers must be evaluated separately.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Is every change archived?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">As a rule, yes. Archiving begins at the moment the first change is made to the original version of the passport, and all changes to the passport are archived (clause 4.2). The only exception is changes that are explicitly exempted by product group-specific rules; the example given in the standard is real-time sensor data (clause 4.2).<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The standard requires the archive to be kept in two locations: the party creating the passport (or its primary provider) and the backup provider (clause 4.2). The product rules specify which products require a backup (clause 4.3); the standard does not clearly outline how a second copy should be handled for a product where a backup is not required.<\/li>\n\n\n\n<li>All archive versions are retained for the duration of the passport&#039;s life (article 4.2).<\/li>\n\n\n\n<li>A verified and authorized actor should be able to restore a version from a specific date (clause 4.2).<\/li>\n\n\n\n<li>Information in the archive is subject to the same access restrictions as its counterpart in the current passport; a controlled area remains controlled in the archive as well (Article 4.2).<\/li>\n\n\n\n<li>The integrity and authenticity of archive versions are guaranteed according to EN 18246 (clause 4.2).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The standard for archival organization is recommended as ISO 14721 (OAIS, Open Archive Information System), the reference model for long-term digital archives; this is a recommendation, not a requirement (clause 4.2). It also specifies who has access to the data in the archive and in the backup, and in what role. <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 explain. The approach of &quot;the current version is sufficient, we can delete the old ones&quot; is incompatible with this standard.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What is a backup service provider, and why is it necessary?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The backup DPP service provider is the provider that holds the backup copy of the passport (clause 3.3.2). The standard defines DPP service providers as independent third parties authorized by the economic operator that markets or puts the product into service (clause 3.3). When the following conditions are read together, this backup should be considered not as a database backup taken overnight, but as a separate access point serving authorized users.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>It stores the most current version and all necessary previous versions (clause 4.3).<\/li>\n\n\n\n<li>The passport grants access to specially authorized users for its entire validity period (clause 4.3).<\/li>\n\n\n\n<li>It receives changes at a frequency that minimizes data loss. As a standard example, it shows the definition of a maximum recovery point objective (RPO), i.e., the maximum acceptable data loss window; it does not give a number and states that the frequency can be determined separately by product rules (clause 4.5).<\/li>\n\n\n\n<li>Replication must be possible using the lifecycle API in EN 18222; the parties may also agree on another secure method. In any case, transmission is carried out using a protocol compliant with EN 18216 (clause 4.5).<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Is a spare part mandatory for every product? The standard itself does not make it mandatory; it states that a spare part may be required when the product is placed on the market (clause 4.3). Which products it is required for depends on the ESPR and product group rules. Annex ZA also outlines this limit: clauses 4.3 and 4.5 are correlated with ESPR Clause 10(4), but the presumption of conformity applies only to the technical aspects of the spare part, not to the existence of the spare part. Clause 4.5 is also correlated with ESPR Clause 11(c); clauses 4.1, 4.2 and 4.4 are not included in the table (Annex ZA, Table ZA.1).<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happens to the passport if the company withdraws from the market?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The concept of data persistence exists precisely for this scenario: the data remains accessible even if the economic operator that created the passport is no longer active (clause 1). The trigger for the standard is when the economic operator is no longer active in the market; in this case, general access to the passport on the backup provider must be opened (clause 4.3). The rationale for the replication frequency requirement is to minimize data loss in this scenario (clause 4.5).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Digital documents attached to the passport (e.g., user manuals or certificates) are treated with the same logic. The document can be placed inside the passport or linked from the passport; in both cases, it must be accessible via the passport, the user must be able to download and save it on their own device, and the document must remain online until the passport expires (clause 4.4). Even if mandatory documents are provided only via link, it is the responsibility of the backup provider to store and keep them accessible (clause 4.4).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The standard does not define how to identify the \u201cno longer active\u201d status or who will restore general access and by what process. Therefore, we recommend that you define the triggering event, notification path, and transition steps in writing with the backup provider; this is not a requirement of the standard, but our recommendation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Storage time: Why doesn&#039;t the standard provide a specific number?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The standard defines the DPP lifetime as the period during which legislation requires the passport to remain accessible to those entitled to access it, without specifying a number in years (clause 3.4). Retention, archiving, backup access, and additional document requirements are all tied to this period (clauses 4.1, 4.2, 4.3, and 4.4).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Non-standard general information: The duration is determined by the delegated act issued for each product group under the ESPR. Therefore, it is not correct to say &quot;EN 18221 requires the passport to be kept for so many years&quot;. Instead of fixing the duration in a number in the contract, it is safer to use a reference such as &quot;for the duration of the DPP as stipulated by the relevant regulation&quot;. For sector-specific 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<\/a> You can browse our pages.<\/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 the passport yourself or provide it to the main service provider? If you host it yourself, you must meet the storage requirements in section 4.1 on your own infrastructure (clauses 3.3.1 and 4.1).<\/li>\n\n\n\n<li>If your product line requires a backup copy, who will be the backup provider (clause 4.3)?<\/li>\n\n\n\n<li>How will the replication frequency be defined (e.g., with a maximum RPO) and will the replication be performed using the EN 18222 API or another secure method (clause 4.5)?<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Supplier contract: Clauses arising from the standard.<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Generating JSON and HTML representations from stored data (item 4.1).<\/li>\n\n\n\n<li>Archiving all changes except those exempted, maintaining the archive both with you or the main provider and (if applicable) the backup provider for the lifetime of DPP; restoring the version from a specific date to the authorized user (clause 4.2).<\/li>\n\n\n\n<li>How to ensure the integrity of archive versions according to EN 18246 and ISO 14721 (OAIS) compliance (clause 4.2; OAIS recommendation level).<\/li>\n\n\n\n<li>Identity of the backup provider and its status as an independent third party (clauses 3.3 and 3.3.2).<\/li>\n\n\n\n<li>The replication frequency should minimize data loss (the standard example shows the maximum RPO definition; you determine the number in the contract) and the replication should be done using the EN 18222 API (clause 4.5).<\/li>\n\n\n\n<li>Enabling general access from backup when the operator is inactive (clause 4.3).<\/li>\n\n\n\n<li>Supplementary documents must be kept in downloadable format and permanently, with backups of those deemed necessary (Article 4.4).<\/li>\n<\/ul>\n\n\n\n<h3 class=\"wp-block-heading\">Things not regulated by the standard but that should be included in the contract.<\/h3>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The country where the data is stored and safeguards regarding the transfer of personal data.<\/li>\n\n\n\n<li>If you switch to another provider, what format and timeframe will all versions and documents be delivered in? The issue of dependency on the supplier regarding identity matters. <a href=\"https:\/\/aesinn.com\/en\/uyum-denetim-due-diligence-danismanligi\/dijital-urun-pasaportu-dpp\/en-18219-dpp-benzersiz-tanimlayici-urun-operator-tesis-kimligi\/\">in our singular descriptive text<\/a> We are addressing it.<\/li>\n\n\n\n<li>\u201cThe definition of &quot;inactive&quot; status, who decides on it, and the steps to make it generally accessible.<\/li>\n\n\n\n<li>The backup provider&#039;s own continuity assurance and retention period must be written with reference to the product specification.<\/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>Follow the ESPR regulations for your product line; they should clarify the DPP lifecycle, backup requirements, and any additional rules regarding replication frequency, with any exemptions.<\/li>\n\n\n\n<li>Determine which systems (ERP, PLM, quality) the passport data comes from and how often it changes; the frequency of changes determines the archive volume.<\/li>\n\n\n\n<li>Send the above two lists as written questions to prospective suppliers and compare their answers using the item numbers.<\/li>\n\n\n\n<li>List the manuals, certificates, and test reports you will attach to the passport; check that they are in a downloadable format.<\/li>\n\n\n\n<li>Turn the scenario for the cessation of the activity into a written plan.<\/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\/dpp-yazilimi-secimi-en-18216-en-18222-en-18223-protokol-api\/\">When Choosing DPP Software: Protocol and API according to EN 18216, 18222 and 18223.<\/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\">Will the EU conceal the DPP&#039;s output?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. The passport is stored by the actor that created it or the DPP service provider working on its behalf; the architecture is decentralized (EN 18221, clauses 1 and 4.1). The standard does not refer to a centralized EU data repository.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How many years do I need to keep my passport?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It does not provide a standard figure. The DPP defines its lifespan as the period during which legislation requires the passport to remain accessible (clause 3.4); archive versions are also retained for this period (clause 4.2). As non-standard information, it is stipulated that the period will be determined by the product group regulation under the ESPR.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I delete the old version of my passport when I update it?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. Every change from the first one onwards is archived; the archive is kept by you or your primary provider and, if applicable, the backup provider for the lifetime of the DPP. Only changes that are explicitly exempted by the product rules, such as real-time sensor data, may be excluded (clause 4.2).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Is a backup service provider mandatory for every product?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The standard itself does not mandate this; it states that a backup copy may be requested (clause 4.3). Which products require it depends on the ESPR and product group regulations. When a backup is requested, the technical specifications are in clauses 4.3 and 4.5.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What will happen to the passports if our company ceases operations?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">When the economic operator is no longer active in the market, general access to the passport must be opened with the replacement provider (clause 4.3). How this is determined is not defined in the standard; it must be specified in the contract with the replacement provider.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can I store my passport data on a server in T\u00fcrkiye?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">EN 18221 does not contain any provisions regarding data location; it neither prohibits nor encourages it. As a non-standard note, if personal data is included in the passport, the KVKK and GDPR transfer rules should be considered separately.<\/p>","protected":false},"excerpt":{"rendered":"<p>You or your service provider will store the DPP data, not the EU. We explain the archiving, backup provider, and persistence rules of EN 18221, the retention period which the standard does not specify, and the clauses that should be included in the supplier contract.<\/p>","protected":false},"author":1,"featured_media":6507,"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 18221: DPP Data Storage, Archiving, Backup and Persistence","description":"Who stores the DPP data according to EN 18221, where, and for how long? What about the archive of every change, the backup service provider, and what happens if the company withdraws from the market?"},"_pplb_hide_from_list":false,"footnotes":""},"class_list":["post-6508","page","type-page","status-publish","has-post-thumbnail","hentry"],"acf":[],"taxonomy_info":[],"featured_image_src_large":["https:\/\/aesinn.com\/wp-content\/uploads\/dpp-en18221-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\/6508","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=6508"}],"version-history":[{"count":1,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages\/6508\/revisions"}],"predecessor-version":[{"id":6520,"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/pages\/6508\/revisions\/6520"}],"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\/6507"}],"wp:attachment":[{"href":"https:\/\/aesinn.com\/en\/wp-json\/wp\/v2\/media?parent=6508"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}