Üçüncü tarafların istemci kimliğinizi kendi web sitelerinde kullanmasını önlemek için istemci kimliğinizin kullanımı, özel olarak yetkilendirdiğiniz URL'lerin listesiyle sınırlandırılmıştır.
Bir URL'yi kaldırmak için URL'nin solundaki kutuyu işaretleyin ve tablonun sağ üst kısmındaki deletesil simgesini tıklayın.
Yeni URL eklemek için tablonun alt kısmındaki URL ekle'yi tıklayın.
Önemli: Yetkili istemci kimliği URL'lerinin kuralları, API anahtarı yönlendiren kısıtlamalarından farklıdır. Daha ayrıntılı bilgi için aşağıya bakın.
Yetkili URL'ler için aşağıdaki hususlar geçerlidir:
Alan adının veya IP adresinin herkese açık olması gerekmez.
Örneğin, http://myintranet ve http://192.168.1.1 geçerli girişlerdir.
Belirtilen alanın tüm alt alanları da yetkilendirilir.
Örneğin, http://example.com çıplak alanı yetkiliyse http://www.example.com alt alanı da yetkilidir. Bunun tersi doğru değildir: http://www.example.com yetkiliyse http://example.com otomatik olarak yetkili olmaz.
Yetkili bir yolun tüm alt yolları da yetkilendirilir.
Örneğin, http://example.com yetkiliyse http://example.com/foo de yetkilidir. Ayrıca, belirtilen alanın alt alan adları da yetkilendirildiğinden http://sub.example.com/bar yetkilendirilir.
Yollar büyük/küçük harfe duyarlıdır.
Örneğin, http://www.example.com/ThisPath/ ile http://www.example.com/thispath/ aynı değildir.
Geçerli URL'leri belirli bağlantı noktalarını kullananlarla kısıtlayabilirsiniz.
Örneğin, http://example.com:8080/foo belirtilirse bu, http://example.com için yetki vermez.
HTTP ve HTTPS protokolleri farklı URL'ler olarak kabul edilir.
Örneğin, https://example.com yetkiliyse http://example.com otomatik olarak yetkili olmaz.
Protokol şeması olmadan bir son ek referansı sağlarsanız (ör. www.example.com) hem HTTP hem de HTTPS için ayrı kurallar oluşturulur.
HTTP veya HTTPS'den daha sıra dışı protokol şemaları için Cloud Console'da verilen talimatları inceleyin.
[null,null,["Son güncelleme tarihi: 2025-06-16 UTC."],[[["\u003cp\u003eThe Google Maps Platform Premium Plan is no longer available for new users and this documentation is for existing legacy applications using client IDs.\u003c/p\u003e\n"],["\u003cp\u003eFor new applications, always use API keys instead of client IDs for authentication.\u003c/p\u003e\n"],["\u003cp\u003eClient ID usage is restricted to authorized URLs which can be managed in the Google Cloud Console.\u003c/p\u003e\n"],["\u003cp\u003eAuthorizing a domain automatically authorizes all its subdomains and subpaths, differing from API key referrer restrictions.\u003c/p\u003e\n"],["\u003cp\u003eHTTP and HTTPS protocols are treated as separate URLs for authorization purposes, unlike API key referrer restrictions.\u003c/p\u003e\n"]]],[],null,["# Client ID URL Authorization\n\n**Important:** The Google Maps Platform Premium Plan is no longer available for\nsign up or new customers.\n| **Caution:** This document is only provided as a reference for maintaining existing legacy applications that use client IDs. For new applications, *always* use API keys! See the [Premium Plan Authentication Overview](/maps/premium/authentication/overview) for further details.\n\nMaps JavaScript API client ID authentication\n--------------------------------------------\n\nYou can authenticate your requests with the Google Maps Platform using a client ID\nin combination with **URL registration** (instead of an API key).\n\n### Specify a client ID when loading the API\n\n| **Warning:** Requests containing both a client ID and an API key may result in unexpected API behavior or unintended billing behavior. To prevent this, make sure your requests use only one of these parameters.\n\nThe code below shows you how to replace \u003cvar translate=\"no\"\u003eYOUR_CLIENT_ID\u003c/var\u003e\nwith your own client ID when loading the Google Maps Platform. \n\n \u003cscript async defer src=\"https://maps.googleapis.com/maps/api/js?client=\u003cvar translate=\"no\"\u003eYOUR_CLIENT_ID\u003c/var\u003e&v=quarterly&callback=initMap\"\u003e\u003c/script\u003e\n\n### Manage authorized URLs\n\nTo prevent a third party from using your client ID on their own website, the\nuse of your client ID is restricted to a list of URLs that you have specifically\nauthorized.\n\n#### Locate your client ID in the Cloud console\n\n| **Note:** If you are unable to locate the project linked to your client ID, see [Finding client ID project](/maps/premium/authentication/overview#finding-client-id-project) and [Pausing your client ID](/maps/premium/authentication/overview#pause-client-id).\n\n#### URL authorization in the Cloud console\n\n- Your authorized URLs are all listed in the\n **Authorized URLs for Client ID gme-\\[company\\]** table on the\n [Client ID page](https://console.cloud.google.com/project/_/google/maps-apis/clientid).\n\n- To remove a URL, check the box to the left of the URL and click the\n delete **delete** icon at the top right\n of the table.\n\n- To add new URLs, click **Add URLs** at the bottom of the table.\n\nInportant: The rules of authorized client IDs URLs differs from API key referrer\nrestrictions. See below for further details.\n\nThe following considerations apply regarding URLs that are authorized:\n\nThe domain name or IP address does not have to be publicly accessible.\n: For example, `http://myintranet` and `http://192.168.1.1` are valid entries.\n\nAll subdomains of a specified domain are also authorized.\n:\n | **Caution:** This behavior differs from API key referrer rules!\n\n: For example, if the naked domain `http://example.com` is authorized, then\n subdomain `http://www.example.com` is also authorized. The reverse\n is not true: if `http://www.example.com` is authorized, `http://example.com`\n is not automatically authorized.\n\nAll subpaths of an authorized path are also authorized.\n:\n | **Caution:** This behavior differs from API key referrer rules!\n\n: For example, if `http://example.com` is authorized, then\n `http://example.com/foo` is also authorized. In addition, because subdomains\n of a specified domain are also authorized, `http://sub.example.com/bar` is\n authorized.\n\nPaths are case sensitive.\n\n: For example, `http://www.example.com/ThisPath/` is not the same as\n `http://www.example.com/thispath/`.\n\nYou may restrict valid URLs to those using certain ports.\n\n: For example, if `http://example.com:8080/foo` is specified,\n that doesn't authorize `http://example.com`.\n\nHTTP and HTTPS protocols are considered different URLs.\n:\n | **Caution:** This behavior differs from API key referrer rules!\n\n: For example, if `https://example.com` is authorized, `http://example.com` is\n not automatically authorized.\n\n If you provide a suffix reference without protocol scheme, for example\n `www.example.com`, separate rules will be created both for HTTP and HTTPS.\n\nFor more exotic protocol schemes than HTTP or HTTPS, see the provided\ninstructions in the Cloud console."]]
