{"id":85,"date":"2026-10-03T17:55:00","date_gmt":"2026-10-03T17:55:00","guid":{"rendered":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/03\/webhook-design-signing-retry\/"},"modified":"2026-10-03T17:55:00","modified_gmt":"2026-10-03T17:55:00","slug":"webhook-design-signing-retry","status":"publish","type":"post","link":"https:\/\/www.akifsen.com.tr\/blog\/2026\/10\/03\/webhook-design-signing-retry\/","title":{"rendered":"Webhook G\u00f6ndermek Kolay, G\u00fcvenilir Webhook G\u00f6ndermek Zor"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Bir platforma webhook \u00f6zelli\u011fi eklemek genellikle \u015f\u00f6yle ba\u015flar:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir olay ger\u00e7ekle\u015fir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kullan\u0131c\u0131n\u0131n kaydetti\u011fi URL&#8217;ye HTTP iste\u011fi g\u00f6nderilir.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>POST https:\/\/customer.example\/hooks\n{ \"type\": \"invoice.paid\", \"id\": \"evt_81f2\" }<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Bu kadar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130lk m\u00fc\u015fteri entegrasyonu \u00e7al\u0131\u015f\u0131r. Sonra destek talepleri gelmeye ba\u015flar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8220;D\u00fcn bir \u00f6deme bildirimi almad\u0131k.&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8220;Ayn\u0131 bildirim iki kez geldi.&#8221;<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">&#8220;Bu iste\u011fin sizden geldi\u011fini nas\u0131l anlayaca\u011f\u0131z?&#8221;<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Kar\u015f\u0131 taraf her zaman ayakta de\u011fildir<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Webhook alan sistem deploy oluyor olabilir. Yava\u015f cevap veriyor olabilir. Bir saatlik bak\u0131m \u00e7al\u0131\u015fmas\u0131nda olabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Webhook g\u00f6nderen taraf bunu normal kabul etmeli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu y\u00fczden webhook g\u00f6nderimi, olay\u0131n olu\u015ftu\u011fu iste\u011fin i\u00e7inde senkron olarak yap\u0131lmamal\u0131. Olay \u00f6nce kal\u0131c\u0131 olarak kaydedilmeli ve ayr\u0131 bir worker taraf\u0131ndan g\u00f6nderilmeli. \u00d6deme i\u015fleminin cevab\u0131, m\u00fc\u015fterinin webhook endpoint&#8217;inin yava\u015fl\u0131\u011f\u0131ndan etkilenmemeli.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Retry ve backoff<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">2xx d\u0131\u015f\u0131ndaki her cevap veya timeout ba\u015far\u0131s\u0131z kabul edilir ve tekrar denenir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama hemen de\u011fil. Artan aral\u0131klarla:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>1 dakika\n5 dakika\n30 dakika\n2 saat\n...\ntoplam ~3 g\u00fcn<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Birka\u00e7 g\u00fcnl\u00fck bir retry penceresi, kar\u015f\u0131 taraf\u0131n uzun bir kesintiden sonra bile olaylar\u0131 almas\u0131n\u0131 sa\u011flar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bir endpoint uzun s\u00fcre s\u00fcrekli ba\u015far\u0131s\u0131z oluyorsa, m\u00fc\u015fteriye bildirim g\u00f6nderip endpoint&#8217;i devre d\u0131\u015f\u0131 b\u0131rakmak da gerekebilir. Aksi halde worker&#8217;lar \u00f6l\u00fc bir adrese sonsuza kadar istek atar.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Timeout de\u011feri de k\u0131sa tutulmal\u0131. Webhook alan taraf\u0131n i\u015fi uzun s\u00fcrecekse, iste\u011fi hemen kabul edip i\u015fi arka planda yapmas\u0131 beklenir. Stripe ve GitHub gibi platformlar da dok\u00fcmantasyonlar\u0131nda h\u0131zl\u0131ca 2xx d\u00f6n\u00fclmesini \u00f6neriyor.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Ayn\u0131 olay birden fazla gelebilir<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Webhook g\u00f6nderildi. Kar\u015f\u0131 taraf i\u015fledi. Ama cevap a\u011fda kayboldu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">G\u00f6nderen taraf timeout g\u00f6rd\u00fc\u011f\u00fc i\u00e7in tekrar g\u00f6nderir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Webhook&#8217;lar at-least-once teslim edilir. Bu ka\u00e7\u0131n\u0131lmaz.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu y\u00fczden her olay\u0131n benzersiz ve de\u011fi\u015fmeyen bir ID&#8217;si olmal\u0131. Alan taraf bu ID&#8217;yi saklayarak tekrar gelen olaylar\u0131 ay\u0131klayabilmeli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">G\u00f6nderen taraf\u0131n dok\u00fcmantasyonunda bunu a\u00e7\u0131k\u00e7a yazmas\u0131 da \u00f6nemli. &#8220;Ayn\u0131 event birden fazla gelebilir, <code>id<\/code> alan\u0131 ile tekille\u015ftirin&#8221; c\u00fcmlesi, bir\u00e7ok entegrasyon hatas\u0131n\u0131 ba\u015ftan \u00f6nler.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">S\u0131ra garantisi yok<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Retry mekanizmas\u0131 olan her sistemde olaylar g\u00f6nderildi\u011fi s\u0131rayla ula\u015fmayabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><code>invoice.paid<\/code> olay\u0131 <code>invoice.created<\/code> olay\u0131ndan \u00f6nce gelebilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Alan taraf bunu tolere etmeli. Pratik bir yakla\u015f\u0131m, webhook&#8217;u sadece &#8220;bu kaynakta bir \u015fey de\u011fi\u015fti&#8221; sinyali olarak kullanmak ve g\u00fcncel durumu API&#8217;den okumakt\u0131r. B\u00f6ylece s\u0131ra problemi b\u00fcy\u00fck \u00f6l\u00e7\u00fcde ortadan kalkar.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">\u0130mza<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Webhook endpoint&#8217;i internete a\u00e7\u0131k bir URL&#8217;dir. Herkes oraya istek g\u00f6nderebilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Alan taraf\u0131n iste\u011fin ger\u00e7ekten platformdan geldi\u011fini do\u011frulayabilmesi gerekir. En yayg\u0131n y\u00f6ntem, her m\u00fc\u015fteri i\u00e7in ayr\u0131 bir secret ile HMAC imzas\u0131 \u00fcretmektir:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>X-Signature: t=1792951200,v1=5257a869e7ecebeda32a...<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130mza, zaman damgas\u0131 ve g\u00f6vdenin birle\u015fiminden hesaplan\u0131r. Alan taraf ayn\u0131 hesab\u0131 yapar ve sonu\u00e7lar\u0131 kar\u015f\u0131la\u015ft\u0131r\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Burada iki detay \u00f6nemli.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Kar\u015f\u0131la\u015ft\u0131rma constant-time yap\u0131lmal\u0131. Basit string kar\u015f\u0131la\u015ft\u0131rmas\u0131 timing attack&#8217;a a\u00e7\u0131k olabilir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Zaman damgas\u0131 kontrol edilmeli. Birka\u00e7 dakikadan eski istekler reddedilirse, yakalanm\u0131\u015f bir iste\u011fin daha sonra tekrar oynat\u0131lmas\u0131 engellenir.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130mza ham g\u00f6vde \u00fczerinden do\u011frulanmal\u0131. JSON parse edilip tekrar serialize edilen g\u00f6vde, bo\u015fluk veya alan s\u0131ras\u0131 fark\u0131 nedeniyle farkl\u0131 bir imza \u00fcretir. Framework&#8217;ler bazen g\u00f6vdeyi otomatik parse etti\u011fi i\u00e7in bu, en s\u0131k kar\u015f\u0131la\u015f\u0131lan do\u011frulama hatalar\u0131ndan biri.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">G\u00f6zlemlenebilirlik m\u00fc\u015fteriye de laz\u0131m<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">\u0130yi bir webhook sistemi, m\u00fc\u015fterinin kendi taraf\u0131nda olanlar\u0131 g\u00f6rebilmesini sa\u011flar. G\u00f6nderilen olaylar\u0131n listesi, cevap kodlar\u0131, deneme say\u0131s\u0131 ve manuel olarak tekrar g\u00f6nderme butonu.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Bu ekran, destek ekibine gelen &#8220;bildirim gelmedi&#8221; taleplerinin b\u00fcy\u00fck k\u0131sm\u0131n\u0131 ortadan kald\u0131r\u0131r.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Webhook basit bir HTTP iste\u011fi gibi g\u00f6r\u00fcn\u00fcyor.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Ama asl\u0131nda iki farkl\u0131 \u015firketin sistemleri aras\u0131nda kurulan da\u011f\u0131t\u0131k bir mesajla\u015fma kanal\u0131 ve \u00f6yle tasarlanmas\u0131 gerekiyor.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Webhook endpoint&#8217;i kapal\u0131ysa olay kaybolur mu? Ayn\u0131 event iki kez gelirse ne olur? Webhook g\u00f6nderen ve alan taraf i\u00e7in imzalama, retry ve idempotency.<\/p>\n","protected":false},"author":1,"featured_media":84,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[],"class_list":["post-85","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-api-tasarimi"],"_links":{"self":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/85","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/comments?post=85"}],"version-history":[{"count":0,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/posts\/85\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media\/84"}],"wp:attachment":[{"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/media?parent=85"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/categories?post=85"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.akifsen.com.tr\/blog\/wp-json\/wp\/v2\/tags?post=85"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}