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:
Set the host field of your OpenAPI document 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-08-04 UTC."],[[["This guide explains how to run multiple independent APIs on a custom ___domain, such as `example.com`."],["To use a custom ___domain, you must first verify ownership of the ___domain, which allows deploying APIs to any of its subdomains."],["Deploying an API to a subdomain involves setting the `host` field in the OpenAPI document and then deploying both the Endpoints configuration and the API backend."],["Each new API you deploy on your custom ___domain will require a unique subdomain, with the process being repeated for each one."]]],[]]
