{"id":18572,"date":"2025-12-22T17:27:57","date_gmt":"2025-12-22T16:27:57","guid":{"rendered":"https:\/\/dev.databack.fr\/non-categorise\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/"},"modified":"2026-03-30T14:14:07","modified_gmt":"2026-03-30T12:14:07","slug":"ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025","status":"publish","type":"post","link":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/","title":{"rendered":"DDoS cyberattack against La Poste and La Banque Postale: understanding the incident of December 22, 2025"},"content":{"rendered":"\n

On the morning of Monday December 22, 2025<\/strong>, aDDoS attack severely disrupted the La Poste and La Banque Postale groups<\/strong>. According to the information made public, the interconnection between a datacenter and the Internet was targeted, rendering numerous online services inaccessible from around 6:30 a.m., just 48 hours before Christmas Eve. At the same time, other establishments such as Caisse d’\u00c9pargne and Banque Populaire reported slowdowns and “malfunctioning” of their services. <\/p>\n\n

This article takes a structured look at what we know about the incident, how a DDoS attack works and the lessons to be learned in terms of service continuity and digital security.<\/p>\n\n

<\/div>\n\n

Key points to remember<\/strong><\/h2>\n\n
<\/div>\n\n
    \n
  • On the morning of December 22, 2025, a DDoS (distributed denial of service) cyber attack hit La Poste and La Banque Postale<\/strong>.<\/li>\n\n\n\n
  • The attack is believed to have targeted the interconnection between one of the Group’s datacenters and the Internet, disrupting a large number of online services.<\/li>\n\n\n\n
  • These included<\/strong> access to La Banque Postale accounts, Colissimo services (franking, labeling, automated delivery) and the Digiposte digital safe.<\/li>\n\n\n\n
  • Payments (by card, bank transfer, etc.)<\/strong> were presented as not being concerned, as they use a separate technical flow, separate from the targeted datacenter.<\/li>\n\n\n\n
  • Faced with the scale of the blockade, the group’s management authorized the closure of some post offices<\/strong>, while some parcel deliveries could still be carried out manually, “the old-fashioned way”.<\/li>\n\n\n\n
  • This followed a first outage on Saturday December 20<\/strong>, already attributed to a DDoS attack.<\/li>\n\n\n\n
  • Two<\/strong> other French banks, Caisse d’\u00c9pargne and Banque Populaire<\/strong>, experienced slowdowns at the same time, which they attributed to a malfunction, without confirming a cyberattack.<\/li>\n\n\n\n
  • The incident raises questions about the scale of the attack, the effectiveness of mitigation measures and the possible involvement of organized actors, but there is no public evidence at this stage.<\/li>\n<\/ul>\n\n
    <\/div>\n
    \n
    \"cyberattack<\/figure>\n<\/div>\n

    Timeline: from the first disruptions on December 20 to the major incident on December 22<\/strong><\/h2>\n\n
    <\/div>\n\n

    Saturday, December 20: a first warning<\/strong><\/h3>\n\n
    <\/div>\n\n

    According to the information made public, the first signs of fragility appeared on Saturday December 20, 2025. La Poste and La Banque Postale services were unavailable<\/strong> for several hours. The technical information available indicates that this was already a DDoS attack, before a gradual return to normal during the day. <\/p>\n\n

    With hindsight, this episode appears to be a precursor: the attackers already seemed to be testing the resilience of the Group’s infrastructures, before striking harder two days later.<\/p>\n\n

    <\/div>\n\n

    Monday morning, December 22: massive blockade 48 hours before Christmas<\/strong><\/h3>\n\n
    <\/div>\n\n

    On the morning of Monday December 22, 2025, the situation took a turn for the worse. From around 6:30 a.m., access to many of La Poste group’s services was disrupted or impossible: <\/p>\n\n

      \n
    • many customers unable to connect to their La Banque Postale accounts;<\/li>\n\n\n\n
    • breakdowns affecting Colissimo services, notably franking, labelling and part of the automated parcel distribution system;<\/li>\n\n\n\n
    • reported unavailability of the Digiposte digital safe;<\/li>\n\n\n\n
    • more generally, difficulties accessing La Poste’s various online services.<\/li>\n<\/ul>\n\n

      The incident comes at a particularly sensitive time: the final stretch before Christmas, when many individuals rely on La Poste and Colissimo to send or receive their presents. The combination of the seasonal peak in activity and the attack mechanically reinforces the impact felt by users. <\/p>\n\n

      <\/div>\n\n

      Services affected and services preserved<\/strong><\/h2>\n\n
      <\/div>\n\n

      Over the hours, a relatively coherent picture has emerged from technical information and user testimonials. Here is a summary, based on the information available on December 22, 2025<\/strong>: <\/p>\n\n

      Service type<\/strong><\/td>Situation on December 22 (based on available information)<\/strong><\/td><\/tr>
      Access to La Banque Postale online accounts<\/td>Severely disrupted or impossible for many customers.<\/td><\/tr>
      La Poste web services (website, customer areas, etc.)<\/td>Severely disrupted, with many unavailabilities reported.<\/td><\/tr>
      Colissimo (postage, labelling, tracking)<\/td>Postage and labeling largely blocked; disruptions to automated distribution lines.<\/td><\/tr>
      Parcel delivery<\/td>In some cases, this can be done manually, without an electronic terminal, but with degraded operation.<\/td><\/tr>
      Digiposte (digital safe)<\/td>Service reported as unavailable or difficult to access.<\/td><\/tr>
      Physical post offices<\/td>Operations deteriorated; authorization given to close certain offices in the face of difficulties.<\/td><\/tr>
      Group-related payments (cards, transfers, etc.)<\/td>Presented as unaffected, as they use a separate flow that does not pass through the targeted datacenter.<\/td><\/tr>
      Caisse d’\u00c9pargne and Banque Populaire<\/td>Slowdowns and malfunctions reported; establishments speak of an incident, without confirming a DDoS cyberattack.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n

      This table clearly shows the systemic nature of the affected interconnection point: by targeting a network node, the attack had a transversal impact on many of the group’s online services.<\/p>\n\n

      <\/div>\n\n

      How La Poste and La Banque Postale reacted<\/strong><\/h2>\n\n
      <\/div>\n\n

      In view of the seriousness of the situation, several operational measures have been reported:<\/p>\n\n

        \n
      • The management of the La Poste group<\/strong> has agreed to close certain post offices when the scale of the disruption no longer allows normal service;<\/li>\n\n\n\n
      • However, it was pointed out that parcel deliveries could still be made manually, i.e. without using the<\/strong> usual electronic terminals<\/strong>, in order to limit delays as far as possible;<\/li>\n\n\n\n
      • Communications emphasized the fact that payment flows were isolated from the affected datacenter, enabling transactions (card payments, transfers, etc.) to continue uninterrupted despite the breakdown of online services.<\/li>\n<\/ul>\n\n

        These elements highlight an organization that is already partially segmented: critical payment flows obviously follow a different technical path from that of web services, which limits the immediate impact on the payment chain in the event of a problem in a datacenter.<\/p>\n\n

        <\/div>\n\n

        Just a DDoS incident? What we can deduce (and what we don’t) <\/strong><\/h2>\n\n
        <\/div>\n\n

        In exchanges between Internet users and commentators, one question often comes up: if the incident is indeed “only” linked to a DDoS, is it really serious? And is this explanation sufficient to describe what happened? <\/p>\n\n

        <\/div>\n\n

        The reassuring elements<\/strong><\/h3>\n\n
        <\/div>\n\n

        On the basis of the information made public at the time, several points can be considered relatively reassuring:<\/p>\n\n

          \n
        • the communications refer to a DDoS attack<\/strong> targeting the network interconnection; there is no mention, at this stage, of any proven intrusion into internal systems or data theft;<\/li>\n\n\n\n
        • the fact that payments have been maintained via a separate flow indicates an architecture where certain critical bricks are separated from consumer online services;<\/li>\n\n\n\n
        • Internal banking operations<\/strong>(clearing, interbank transfers, etc.) can, in many cases, be based on different circuits from the web or mobile interfaces consulted by customers.<\/li>\n<\/ul>\n\n

          It’s important to point out that the absence of any public mention does not mean that there was no internal technical incident, but simply that no data leak or compromise was presented as an established fact at the time the incident was commented on.<\/p>\n\n

          <\/div>\n\n

          Legitimate questions still unanswered<\/strong><\/h3>\n\n
          <\/div>\n\n

          On the other hand, a number of grey areas remain, raising legitimate questions:<\/p>\n\n

            \n
          • A large-scale DDoS attack is usually expected by large groups, which generally have mitigation solutions in place (specialized suppliers, filtering, redundancy, etc.). The scale of the disruption therefore raises questions about the power of the attack or the exact configuration of the protection in place;<\/li>\n\n\n\n
          • the fact that similar disruptions were observed on December 20, and again on December 22<\/strong>, raises questions about a targeted campaign rather than a single isolated incident;<\/li>\n\n\n\n
          • Some observers are questioning the possibility of a more complex attack than DDoS alone, or of a combination of cyber attack<\/strong> and technical failure, although there is no public evidence to confirm this;<\/li>\n\n\n\n
          • As with many incidents of this type, the question of the possible involvement of organized, or even state-sponsored, actors is being raised against a backdrop of geopolitical tensions, but for the moment this is nothing more than speculation with no public backing.<\/li>\n<\/ul>\n\n

            In short<\/strong>, the main hypothesis remains that of a massive, repeated DDoS attack, but the scale of the blockage and its context call for an in-depth examination of resilience mechanisms and possible scenarios.<\/p>\n\n

            <\/div>\n\n

            What does this mean for customers?<\/strong><\/h2>\n\n
            <\/div>\n\n

            For individuals and businesses alike, the practical repercussions of such an incident can be seen above all in the sudden loss of access to services that have become essential to daily life.<\/p>\n\n

              \n
            • La Banque Postale customers<\/strong>: unable, sometimes for several hours, to connect to the customer area to consult accounts, make transfers or manage day-to-day transactions.<\/li>\n\n\n\n
            • La Poste users<\/strong>: difficulty franking letters or parcels via online services and certain terminals, inability to print Colissimo labels, disrupted parcel tracking.<\/li>\n\n\n\n
            • Digiposte users<\/strong>: temporary unavailability of their digital safe, with the frustration of not being able to access certain documents stored online.<\/li>\n\n\n\n
            • Businesses, e-tailers and professionals<\/strong>: risk of additional logistical delays in the run-up to Christmas, more complex management of customer shipments and commercial relations.<\/li>\n<\/ul>\n\n
              <\/div>\n\n

              What’s more,the repetition of these incidents<\/strong> (on December 20 and 22) may be generating a feeling of uncertainty among customers, who are questioning the capacity of the infrastructure to absorb this type of shock in the future.<\/p>\n\n

              <\/div>\n\n

              Specific impact on banking operations<\/strong><\/h3>\n\n
              <\/div>\n\n

              An important point is that the payments themselves (card payments, interbank transfers, etc.) were described as functioning normally, thanks to their routing via a separate flow from the attacked datacenter.<\/p>\n\n

              <\/div>\n\n

              In concrete terms, this means that :<\/p>\n\n

                \n
              • in-store or online transactions, already initiated, could continue to run even if customers were unable to connect to their web or mobile interface;<\/li>\n\n\n\n
              • On the other hand, it was more difficult, if not impossible, to prepare new operations (making a transfer, adding a beneficiary…) from the customer area, as long as access remained saturated.<\/li>\n<\/ul>\n\n
                <\/div>\n\n

                For users, the main inconvenience was the inability to interact with their accounts in real time, rather than a complete blockage of the underlying financial flows.<\/p>\n\n

                <\/div>\n\n
                  \n
                • they provide access to a multitude of consumer and professional services;<\/li>\n\n\n\n
                • their unavailability immediately translates into visible blockages for millions of users;<\/li>\n\n\n\n
                • They are prime targets for attackers seeking to disrupt, destabilize or exert pressure.<\/li>\n<\/ul>\n\n
                  <\/div>\n\n

                  This episode illustrates the need for operators of essential services to have robust continuity plans and DDoS mitigation solutions, regularly tested and adapted to evolving threats.<\/p>\n","protected":false},"excerpt":{"rendered":"

                  Latest news.<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[133],"tags":[],"ppma_author":[144],"class_list":["post-18572","post","type-post","status-publish","format-standard","hentry","category-blog","author-samuel-durand-en"],"yoast_head":"\nCyberAttack at La Poste and Banque Postale<\/title>\n<meta name=\"description\" content=\"Consequences of the cyberattack on La Poste and Banque Postale: parcel and mail delivery severely disrupted.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"CyberAttack at La Poste and Banque Postale\" \/>\n<meta property=\"og:description\" content=\"Consequences of the cyberattack on La Poste and Banque Postale: parcel and mail delivery severely disrupted.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/\" \/>\n<meta property=\"og:site_name\" content=\"Databack\" \/>\n<meta property=\"article:published_time\" content=\"2025-12-22T16:27:57+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-03-30T12:14:07+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/dev.databack.fr\/wp-content\/uploads\/2025\/12\/la-poste-cyberattaque.png\" \/>\n\t<meta property=\"og:image:width\" content=\"600\" \/>\n\t<meta property=\"og:image:height\" content=\"400\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Samuel Durand\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Samuel Durand\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"8 minutes\" \/>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"CyberAttack at La Poste and Banque Postale","description":"Consequences of the cyberattack on La Poste and Banque Postale: parcel and mail delivery severely disrupted.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/","og_locale":"en_US","og_type":"article","og_title":"CyberAttack at La Poste and Banque Postale","og_description":"Consequences of the cyberattack on La Poste and Banque Postale: parcel and mail delivery severely disrupted.","og_url":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/","og_site_name":"Databack","article_published_time":"2025-12-22T16:27:57+00:00","article_modified_time":"2026-03-30T12:14:07+00:00","og_image":[{"width":600,"height":400,"url":"https:\/\/dev.databack.fr\/wp-content\/uploads\/2025\/12\/la-poste-cyberattaque.png","type":"image\/png"}],"author":"Samuel Durand","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Samuel Durand","Est. reading time":"8 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/#article","isPartOf":{"@id":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/"},"author":{"name":"Samuel Durand","@id":"https:\/\/dev.databack.fr\/en\/#\/schema\/person\/531f3f19be2ec1ba9dcf678d099e2c51"},"headline":"DDoS cyberattack against La Poste and La Banque Postale: understanding the incident of December 22, 2025","datePublished":"2025-12-22T16:27:57+00:00","dateModified":"2026-03-30T12:14:07+00:00","mainEntityOfPage":{"@id":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/"},"wordCount":1613,"publisher":{"@id":"https:\/\/dev.databack.fr\/en\/#organization"},"image":{"@id":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/#primaryimage"},"thumbnailUrl":"https:\/\/dev.databack.fr\/wp-content\/uploads\/2025\/12\/la-poste-cyberattaque.png","articleSection":["BLOG"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/","url":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/","name":"CyberAttack at La Poste and Banque Postale","isPartOf":{"@id":"https:\/\/dev.databack.fr\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/#primaryimage"},"image":{"@id":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/#primaryimage"},"thumbnailUrl":"https:\/\/dev.databack.fr\/wp-content\/uploads\/2025\/12\/la-poste-cyberattaque.png","datePublished":"2025-12-22T16:27:57+00:00","dateModified":"2026-03-30T12:14:07+00:00","description":"Consequences of the cyberattack on La Poste and Banque Postale: parcel and mail delivery severely disrupted.","breadcrumb":{"@id":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/#primaryimage","url":"https:\/\/dev.databack.fr\/wp-content\/uploads\/2025\/12\/la-poste-cyberattaque.png","contentUrl":"https:\/\/dev.databack.fr\/wp-content\/uploads\/2025\/12\/la-poste-cyberattaque.png"},{"@type":"BreadcrumbList","@id":"https:\/\/dev.databack.fr\/en\/blog\/ddos-cyberattack-against-la-poste-and-la-banque-postale-understanding-the-incident-of-december-22-2025\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"R\u00e9cup\u00e9ration de donn\u00e9es","item":"https:\/\/dev.databack.fr\/en\/"},{"@type":"ListItem","position":2,"name":"DDoS cyberattack against La Poste and La Banque Postale: understanding the incident of December 22, 2025"}]},{"@type":"WebSite","@id":"https:\/\/dev.databack.fr\/en\/#website","url":"https:\/\/dev.databack.fr\/en\/","name":"Databack","description":"Laboratoire fran\u00e7ais de traitement de donn\u00e9es sensibles et volumineuses","publisher":{"@id":"https:\/\/dev.databack.fr\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/dev.databack.fr\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/dev.databack.fr\/en\/#organization","name":"Datenabruf","url":"https:\/\/dev.databack.fr\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/dev.databack.fr\/en\/#\/schema\/logo\/image\/","url":"https:\/\/dev.databack.fr\/wp-content\/uploads\/2025\/06\/favicon.png","contentUrl":"https:\/\/dev.databack.fr\/wp-content\/uploads\/2025\/06\/favicon.png","width":512,"height":512,"caption":"Datenabruf"},"image":{"@id":"https:\/\/dev.databack.fr\/en\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/dev.databack.fr\/en\/#\/schema\/person\/531f3f19be2ec1ba9dcf678d099e2c51","name":"Samuel Durand","description":"Ing\u00e9nieur en g\u00e9nie \u00e9lectronique, Samuel Durand d\u00e9bute sa carri\u00e8re dans le domaine de la r\u00e9cup\u00e9ration de donn\u00e9es, o\u00f9 il se forge une solide expertise au sein d\u2019une entreprise pendant plus de quatre ans. En 2004, il cr\u00e9e DATABACK, un laboratoire ind\u00e9pendant enti\u00e8rement tourn\u00e9 vers le traitement et la r\u00e9cup\u00e9ration de donn\u00e9es. Il occupe aujourd\u2019hui le poste de directeur technique. Sous sa direction, DATABACK a mis au point des solutions innovantes pour restaurer des volumes importants de donn\u00e9es sensibles. Face \u00e0 la multiplication des cyberattaques, et en particulier des ran\u00e7ongiciels, il d\u00e9veloppe avec son \u00e9quipe des outils et des logiciels capables de traiter ces situations complexes, dans le respect des contraintes techniques et de confidentialit\u00e9 de ses clients.","sameAs":["https:\/\/www.linkedin.com\/in\/samuel-durand-1a78877\/"]}]}},"authors":[{"term_id":144,"user_id":0,"is_guest":1,"slug":"samuel-durand-en","display_name":"Samuel Durand","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/?s=96&d=mm&r=g","author_category":"","first_name":"","last_name":"","user_url":"","job_title":"","description":""}],"_links":{"self":[{"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/posts\/18572","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/comments?post=18572"}],"version-history":[{"count":4,"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/posts\/18572\/revisions"}],"predecessor-version":[{"id":18592,"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/posts\/18572\/revisions\/18592"}],"wp:attachment":[{"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/media?parent=18572"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/categories?post=18572"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/tags?post=18572"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/dev.databack.fr\/en\/wp-json\/wp\/v2\/ppma_author?post=18572"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}