{"id":22432,"date":"2025-05-28T20:30:13","date_gmt":"2025-05-28T17:30:13","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/rest-apilerinde-uri-tasarimi-sik-temiz-ve-tutarli\/"},"modified":"2025-05-28T20:30:13","modified_gmt":"2025-05-28T17:30:13","slug":"rest-apilerinde-uri-tasarimi-sik-temiz-ve-tutarli","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/rest-apilerinde-uri-tasarimi-sik-temiz-ve-tutarli\/","title":{"rendered":"REST API’lerinde URI Tasar\u0131m\u0131: \u015e\u0131k, Temiz ve Tutarl\u0131"},"content":{"rendered":"

<\/p>\n

REST API’lerinde URI Tasar\u0131m\u0131: \u015e\u0131k, Temiz ve Tutarl\u0131<\/p>\n

RESTful API’ler tasarlarken, URI’lerin (Uniform Resource Identifier) do\u011fru \u015fekilde tasarlanmas\u0131, API’nizin performans\u0131, okunabilirli\u011fi ve s\u00fcrd\u00fcr\u00fclebilirli\u011fi a\u00e7\u0131s\u0131ndan olduk\u00e7a \u00f6nemlidir. Bu makalede, temiz, \u015f\u0131k ve tutarl\u0131 URI’ler olu\u015fturmak i\u00e7in pratik ipu\u00e7lar\u0131 ve en iyi uygulamalar\u0131 ele alaca\u011f\u0131z. Ayr\u0131ca, s\u0131k yap\u0131lan hatalardan ve bunlar\u0131n nas\u0131l \u00f6nlenece\u011finden bahsedece\u011fiz. \u0130yi bir URI tasar\u0131m\u0131, API’nizin kullan\u0131m\u0131 ve anla\u015f\u0131lmas\u0131 konusunda b\u00fcy\u00fck bir fark yarat\u0131r.<\/p>\n

Temel \u0130lkeler<\/h2>\n

\u00d6ncelikle, iyi bir REST API URI tasar\u0131m\u0131n\u0131n baz\u0131 temel ilkeleri vard\u0131r. Bunlardan en \u00f6nemlisi, kaynaklar\u0131 temsil eden URI’lerin kullan\u0131lmas\u0131d\u0131r. \u00d6rne\u011fin, kullan\u0131c\u0131lar\u0131 temsil eden bir URI \/users olabilir. Bu, kaynaklar\u0131n ne oldu\u011funu anlamam\u0131z\u0131 kolayla\u015ft\u0131r\u0131r. Ayr\u0131ca, URI’ler k\u0131sa, \u00f6z ve anla\u015f\u0131labilir olmal\u0131d\u0131r. Karma\u015f\u0131k URI’ler, hem geli\u015ftiriciler hem de kullan\u0131c\u0131lar i\u00e7in kafa kar\u0131\u015f\u0131kl\u0131\u011f\u0131 yaratabilir.<\/p>\n

Ba\u015fka bir \u00f6nemli nokta ise tutarl\u0131l\u0131k. T\u00fcm API boyunca ayn\u0131 isimlendirme ve yap\u0131land\u0131rmay\u0131 kullanmak, API’nin anla\u015f\u0131l\u0131rl\u0131\u011f\u0131n\u0131 ve kullan\u0131m kolayl\u0131\u011f\u0131n\u0131 art\u0131r\u0131r. \u00d6rne\u011fin, t\u00fcm kaynaklar i\u00e7in ayn\u0131 s\u00f6zdizimi kullan\u0131l\u0131rsa, API’yi kullananlar URI’leri daha kolay tahmin edebilir.<\/p>\n

S\u0131k Yap\u0131lan Hatalar ve \u00c7\u00f6z\u00fcmler<\/h2>\n

URI tasar\u0131m\u0131nda s\u0131k kar\u015f\u0131la\u015f\u0131lan hatalardan biri, i\u015flem (verb) bilgilerini URI’nin i\u00e7ine eklemektir. \u00d6rne\u011fin, \/users\/delete\/123 yanl\u0131\u015f bir yakla\u015f\u0131md\u0131r. HTTP metodlar\u0131 (GET, POST, PUT, DELETE) bu i\u015flemleri belirtmek i\u00e7in kullan\u0131l\u0131r. Do\u011fru yakla\u015f\u0131m, \/users\/123 URI’sini kullan\u0131p DELETE metodunu kullanmakt\u0131r.<\/p>\n

Bir di\u011fer yayg\u0131n hata ise gereksiz hiyerar\u015filer kullanmakt\u0131r. Gereksiz yere uzun ve karma\u015f\u0131k URI’ler, okunabilirli\u011fi ve anla\u015f\u0131l\u0131rl\u0131\u011f\u0131 azalt\u0131r. URI’leri olabildi\u011fince k\u0131sa ve \u00f6z tutmaya \u00e7al\u0131\u015fmal\u0131y\u0131z. \u00d6rne\u011fin, \/products\/categories\/123\/products\/456 yerine daha temiz bir yap\u0131 tercih edilmelidir.<\/p>\n

\u00d6rnek URI’ler<\/h2>\n

\u0130\u015fte baz\u0131 \u00f6rnek URI’ler ve bunlar\u0131n neden iyi veya k\u00f6t\u00fc tasar\u0131mlar oldu\u011funa dair a\u00e7\u0131klamalar:<\/p>\n