Stay organized with collectionsSave and categorize content based on your preferences.
API endpoint types
This page describes the different types of API endpoints that can be used in
Assured Workloads. An API endpoint (orservice endpoint) is a URL
that specifies the network address of a Google Cloud API service, such asbigquery.googleapis.com. Google Cloud services allow access to resources using
different types of API endpoints, including global, locational, and regional
endpoints. Availability for each type depends on whether they are provided by a
given Google Cloud product or service.
All Assured Workloadscontrol packagessupport global
API endpoints. Support for locational and regional API endpoints varies across
control packages.
Global API endpoints
A global API endpoint doesn't specify the location in the URL hostname. For
example:
storage.googleapis.com
bigquery.googleapis.com
logging.googleapis.com
These globally scoped endpoints provide highly available service endpoints
that terminate the TLS session as close to the client as possible, which
minimizes latency when serving API calls from a dispersed client population
over the internet.
Locational API endpoints
A locational API endpoint specifies the location in the URL hostname. For
example:
us-west1-storage.googleapis.com
us-west1-bigquery.googleapis.com
us-west1-logging.googleapis.com
These locational endpoints offer benefits to customers who require the use of
location-specific services, and want to verify that in-transit data remains in
a particular location when accessed through private connectivity.
Regional API endpoints
A regional API endpoint specifies the location as a subdomain. For example:
storage.us-west1.rep.googleapis.com
bigquery.us-west1.rep.googleapis.com
logging.us-west1.rep.googleapis.com
These regional endpoints offer the most benefits to customers who require the
use of location-specific services, and want to have ways to verify that
in-transit data remains in a particular location when accessed through either
private connectivity or the public internet.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eAPI endpoints, which are URLs specifying the network address of a Google Cloud API service, can be global, locational, or regional.\u003c/p\u003e\n"],["\u003cp\u003eGlobal API endpoints, like \u003ccode\u003estorage.googleapis.com\u003c/code\u003e, do not specify a location and are designed for high availability and low latency for clients around the world.\u003c/p\u003e\n"],["\u003cp\u003eLocational API endpoints, such as \u003ccode\u003eus-west1-storage.googleapis.com\u003c/code\u003e, include the location in the hostname and are used by customers who require location-specific services and wish to keep in-transit data in a specific area.\u003c/p\u003e\n"],["\u003cp\u003eRegional API endpoints, exemplified by \u003ccode\u003estorage.us-west1.rep.googleapis.com\u003c/code\u003e, use a location subdomain and offer the greatest control for keeping in-transit data within a specific region, either via private connectivity or the internet.\u003c/p\u003e\n"],["\u003cp\u003eAssured Workloads control packages support global API endpoints, while support for locational and regional endpoints varies, with the availability of both locational and regional endpoints being limited across Google Cloud services.\u003c/p\u003e\n"]]],[],null,["# API endpoint types\n==================\n\nThis page describes the different types of API endpoints that can be used in\nAssured Workloads. An API endpoint (or *service endpoint* ) is a URL\nthat specifies the network address of a Google Cloud API service, such as\n`bigquery.googleapis.com`. Google Cloud services allow access to resources using\ndifferent types of API endpoints, including global, locational, and regional\nendpoints. Availability for each type depends on whether they are provided by a\ngiven Google Cloud product or service.\n\nAll Assured Workloads\n[control packages](/assured-workloads/docs/control-packages) support global\nAPI endpoints. Support for locational and regional API endpoints varies across\ncontrol packages.\n\nGlobal API endpoints\n--------------------\n\nA global API endpoint doesn't specify the location in the URL hostname. For\nexample:\n\n- `storage.googleapis.com`\n- `bigquery.googleapis.com`\n- `logging.googleapis.com`\n\nThese globally 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\nLocational API endpoints\n------------------------\n\nA locational API endpoint specifies the location in the URL hostname. For\nexample:\n\n- `us-west1-storage.googleapis.com`\n- `us-west1-bigquery.googleapis.com`\n- `us-west1-logging.googleapis.com`\n\nThese locational endpoints offer benefits to customers who require the use of\nlocation-specific services, and want to verify that in-transit data remains in\na particular location when accessed through private connectivity.\n| **Note:** Locational API endpoints are supported by a limited number of services, and their availability may vary. In addition, your organization may require additional configuration to enable them in your organization. Contact [Cloud Customer Care](/support) for more information.\n\nRegional API endpoints\n----------------------\n\nA regional API endpoint specifies the location as a subdomain. For example:\n\n- `storage.us-west1.rep.googleapis.com`\n- `bigquery.us-west1.rep.googleapis.com`\n- `logging.us-west1.rep.googleapis.com`\n\nThese regional endpoints offer the most benefits to customers who require the\nuse of location-specific services, and want to have ways to verify that\nin-transit data remains in a particular location when accessed through either\nprivate connectivity or the public internet.\n| **Note:** Regional API endpoints are supported by a limited number of services, and their availability may vary."]]
