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-28 UTC."],[[["\u003cp\u003eThis guide explains how to run multiple independent APIs on a custom domain, such as \u003ccode\u003eexample.com\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo use a custom domain, you must first verify ownership of the domain, which allows deploying APIs to any of its subdomains.\u003c/p\u003e\n"],["\u003cp\u003eDeploying an API to a subdomain involves setting the \u003ccode\u003ehost\u003c/code\u003e field in the OpenAPI document and then deploying both the Endpoints configuration and the API backend.\u003c/p\u003e\n"],["\u003cp\u003eEach new API you deploy on your custom domain will require a unique subdomain, with the process being repeated for each one.\u003c/p\u003e\n"]]],[],null,["# Serving multiple APIs from a domain\n\nOpenAPI \\| [gRPC](/endpoints/docs/grpc/deploying-apis-subdomains \"View this page for the Cloud Endpoints gRPC docs\")\n\n\u003cbr /\u003e\n\nThis page shows you how to run multiple independent APIs on your own custom\ndomain (for example, `example.com`).\n\nBefore you begin\n----------------\n\nTo use a custom domain, follow the instructions in\n[Verifying a domain name](/endpoints/docs/openapi/verify-domain-name).\nDuring that process, you must confirm ownership of the domain. This confirmation\nlets you deploy and service APIs on any of its subdomains.\n\nFor example, if domain ownership is established for `example.com`, service names\ncan include subdomains of `example.com` such as `api.example.com` or\n`catalog.api.example.com`.\n\nDeploying an API on a subdomain\n-------------------------------\n\nThe following example deploys the API to the subdomain `first_api.example.com`:\n\n1. Set the `host` field of your OpenAPI document to `first_api.example.com`\n and set the other fields as described in\n [Configuring Cloud Endpoints](/endpoints/docs/openapi/configure-endpoints).\n\n2. [Deploy the Endpoints configuration](/endpoints/docs/openapi/deploy-endpoints-config).\n\n3. [Deploy the API backend](/endpoints/docs/openapi/deploy-api-backend).\n\nNow you can send requests to `first_api.example.com` and view graphs of those\nrequests on the\n[**Endpoints** \\\u003e **Services** page](https://console.cloud.google.com/endpoints).\n\nDeploying your next API\n-----------------------\n\nTo deploy another API, repeat the preceding steps, changing the subdomain\n`first_api.example.com` to the subdomain you are using for the next API."]]
