Kunci API dikaitkan dengan project Google Cloud tempat kunci tersebut dibuat. Jika API Anda memerlukan kunci API, Anda harus memberikan
kunci kepada pengguna API dari project tempat Anda membuat layanan Cloud Endpoints, atau Anda dapat mengizinkan pengguna mengaktifkan API di project Google Cloudmereka sendiri dan membuat kunci API. Halaman ini menunjukkan cara memberikan izin
yang diperlukan pengguna untuk mengaktifkan API Anda.
Memberikan akses
Endpoint menggunakan peran Service ConsumerIdentity and Access Management (IAM) untuk mengizinkan seseorang yang bukan anggota projectGoogle Cloud Anda mengaktifkan API Anda di project Google Cloud-nya sendiri. Bagian ini menunjukkan cara memberikan akses menggunakan
konsolGoogle Cloud atau Google Cloud CLI.
Google Cloud console
Di Google Cloud console, buka halaman Endpoints > Services
untuk project Anda.
Jika Anda memiliki lebih dari satu API, klik nama API yang ingin Anda beri akses.
Jika panel samping Izin tidak terbuka, klik Tampilkan Panel Izin.
Di kolom Add Principal, masukkan alamat email orang atau
Grup Google yang
ingin Anda beri akses.
Di menu dropdown Select a role, pilih Service Management >
Service Consumer.
Klik Simpan.
Ulangi penambahan anggota dan pemilihan peran, sesuai kebutuhan.
Hubungi pengguna atau grup yang Anda tambahkan dan beri tahu mereka bahwa mereka dapat mengaktifkan API di project Google Cloud mereka. Lihat artikel Mengaktifkan API di project Google Cloud untuk mengetahui informasi tentang cara mengaktifkan layanan di API & layanan.
gcloud
Buka Cloud Shell, atau jika Anda telah menginstal Google Cloud CLI, buka
jendela terminal.
Jika Anda memberikan akses kepada pengguna tertentu:
Hubungi pengguna atau grup yang Anda tambahkan dan beri tahu mereka bahwa mereka dapat mengaktifkan
API dalam project Google Cloud mereka. Lihat artikel Mengaktifkan API di project Google Cloud untuk mengetahui informasi tentang cara mengaktifkan layanan di API & layanan.
Mencabut akses
Anda mencabut akses ke API dengan menghapus peran Service Consumer dari
pengguna atau grup yang sebelumnya memiliki peran tersebut. Setelah Anda mencabut akses seseorang,
dia tidak akan dapat mengaktifkan API Anda.
Bagian ini menunjukkan cara mencabut akses menggunakan konsol Google Cloud atau
Google Cloud CLI.
Google Cloud console
Di Google Cloud console, buka halaman Endpoints > Services
untuk project Google Cloud Anda.
[[["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-18 UTC."],[[["\u003cp\u003eAPI keys are linked to the Google Cloud project where they are created, allowing users to utilize keys from the service's project or enable the API in their own project.\u003c/p\u003e\n"],["\u003cp\u003eThe Identity and Access Management (IAM) Service Consumer role grants external users the ability to enable the API in their Google Cloud projects.\u003c/p\u003e\n"],["\u003cp\u003eAccess can be granted to users or Google Groups via the Google Cloud console or the Google Cloud CLI by assigning the Service Consumer role.\u003c/p\u003e\n"],["\u003cp\u003eAccess can be revoked from users or Google Groups through the Google Cloud console or the Google Cloud CLI by removing the Service Consumer role.\u003c/p\u003e\n"],["\u003cp\u003eRevoking access doesn't prevent users who have already enabled the API from making calls, however, logic can be implemented to disable specific API keys.\u003c/p\u003e\n"]]],[],null,["# Controlling who can enable your API\n\nOpenAPI \\| [gRPC](/endpoints/docs/grpc/control-api-callers \"View this page for the Cloud Endpoints gRPC docs\")\n\n\u003cbr /\u003e\n\nAPI keys are associated with the Google Cloud project in which\nthey have been created. If your API requires an API key, you either have to give\nyour API users a key from the project that you created the Cloud Endpoints\nservice in, or you can let users enable your API in their own Google Cloud\nproject and create an API key. This page shows you how to grant the permission\nthat users need to enable your API.\n\nGranting access\n---------------\n\nEndpoints uses the\n[Identity and Access Management (IAM)](/iam/docs)\n**Service Consumer** role to allow someone who isn't a member of your\nGoogle Cloud project to enable your API in their own Google Cloud\nproject. This section shows you how to grant access using the\nGoogle Cloud console or the Google Cloud CLI. \n\n### Google Cloud console\n\n1. In the Google Cloud console, go to the **Endpoints** \\\u003e **Services** page for your project.\n\n\n [Go to the Endpoints Services page](https://console.cloud.google.com/endpoints)\n\n \u003cbr /\u003e\n\n2. If you have more than one API, click the name of the API that you want to grant access to.\n3. If the **Permissions** side panel isn't open, click **Show Permissions Panel**.\n4. In the **Add Principal** field, enter the email address of the person or [Google Group](https://support.google.com/groups/answer/2464926) that you want to grant access to.\n5. In the **Select a role** drop-down menu, select **Service Management** \\\u003e **Service Consumer**.\n6. Click **Save**.\n7. Repeat adding members and selecting the role, as needed.\n8. Contact the users or groups that you added and let them know they can enable the API in their Google Cloud projects. See [Enable an API in your Google Cloud\n project](/endpoints/docs/openapi/enable-api) for information on how to enable a service in APIs \\& services.\n\n### gcloud\n\n1. Open Cloud Shell, or if you have the Google Cloud CLI installed, open a terminal window.\n - If you are granting access to an individual user:\n\n - If you are granting access to a Google Group:\n\n2. Contact the users or groups that you added and let them know they can enable the API in their Google Cloud projects. See [Enable an API in your Google Cloud\n project](/endpoints/docs/openapi/enable-api) for information on how to enable a service in APIs \\& services.\n\nRevoking access\n---------------\n\nYou revoke access to your API by removing the **Service Consumer** role from a\nuser or group that previously had the role. After you revoke someone's access,\nthey won't be able to enable your API.\n| **Note:** If someone has already enabled your API, revoking access doesn't prevent them from calling your API. Although there is no easy way to to prevent these calls, you can add logic to your code that disallows calls from a specific caller's API key.\n\nThis section shows you how to revoke access using the Google Cloud console or\nthe Google Cloud CLI. \n\n### Google Cloud console\n\n1. In the Google Cloud console, go to the **Endpoints** \\\u003e **Services** page for your Google Cloud project.\n\n\n [Go to the Endpoints Services page](https://console.cloud.google.com/endpoints)\n\n \u003cbr /\u003e\n\n2. If you have more than one API, click the name of the API that you want to revoke access to.\n3. If the **Permissions** side panel isn't open, click **addPermissions**.\n4. Click the **Role** card that the member belongs to.\n5. Click **Delete** delete.\n\n### gcloud\n\n- If you are revoking access for an individual user:\n\n- If you are revoking access for a Google Group:\n\nWhat's next\n-----------\n\n- Tell users how to [enable your API in their Google Cloud project](/endpoints/docs/openapi/enable-api).\n\n\u003c!-- --\u003e\n\n- Learn more about [Sharing APIs protected by API keys](/endpoints/docs/openapi/restricting-api-access-with-api-keys#sharing_apis_protected_by_api_key).\n\n\u003c!-- --\u003e\n\n- Create a [Cloud Endpoints Portal](/endpoints/docs/openapi/dev-portal-overview) for your users."]]
