{"id":479651,"date":"2023-08-09T10:43:04","date_gmt":"2023-08-09T10:43:04","guid":{"rendered":""},"modified":"2023-09-05T11:19:17","modified_gmt":"2023-09-05T11:19:17","slug":"webhook","status":"publish","type":"wiki","link":"https:\/\/oneproxy.pro\/tr\/wiki\/webhook\/","title":{"rendered":"Web kancas\u0131"},"content":{"rendered":"

Web kancas\u0131, web geli\u015ftirmede kullan\u0131lan ve farkl\u0131 web uygulamalar\u0131 aras\u0131nda ger\u00e7ek zamanl\u0131 ileti\u015fim ve veri al\u0131\u015fveri\u015fini sa\u011flayan bir mekanizmad\u0131r. Belirli olaylar veya tetikleyiciler meydana geldi\u011finde bir uygulaman\u0131n ba\u015fka bir uygulamaya otomatik olarak veri g\u00f6ndermesine olanak tan\u0131r. Web kancalar\u0131 modern web hizmetleri i\u00e7in gereklidir ve \u00e7e\u015fitli \u00e7evrimi\u00e7i platformlar aras\u0131nda kusursuz entegrasyon ve otomasyonun sa\u011flanmas\u0131nda \u00e7ok \u00f6nemli bir rol oynar.<\/p>\n

Webhook'un k\u00f6keninin tarihi ve ilk s\u00f6z\u00fc<\/h2>\n

Web kancalar\u0131 kavram\u0131, web geli\u015ftirmede kullan\u0131lan geleneksel istek-yan\u0131t modelini geli\u015ftirmenin bir yolu olarak tan\u0131t\u0131ld\u0131klar\u0131 2000'li y\u0131llar\u0131n ba\u015flar\u0131na kadar uzanmaktad\u0131r. Web kancalar\u0131n\u0131n ilk s\u00f6z\u00fc Jeff Lindsay'in 2007'deki bir blog g\u00f6nderisine kadar uzanabilir; burada onlardan "HTTP-POST geri aramalar\u0131" olarak s\u00f6z edilmi\u015ftir. "Webhook" terimi zamanla pop\u00fclerlik kazand\u0131 ve art\u0131k teknoloji end\u00fcstrisinde yayg\u0131n olarak tan\u0131n\u0131yor ve kullan\u0131l\u0131yor.<\/p>\n

Webhook hakk\u0131nda ayr\u0131nt\u0131l\u0131 bilgi: Webhook konusunu geni\u015fletme<\/h2>\n

Web kancalar\u0131 basit bir \u00f6nermeye dayanmaktad\u0131r: Bir uygulamada bir olay meydana geldi\u011finde, ba\u015fka bir uygulama taraf\u0131ndan sa\u011flanan bir URL'ye bir HTTP iste\u011fi g\u00f6ndererek bir eylemi veya bildirimi tetikler. Web kancalar\u0131n\u0131 entegre etme s\u00fcreci a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 i\u00e7erir:<\/p>\n

    \n
  1. \n

    Olay Olu\u015fumu: \u0130lk ad\u0131mda kaynak uygulamada bir olay ger\u00e7ekle\u015fir. Uygulama geli\u015ftiricisinin bir web kancas\u0131n\u0131 tetiklemek i\u00e7in yap\u0131land\u0131rd\u0131\u011f\u0131 herhangi bir eylem veya etkinlik olabilir.<\/p>\n<\/li>\n

  2. \n

    HTTP \u0130ste\u011fi: Olay meydana geldi\u011finde kaynak uygulama, hedef uygulaman\u0131n webhook URL'sine bir HTTP POST iste\u011fi g\u00f6nderir.<\/p>\n<\/li>\n

  3. \n

    Y\u00fck Verisi: HTTP iste\u011fi genellikle olayla ilgili, genellikle veri y\u00fck\u00fc olarak adland\u0131r\u0131lan ilgili verileri i\u00e7erir. Hedef uygulama bu veriyi i\u015fler ve buna g\u00f6re gerekli eylemleri ger\u00e7ekle\u015ftirir.<\/p>\n<\/li>\n

  4. \n

    Yan\u0131t \u0130\u015fleme: Verileri i\u015fledikten sonra hedef uygulama, web kancas\u0131n\u0131n ba\u015far\u0131l\u0131 bir \u015fekilde al\u0131nd\u0131\u011f\u0131n\u0131 onaylamak i\u00e7in bir onayla veya iste\u011fe ba\u011fl\u0131 olarak ilgili bilgilerle yan\u0131t verebilir.<\/p>\n<\/li>\n<\/ol>\n

    Web kancalar\u0131 \u00e7ok y\u00f6nl\u00fcd\u00fcr ve otomatik bildirimler, veri senkronizasyonu ve ger\u00e7ek zamanl\u0131 g\u00fcncellemeler gibi \u00e7e\u015fitli ama\u00e7larla yayg\u0131n olarak kullan\u0131l\u0131r.<\/p>\n

    Webhook'un i\u00e7 yap\u0131s\u0131: Webhook nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/h2>\n

    Bir webhook'un i\u00e7 yap\u0131s\u0131 \u00fc\u00e7 ana bile\u015fenden olu\u015fur:<\/p>\n

      \n
    1. \n

      Olay Kayna\u011f\u0131: Olay kayna\u011f\u0131, olaylar\u0131n kaynakland\u0131\u011f\u0131 uygulama veya hizmettir. Belirli etkinlikleri veya de\u011fi\u015fiklikleri alg\u0131lar ve olay tetikleyicisini olu\u015fturur. Bu uygulaman\u0131n webhook URL'sine HTTP istekleri yapabilmesi gerekir.<\/p>\n<\/li>\n

    2. \n

      Webhook URL'si: Webhook URL'si, etkinlik bildirimlerini almak isteyen hedef uygulama veya sunucu taraf\u0131ndan sa\u011flan\u0131r. Olay kayna\u011f\u0131n\u0131n HTTP POST isteklerini g\u00f6ndermesi i\u00e7in bir u\u00e7 nokta g\u00f6revi g\u00f6r\u00fcr.<\/p>\n<\/li>\n

    3. \n

      Web Kancas\u0131 \u0130\u015fleyicisi: Web kancas\u0131 i\u015fleyicisi hedef sunucuda bulunur ve gelen web kancas\u0131 isteklerini i\u015flemekten sorumludur. HTTP iste\u011finden y\u00fck verilerini \u00e7\u0131kar\u0131r, yorumlar ve al\u0131nan bilgilere g\u00f6re uygun eylemleri tetikler.<\/p>\n<\/li>\n<\/ol>\n

      Webhook'un temel \u00f6zelliklerinin analizi<\/h2>\n

      Web kancalar\u0131, web uygulamalar\u0131 aras\u0131nda ger\u00e7ek zamanl\u0131 ileti\u015fim ve entegrasyon i\u00e7in onlar\u0131 tercih edilen bir se\u00e7enek haline getiren \u00e7e\u015fitli temel \u00f6zellikler sunar:<\/p>\n

        \n
      1. \n

        Ger\u00e7ek Zamanl\u0131 G\u00fcncellemeler: Web kancalar\u0131, uygulamalar aras\u0131nda an\u0131nda ileti\u015fime olanak tan\u0131yarak ilgili olaylar meydana geldi\u011finde ger\u00e7ek zamanl\u0131 g\u00fcncellemeler sa\u011flar.<\/p>\n<\/li>\n

      2. \n

        Hafif ve Verimli: Web kancalar\u0131, hafif ve verimli olan HTTP POST isteklerini kullan\u0131r ve ileti\u015fimle ilgili ek y\u00fck\u00fc azalt\u0131r.<\/p>\n<\/li>\n

      3. \n

        \u00d6l\u00e7eklenebilirlik: Web kancalar\u0131, birden fazla olay tetikleyicisini y\u00f6netebildikleri ve i\u015f y\u00fck\u00fcn\u00fc \u00e7e\u015fitli hedef uygulamalar aras\u0131nda da\u011f\u0131tabildikleri i\u00e7in olduk\u00e7a \u00f6l\u00e7eklenebilirdir.<\/p>\n<\/li>\n

      4. \n

        Olay Odakl\u0131 Mimari: Web kancalar\u0131, olay odakl\u0131 bir mimariyi takip ederek uygulamalar aras\u0131nda gev\u015fek ba\u011flant\u0131y\u0131 te\u015fvik eder ve daha kolay entegrasyonu kolayla\u015ft\u0131r\u0131r.<\/p>\n<\/li>\n<\/ol>\n

        Web Kancas\u0131 T\u00fcrleri<\/h2>\n

        Web kancalar\u0131 i\u015flevlerine ve uygulamalar\u0131na g\u00f6re kategorize edilebilir. A\u015fa\u011f\u0131da baz\u0131 yayg\u0131n web kancas\u0131 t\u00fcrleri verilmi\u015ftir:<\/p>\n\n\n\n\n\n\n\n\n
        Tip<\/th>\nTan\u0131m<\/th>\n<\/tr>\n<\/thead>\n
        Gelen Web Kancalar\u0131<\/td>\nHarici bir kaynaktan belirli bir uygulama veya hizmete veri ve bildirim g\u00f6ndermek i\u00e7in kullan\u0131l\u0131r. Genellikle ger\u00e7ek zamanl\u0131 uyar\u0131lar ve g\u00fcncellemeler i\u00e7in kullan\u0131l\u0131r.<\/td>\n<\/tr>\n
        Giden Web Kancalar\u0131<\/td>\nBir uygulama veya hizmet taraf\u0131ndan tetiklenir ve verileri harici bir URL'ye g\u00f6nderir. Genellikle veri senkronizasyonu ve \u00fc\u00e7\u00fcnc\u00fc taraf sistemlerle ileti\u015fim i\u00e7in kullan\u0131l\u0131r.<\/td>\n<\/tr>\n
        Web Kancalar\u0131n\u0131 Ters \u00c7evirme<\/td>\nHedef uygulama taraf\u0131ndan ba\u015flat\u0131l\u0131r ve kaynak uygulaman\u0131n gerekti\u011finde belirli verileri g\u00f6ndermesini talep eder. Hedef uygulaman\u0131n kaynak uygulamaya do\u011frudan eri\u015femedi\u011fi senaryolarda kullan\u0131\u015fl\u0131d\u0131r.<\/td>\n<\/tr>\n
        S\u0131ral\u0131 Web Kancalar\u0131<\/td>\nBir web kancas\u0131n\u0131n \u00e7\u0131kt\u0131s\u0131n\u0131n di\u011ferini tetikledi\u011fi bir dizi eylem olu\u015fturmak i\u00e7in birden fazla web kancas\u0131n\u0131 birbirine zincirlemek.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

        Webhook'u kullanma yollar\u0131, kullan\u0131mla ilgili sorunlar ve \u00e7\u00f6z\u00fcmleri<\/h2>\n

        Web kancalar\u0131 \u00e7e\u015fitli alanlardaki uygulamalar\u0131 bulur ve kullan\u0131m senaryolar\u0131n\u0131 kullan\u0131r:<\/p>\n

          \n
        1. \n

          Ger\u00e7ek Zamanl\u0131 Bildirimler: Web kancalar\u0131 genellikle e-posta uyar\u0131lar\u0131, anl\u0131k mesajlar ve anl\u0131k bildirimler gibi ger\u00e7ek zamanl\u0131 bildirimleri kullan\u0131c\u0131lara veya di\u011fer uygulamalara iletmek i\u00e7in kullan\u0131l\u0131r.<\/p>\n<\/li>\n

        2. \n

          Veri Senkronizasyonu: Farkl\u0131 sistemler aras\u0131nda veri senkronizasyonunu kolayla\u015ft\u0131rarak bilgilerin t\u00fcm entegre platformlarda g\u00fcncel kalmas\u0131n\u0131 sa\u011flarlar.<\/p>\n<\/li>\n

        3. \n

          Otomasyon ve \u0130\u015f Ak\u0131\u015flar\u0131: Web kancalar\u0131, tekrarlanan g\u00f6revlerin otomatikle\u015ftirilmesinde ve belirli olaylara dayal\u0131 eylemleri tetikleyen i\u015f ak\u0131\u015flar\u0131n\u0131n olu\u015fturulmas\u0131nda hayati bir rol oynar.<\/p>\n<\/li>\n

        4. \n

          S\u00fcrekli Entegrasyon ve Da\u011f\u0131t\u0131m (CI\/CD): Web kancalar\u0131, CI\/CD i\u015flem hatlar\u0131n\u0131n ayr\u0131lmaz bir par\u00e7as\u0131d\u0131r ve kod de\u011fi\u015fiklikleri havuzlara g\u00f6nderildi\u011finde otomatik da\u011f\u0131t\u0131mlara ve testlere olanak tan\u0131r.<\/p>\n<\/li>\n<\/ol>\n

          Web kancalar\u0131yla kar\u015f\u0131la\u015f\u0131lan yayg\u0131n sorunlar \u015funlard\u0131r:<\/p>\n

            \n
          1. \n

            G\u00fcvenlik Kayg\u0131lar\u0131: Web kancalar\u0131 g\u00fcvenlik a\u00e7\u0131klar\u0131n\u0131 a\u00e7\u0131\u011fa \u00e7\u0131karabilir ve g\u00fcvenli bir \u015fekilde uygulanmad\u0131\u011f\u0131 takdirde potansiyel g\u00fcvenlik tehditlerine yol a\u00e7abilir.<\/p>\n<\/li>\n

          2. \n

            Teslim Hatalar\u0131: Hedef sunucu kullan\u0131lam\u0131yorsa veya yan\u0131t vermiyorsa, web kancalar\u0131 verileri teslim edemeyebilir ve bu da olaylar\u0131n ka\u00e7\u0131r\u0131lmas\u0131na neden olabilir.<\/p>\n<\/li>\n

          3. \n

            Yeniden Denemeleri \u0130\u015fleme: Ba\u015far\u0131s\u0131z teslimat giri\u015fimlerini ele almak i\u00e7in uygun yeniden deneme mekanizmalar\u0131n\u0131n sa\u011flanmas\u0131, veri kayb\u0131n\u0131 \u00f6nlemek a\u00e7\u0131s\u0131ndan \u00e7ok \u00f6nemlidir.<\/p>\n<\/li>\n

          4. \n

            Y\u00fck Do\u011frulamas\u0131: Gelen y\u00fck verilerinin do\u011frulanmas\u0131 ve temizlenmesi, potansiyel veri manip\u00fclasyonu ve ekleme sald\u0131r\u0131lar\u0131n\u0131 \u00f6nlemek i\u00e7in \u00e7ok \u00f6nemlidir.<\/p>\n<\/li>\n<\/ol>\n

            Ana \u00f6zellikler ve benzer terimlerle di\u011fer kar\u015f\u0131la\u015ft\u0131rmalar<\/h2>\n\n\n\n\n\n\n\n\n\n
            karakteristik<\/th>\nWeb kancas\u0131<\/th>\nAPI'si<\/th>\n<\/tr>\n<\/thead>\n
            \u0130leti\u015fim<\/td>\nE\u015fzamans\u0131z (olay odakl\u0131)<\/td>\nSenkron (istek-yan\u0131t)<\/td>\n<\/tr>\n
            Veri ak\u0131\u015f\u0131<\/td>\nTek y\u00f6n (kaynaktan hedefe)<\/td>\n\u0130ki y\u00f6nl\u00fc (talep ve yan\u0131t)<\/td>\n<\/tr>\n
            Ger\u00e7ek Zamanl\u0131 G\u00fcncellemeler<\/td>\nEvet<\/td>\nM\u00fcmk\u00fcn ama do\u011fu\u015ftan de\u011fil<\/td>\n<\/tr>\n
            Y\u00fck Karma\u015f\u0131kl\u0131\u011f\u0131<\/td>\nGenellikle basit JSON veya XML<\/td>\nAPI tasar\u0131m\u0131na ba\u011fl\u0131 olarak de\u011fi\u015fiklik g\u00f6sterir<\/td>\n<\/tr>\n
            Entegrasyon Yakla\u015f\u0131m\u0131<\/td>\nHedef uygulamaya g\u00f6re web kancas\u0131 URL kayd\u0131<\/td>\nServis sa\u011flay\u0131c\u0131 taraf\u0131ndan sa\u011flanan API u\u00e7 noktalar\u0131<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            Webhook ile ilgili gelece\u011fin perspektifleri ve teknolojileri<\/h2>\n

            Web kancalar\u0131n\u0131n gelece\u011fi, \u00e7e\u015fitli end\u00fcstriler ve uygulamalar aras\u0131nda s\u00fcrekli entegrasyon ve benimsenmede yatmaktad\u0131r. Ger\u00e7ek zamanl\u0131 veri al\u0131\u015fveri\u015fi ve kusursuz entegrasyonlara olan talep artt\u0131k\u00e7a, web kancalar\u0131 farkl\u0131 sistemler aras\u0131nda verimli ileti\u015fimin sa\u011flanmas\u0131nda merkezi bir rol oynayacakt\u0131r.<\/p>\n

            Teknoloji a\u00e7\u0131s\u0131ndan web kancalar\u0131n\u0131n geli\u015fimi \u015funlar\u0131 i\u00e7erebilir:<\/p>\n

              \n
            1. \n

              Standardizasyon: Birlikte \u00e7al\u0131\u015fabilirli\u011fi ve daha kolay uygulamay\u0131 sa\u011flamak i\u00e7in standartla\u015ft\u0131r\u0131lm\u0131\u015f webhook formatlar\u0131n\u0131n ve protokollerinin geli\u015ftirilmesi.<\/p>\n<\/li>\n

            2. \n

              G\u00fcvenlik Geli\u015ftirmeleri: Webhook ileti\u015fimlerini korumak ve potansiyel tehditlere kar\u015f\u0131 koruma sa\u011flamak i\u00e7in g\u00fcvenlik \u00f6nlemlerinde yap\u0131lan iyile\u015ftirmeler.<\/p>\n<\/li>\n

            3. \n

              Webhook Ekosistemi: Webhook y\u00f6netimi, izleme ve analiti\u011fine odaklanan \u00f6zel ara\u00e7lar\u0131n ve platformlar\u0131n ortaya \u00e7\u0131k\u0131\u015f\u0131.<\/p>\n<\/li>\n<\/ol>\n

              Proxy sunucular\u0131 Webhook ile nas\u0131l kullan\u0131labilir veya ili\u015fkilendirilebilir?<\/h2>\n

              Proxy sunucular\u0131 web kancalar\u0131n\u0131n uygulanmas\u0131n\u0131 ve g\u00fcvenli\u011fini geli\u015ftirebilir. Kaynak ve hedef uygulamalar aras\u0131nda arac\u0131 g\u00f6revi g\u00f6rerek a\u015fa\u011f\u0131daki faydalar\u0131 sa\u011flarlar:<\/p>\n

                \n
              1. \n

                Artt\u0131r\u0131lm\u0131\u015f Anonimlik: Proxy sunucular\u0131, webhook istekleri g\u00f6nderilirken kaynak uygulaman\u0131n IP adresini anonimle\u015ftirerek ekstra bir g\u00fcvenlik katman\u0131 ekleyebilir.<\/p>\n<\/li>\n

              2. \n

                Y\u00fck Dengeleme: Proxy sunucular\u0131, webhook isteklerini birden fazla hedef sunucu aras\u0131nda da\u011f\u0131tarak y\u00fck dengelemeyi sa\u011flar ve tek ar\u0131za noktalar\u0131n\u0131 \u00f6nler.<\/p>\n<\/li>\n

              3. \n

                \u00d6nbelle\u011fe Alma: Proxy'ler webhook yan\u0131tlar\u0131n\u0131 \u00f6nbelle\u011fe alabilir, yan\u0131t s\u00fcrelerini k\u0131saltabilir ve hedef sunuculardaki y\u00fck\u00fc en aza indirebilir.<\/p>\n<\/li>\n

              4. \n

                G\u00fcvenlik Filtreleme: Proxy'ler, gelen webhook isteklerini filtrelemek ve do\u011frulamak i\u00e7in g\u00fcvenlik \u00f6nlemleri uygulayarak olas\u0131 tehditleri azaltabilir.<\/p>\n<\/li>\n<\/ol>\n

                \u0130lgili Ba\u011flant\u0131lar<\/h2>\n

                Web kancalar\u0131 hakk\u0131nda daha fazla bilgi i\u00e7in a\u015fa\u011f\u0131daki kaynaklar\u0131 ziyaret edebilirsiniz:<\/p>\n

                  \n
                1. Web kancalar\u0131 \u2013 Mozilla Geli\u015ftirici A\u011f\u0131<\/a><\/li>\n
                2. Web Kancalar\u0131n\u0131 Anlamak \u2013 Shopify Geli\u015ftirici Belgeleri<\/a><\/li>\n
                3. Web kancalar\u0131 ve API'ler: Fark Nedir? \u2013 Postac\u0131 Blogu<\/a><\/li>\n
                4. Web Kancalar\u0131n\u0131n Y\u00fckseli\u015fi ve Modern Web Geli\u015ftirmedeki Rol\u00fc \u2013 DZone<\/a><\/li>\n
                5. Web Kancalar\u0131 Sade \u0130ngilizceyle A\u00e7\u0131klan\u0131yor \u2013 Zapier Blogu<\/a><\/li>\n<\/ol>","protected":false},"featured_media":479652,"menu_order":0,"template":"","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"class_list":["post-479651","wiki","type-wiki","status-publish","has-post-thumbnail","hentry"],"acf":{"faq_title":"Frequently Asked Questions about Webhook: A Comprehensive Guide<\/mark>","faq_items":[{"question":"What is a webhook, and how does it work?","answer":"

                  A webhook is a mechanism used in web development that enables real-time communication and data exchange between different web applications. When a specific event occurs in one application, it automatically sends an HTTP request to a URL provided by another application, triggering an action or notification. The destination application, known as the webhook handler, processes the incoming request's payload data and performs the required actions accordingly.<\/p>"},{"question":"What is the history of webhooks, and who first introduced the term?","answer":"

                  The concept of webhooks dates back to the early 2000s, but the term \"webhook\" gained popularity after Jeff Lindsay mentioned it in a blog post in 2007, referring to them as \"HTTP-POST callbacks.\"<\/p>"},{"question":"What are the key features of webhooks?","answer":"

                  Webhooks offer real-time updates, lightweight and efficient communication, scalability, and an event-driven architecture, promoting easier integration and automation between web applications.<\/p>"},{"question":"What are the different types of webhooks?","answer":"

                  Webhooks can be categorized as Incoming Webhooks, Outgoing Webhooks, Reverse Webhooks, and Sequential Webhooks, based on their functionality and implementation.<\/p>"},{"question":"How are webhooks used, and what are the common problems associated with them?","answer":"

                  Webhooks are used for real-time notifications, data synchronization, automation, and CI\/CD pipelines. Common problems include security concerns, delivery failures, handling retries, and payload validation.<\/p>"},{"question":"How do webhooks compare with APIs?","answer":"

                  Webhooks are asynchronous and one-way, while APIs are synchronous and two-way. Webhooks provide real-time updates, while APIs may not inherently offer that capability.<\/p>"},{"question":"What are the future perspectives and technologies related to webhooks?","answer":"

                  The future of webhooks involves standardization, security enhancements, and the emergence of specialized webhook management tools and platforms.<\/p>"},{"question":"How can proxy servers be associated with webhooks?","answer":"

                  Proxy servers can enhance webhook implementation by increasing anonymity, load balancing, caching, and implementing security filtering.<\/p>"},{"question":"Where can I find more information about webhooks?","answer":"

                  For more information about webhooks, you can visit the provided related links, covering various aspects and use cases of webhooks.<\/p>"}]},"_links":{"self":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki\/479651","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki"}],"about":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/types\/wiki"}],"version-history":[{"count":0,"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki\/479651\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/media\/479652"}],"wp:attachment":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/media?parent=479651"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}