本文档介绍了 Sensitive Data Protection 提供的不同类型的 API 端点。本文档还提供了在决定在 Sensitive Data Protection 请求中使用哪种端点类型时需要考虑的事项。如需有关不同类型 API 端点的一般信息，请参阅 Assured Workloads 文档中的 API 端点类型。
API 端点（或服务端点）是指定 Google Cloud API 服务（例如 Sensitive Data Protection）的网络地址的基本网址。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"]],["最后更新时间 (UTC)：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)."]]
