Halaman ini menunjukkan cara menjalankan beberapa API independen di domain kustom Anda sendiri (misalnya, example.com).
Sebelum memulai
Untuk menggunakan domain kustom, ikuti petunjuk di bagian Memverifikasi nama domain.
Selama proses tersebut, Anda harus mengonfirmasi kepemilikan domain. Konfirmasi ini
memungkinkan Anda men-deploy dan melayani API di subdomain mana pun.
Misalnya, jika kepemilikan domain ditetapkan untuk example.com, nama layanan
dapat menyertakan subdomain example.com seperti api.example.com atau
catalog.api.example.com.
Men-deploy API di subdomain
Contoh berikut men-deploy API ke subdomain first_api.example.com:
Di file konfigurasi gRPC API, tetapkan kolom name ke first_api.example.com dan tetapkan kolom lainnya seperti yang dijelaskan dalam Mengonfigurasi Cloud Endpoints.
Sekarang Anda dapat mengirim permintaan ke first_api.example.com dan melihat grafik permintaan tersebut di halaman Endpoints > Services.
Men-deploy API berikutnya
Untuk men-deploy API lain, ulangi langkah-langkah sebelumnya, dengan mengubah subdomain
first_api.example.com menjadi subdomain yang Anda gunakan untuk API berikutnya.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 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."]]
