Cloud Data Loss Prevention (Cloud DLP) 現已併入機密資料保護。API 名稱維持不變：Cloud Data Loss Prevention API (DLP API)。如要瞭解構成 Sensitive Data Protection 的服務，請參閱「Sensitive Data Protection 總覽」。
本文說明 Sensitive Data Protection 提供的各類 API 端點。本文也提供相關考量點，協助您決定要在 Sensitive Data Protection 要求中使用哪種端點類型。如要瞭解不同類型的 API 端點，請參閱 Assured Workloads 文件中的「API 端點類型」。
API 端點 (或服務端點) 是指定 API 服務 (例如 Sensitive Data Protection) 網路位址的基準網址。 Google Cloud Sensitive Data Protection 具有全域和區域端點。
全域 API 端點
Sensitive Data Protection 的全域端點為 dlp.googleapis.com。
全域範圍端點提供高可用性服務端點，可盡可能在靠近用戶端的位置終止 TLS 會期，從而盡量減少透過網際網路為分散式用戶端群組提供 API 呼叫服務時的延遲時間。
向全域端點傳送要求時，您可以指定要處理要求的位置。
未指定位置的全球端點要求
如果未在要求中指定位置，或指定 global 區域，系統就會在 global 區域處理要求。舉例來說，如果您將 POST 要求傳送至下列網址，要求會傳送至全域端點，並在 global 區域中處理。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-09-04 (世界標準時間)。"],[],[],null,["# Global and regional endpoints for Sensitive Data Protection\n\nThis document describes the different types of API endpoints available with\nSensitive Data Protection. This document also provides points to consider\nwhen deciding which\nendpoint type to use in your Sensitive Data Protection requests. For general\ninformation about the different types of API endpoints, see [API endpoint\ntypes](/assured-workloads/docs/api-endpoints) in the Assured Workloads\ndocumentation.\n\nAn API endpoint (or *service endpoint*) is a base URL that specifies the network\naddress of a Google Cloud API service like Sensitive Data Protection.\nSensitive Data Protection has global and regional endpoints.\n\nGlobal API endpoint\n-------------------\n\nThe global endpoint of Sensitive Data Protection is `dlp.googleapis.com`.\n\nGlobally scoped endpoints provide highly available service endpoints\nthat terminate the TLS session as close to the client as possible, which\nminimizes latency when serving API calls from a dispersed client population\nover the internet.\n\nWhen you send a request to a global endpoint, you can specify the location where\nyou want to process the request.\n\n### Requests to a global endpoint with no location specified\n\nIf you don't specify a location in your request---or if you specify the\n`global` region---then the request is processed in the `global` region. For\nexample, if you send a `POST` request to the following URL, the request is sent\nto the global endpoint and processed in the `global` region. \n\n https://dlp.googleapis.com/v2/projects/example-project/content:inspect\n\n### Requests to a global endpoint with a location specified\n\nIf you specify a location in your request to a global endpoint, the request\nis sent to the global endpoint and processed in the region or multi-region that\nyou specified.\nFor example, if you send a `POST` request to the following\nURL, the request is sent to the global endpoint and processed in the `us-west1`\nregion. \n\n https://dlp.googleapis.com/v2/projects/example-project/locations/us-west1/content:inspect\n\nThere is no guarantee that the data in transit remains in the processing region\nthat you specified. If you aren't required to keep in-transit data within a\nspecific region, then calling the global endpoint in this manner is sufficient.\n\nRegional API endpoints\n----------------------\n\nRegional endpoints (REP) let you keep in-transit data within a specific\nregion. A regional endpoint specifies the location as a subdomain---for\nexample, `dlp.us-west1.rep.googleapis.com`.\n\nA regional endpoint for Sensitive Data Protection follows this format: \n\n dlp.\u003cvar translate=\"no\"\u003eREP_REGION\u003c/var\u003e.rep.googleapis.com\n\nReplace \u003cvar translate=\"no\"\u003eREP_REGION\u003c/var\u003e with a [regional endpoint available\nfor Sensitive Data Protection](/sensitive-data-protection/docs/locations#regional-endpoints).\n\nRegional endpoints terminate TLS sessions in the location specified by the\nendpoint for requests received from the public internet or from private\nconnectivity.\n\nRegional endpoints guarantee [data\nresidency](/assured-workloads/docs/data-residency) by ensuring that your data at\nrest, in use, and in transit isn't moved out of the location specified by the\nendpoint. This guarantee excludes Service Data. For more information, see\n[Note on Customer Data and Service\nData](/assured-workloads/docs/data-residency#customer-service-data).\n\nChoose between the global and regional endpoints\n------------------------------------------------\n\nConsider the following when choosing between global and regional endpoints:\n\n- If your organization is required to keep data at rest, in use, and in transit\n within a specific region, then you must use regional endpoints. If you aren't\n required to keep in-transit data within a specific region, then you can use\n global endpoints.\n\n- Regional endpoints are supported by a limited number of locations. For a full\n list of regions and multi-regions where Sensitive Data Protection is\n available, see [Sensitive Data Protection\n locations](/sensitive-data-protection/docs/locations).\n\n- Sensitive Data Protection has separate sets of\n [quotas](/sensitive-data-protection/limits#request-quotas) for the following:\n\n - Requests to the global endpoint with no location specified (processed in the `global` region)\n - Requests to the global endpoint where a processing location is specified (processed in the specified region)\n - Requests to regional endpoints\n\n The quotas for regional endpoints are lower than the quotas for the other two.\n- If your client application is configured to use global endpoints and you want\n to start using regional endpoints, you need to configure your client\n application to specify the REP-supported region or multi-region in the\n subdomain and the path of each hostname that you use in your requests. For\n more information, see [Specify a region in a request to a regional\n endpoint](/sensitive-data-protection/docs/specifying-location#specify-region-rep).\n\nRestrict global API endpoint usage\n----------------------------------\n\nTo help enforce the use of regional endpoints, use the\n`constraints/gcp.restrictEndpointUsage` organization policy constraint to block\nrequests to the global API endpoint. For more information, see\n[Restrict endpoint usage](/assured-workloads/docs/restrict-endpoint-usage) in\nthe Assured Workloads documentation.\n\nWhat's next\n-----------\n\n- Refer to a list of [locations where Sensitive Data Protection is\n available](/sensitive-data-protection/docs/locations).\n- Learn how to [specify a location in your\n request](/sensitive-data-protection/docs/specifying-location)."]]
