En esta página, se muestra cómo ejecutar varias API independientes en tu propio dominio personalizado (por ejemplo, example.com).
Antes de comenzar
Para usar un dominio personalizado, sigue las instrucciones en Verificar un nombre de dominio.
Durante ese proceso, debes confirmar la propiedad del dominio. Esta confirmación te permite implementar y entregar las API en cualquiera de sus subdominios.
Por ejemplo, si se establece la propiedad del dominio para example.com, los nombres de servicio pueden incluir subdominios de example.com, como api.example.com o catalog.api.example.com.
Implementar una API en un subdominio
En el ejemplo siguiente, se implementa la API en el subdominio first_api.example.com:
En tu archivo de configuración de la API de gRPC, configura el campo name como first_api.example.com y los otros campos como se describe en Configurar Endpoints.
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThis page details how to deploy multiple independent APIs on a custom domain, such as \u003ccode\u003eexample.com\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eBefore deploying APIs, you must verify domain ownership, enabling the use of any subdomains like \u003ccode\u003eapi.example.com\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eTo deploy an API on a subdomain, you must set the \u003ccode\u003ename\u003c/code\u003e field in your gRPC API configuration file to the desired subdomain.\u003c/p\u003e\n"],["\u003cp\u003eThe process involves configuring Cloud Endpoints, deploying the Endpoints configuration, and deploying the API backend, with each API deployed on a different subdomain.\u003c/p\u003e\n"],["\u003cp\u003eTo deploy another API you must repeat the steps changing the subdomain to the new one you will be using.\u003c/p\u003e\n"]]],[],null,["# Serving multiple APIs from a domain\n\n[OpenAPI](/endpoints/docs/openapi/deploying-apis-subdomains \"View this page for the Cloud Endpoints OpenAPI docs\") \\| gRPC\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/grpc/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. In your gRPC API configuration file, set the `name` field to\n `first_api.example.com` and set the other fields as described in\n [Configuring Cloud Endpoints](/endpoints/docs/grpc/configure-endpoints).\n\n2. [Deploy the Endpoints configuration](/endpoints/docs/grpc/deploy-endpoints-config).\n\n3. [Deploy the API backend](/endpoints/docs/grpc/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."]]
