Cloud Endpoints uses the
Extensible Service Proxy (ESP)
and Service Management to manage your API. When you deployed your
service configuration by using the gcloud endpoints services deploy command, the
command used Service Management to create a managed service for your API.
To delete your API you need to:
Delete the instance that ESP and your API backend is running on.
Delete the managed service that was created for your API.
The easiest way to do both of these tasks is to delete the Google Cloud
project that your API is in. If you want to preserve your
Google Cloud project, then you need to delete the instance and the managed
service.
Deleting instances
Compute Engine
Use the gcloud compute instances delete
command. When you delete an instance in this way, the instance shuts down and
is removed from the list of instances, and all resources attached to the
instance are released, such as persistent disks and any static IP addresses.
To delete a GKE cluster with the Google Cloud CLI:
gcloudcontainerclustersdelete[NAME]--zone [ZONE]
Replace [NAME] with the name of your cluster and
[ZONE] with the compute zone that the cluster is in.
For more information on deleting a GKE cluster, see the
GKE documentation.
Deleting the managed service
If you don't need the data on the Endpoints Services page and in the
Produced API log on the Logs Explorer page, you can delete the managed
service for your API, which removes the data from the Google Cloud console.
To delete the managed service:
Make sure that the gcloud CLI (gcloud) is authorized to access your
data and services on Google Cloud:
gcloud auth login
Enter the following to display the project IDs for your Google Cloud
projects:
gcloud projects list
Using the applicable project ID from the previous step, set the default
Google Cloud project to the one that your application is in:
gcloudconfigsetproject[YOUR_PROJECT_ID]
Obtain the name of all managed services in your Google Cloud project:
gcloud endpoints services list
Delete the service from Service Management. Replace
SERVICE_NAME with the name of the service you want
to remove.
gcloud endpoints services delete SERVICE_NAME
Running gcloud endpoints services delete doesn't immediately delete the
managed service. Service Management disables the managed service for
30 days, which allows you time to restore it if you need to. After 30 days,
Service Management permanently deletes the managed service.
[[["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-07 UTC."],[[["\u003cp\u003eCloud Endpoints utilizes the Extensible Service Proxy (ESP) and Service Management to oversee your API, which is initially set up via the \u003ccode\u003egcloud endpoints services deploy\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eDeleting an API involves either removing the Google Cloud project entirely or specifically deleting the instance hosting ESP and the API backend, along with the associated managed service.\u003c/p\u003e\n"],["\u003cp\u003eCompute Engine instances can be deleted using the \u003ccode\u003egcloud compute instances delete\u003c/code\u003e command, while GKE clusters can be deleted using the \u003ccode\u003egcloud container clusters delete\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eManaged services for APIs can be deleted via \u003ccode\u003egcloud endpoints services delete\u003c/code\u003e, which disables the service for a 30-day grace period before permanent deletion.\u003c/p\u003e\n"],["\u003cp\u003eIf you do not want to lose any data, you do not have to delete the Managed Service.\u003c/p\u003e\n"]]],[],null,["# Deleting an API and API instances\n\n[OpenAPI](/endpoints/docs/openapi/deleting-an-api-and-instances \"View this page for the Cloud Endpoints OpenAPI docs\") \\| gRPC\n\n\u003cbr /\u003e\n\nCloud Endpoints uses the\n[Extensible Service Proxy (ESP)](/endpoints/docs/grpc/glossary#extensible_service_proxy)\nand Service Management to manage your API. When you deployed your\nservice configuration by using the `gcloud endpoints services deploy` command, the\ncommand used Service Management to create a managed service for your API.\n\nTo delete your API you need to:\n\n- Delete the instance that ESP and your API backend is running on.\n- Delete the managed service that was created for your API.\n\nThe easiest way to do both of these tasks is to delete the Google Cloud\nproject that your API is in. If you want to preserve your\nGoogle Cloud project, then you need to delete the instance and the managed\nservice.\n| **Note:** If you encounter issues with Google Cloud project deletion, refer to the [troubleshooting](/resource-manager/docs/troubleshooting-project-deletion) section for resolution.\n\nDeleting instances\n------------------\n\n### Compute Engine\n\nUse the [`gcloud compute instances delete`](/sdk/gcloud/reference/compute/instances/delete)\ncommand. When you delete an instance in this way, the instance shuts down and\nis removed from the list of instances, and all resources attached to the\ninstance are released, such as persistent disks and any static IP addresses.\n\nTo delete an instance, use the following command: \n\n```transact-sql\ngcloud compute instances delete [INSTANCE_NAME] --zone = [ZONE]\n```\n\nFor more information on deleting Compute Engine instances, see the\n[Compute Engine documentation](/compute/docs/instances/stopping-or-deleting-an-instance).\n\n### GKE\n\nTo delete a GKE cluster with the Google Cloud CLI: \n\n```transact-sql\ngcloud container clusters delete [NAME] --zone [ZONE]\n```\n\nReplace `[NAME]` with the name of your cluster and\n`[ZONE]` with the compute zone that the cluster is in.\n\nFor more information on deleting a GKE cluster, see the\n[GKE documentation](/kubernetes-engine/docs/how-to/deleting-a-cluster).\n\nDeleting the managed service\n----------------------------\n\nIf you don't need the data on the **Endpoints Services** page and in the\n**Produced API** log on the **Logs Explorer** page, you can delete the managed\nservice for your API, which removes the data from the Google Cloud console.\n\nTo delete the managed service:\n\n1. Make sure that the gcloud CLI (`gcloud`) is authorized to access your\n data and services on Google Cloud:\n\n gcloud auth login\n\n2. Enter the following to display the project IDs for your Google Cloud\n projects:\n\n gcloud projects list\n\n3. Using the applicable project ID from the previous step, set the default\n Google Cloud project to the one that your application is in:\n\n gcloud config set project [YOUR_PROJECT_ID]\n\n4. Obtain the name of all managed services in your Google Cloud project:\n\n gcloud endpoints services list\n\n5. Delete the service from Service Management. Replace\n \u003cvar translate=\"no\"\u003eSERVICE_NAME\u003c/var\u003e with the name of the service you want\n to remove.\n\n ```\n gcloud endpoints services delete SERVICE_NAME\n ```\n\n Running `gcloud endpoints services delete` doesn't immediately delete the\n managed service. Service Management disables the managed service for\n 30 days, which allows you time to restore it if you need to. After 30 days,\n Service Management permanently deletes the managed service.\n\nWhat's next\n-----------\n\n- To restore a managed service, see\n [Restoring a managed service](/endpoints/docs/grpc/restore-managed-service).\n\n- For information on the `gcloud` commands used on this page, see the\n [gcloud reference](/sdk/gcloud/reference).\n\n- For information on Service Management, see\n [Creating and deleting managed services](/service-infrastructure/docs/create-services)."]]
