This page shows you how to run multiple independent APIs on your own custom
domain (for example, example.com).
Before you begin
To use a custom domain, follow the instructions in
Verifying a domain name.
During that process, you must confirm ownership of the domain. This confirmation
lets you deploy and service APIs on any of its subdomains.
For example, if domain ownership is established for example.com, service names
can include subdomains of example.com such as api.example.com or
catalog.api.example.com.
Deploying an API on a subdomain
The following example deploys the API to the subdomain first_api.example.com:
In your gRPC API configuration file, set the name field to
first_api.example.com and set the other fields as described in
Configuring Cloud Endpoints.
[[["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-03-21 UTC."],[[["This page details how to deploy multiple independent APIs on a custom domain, such as `example.com`."],["Before deploying APIs, you must verify domain ownership, enabling the use of any subdomains like `api.example.com`."],["To deploy an API on a subdomain, you must set the `name` field in your gRPC API configuration file to the desired subdomain."],["The process involves configuring Cloud Endpoints, deploying the Endpoints configuration, and deploying the API backend, with each API deployed on a different subdomain."],["To deploy another API you must repeat the steps changing the subdomain to the new one you will be using."]]],[]]
