When you delete an API proxy, Apigee
removes that API proxy and undeploys it from the cluster.
Deleting an API proxy is similar to undeploying an API proxy,
except that you can return to edit the revision that you undeploy. If you delete the API proxy, it is no
longer available to edit.
Apigee Cloud console
To delete an API proxy using the Google Cloud console:
In the Google Cloud console, go to the Proxy development > API proxies page.
[[["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-26 UTC."],[[["\u003cp\u003eThis guide outlines how to delete API proxies in both Apigee and Apigee hybrid environments, removing the proxy and undeploying it from the cluster.\u003c/p\u003e\n"],["\u003cp\u003eDeleting an API proxy is a permanent action that makes it unavailable for future edits, unlike undeploying, which allows returning to edit the revision.\u003c/p\u003e\n"],["\u003cp\u003eYou can delete an API proxy using the Apigee UI by selecting the proxy, clicking the trash can icon under "Actions," and confirming the deletion.\u003c/p\u003e\n"],["\u003cp\u003eAlternatively, API proxies can be deleted via the Apigee API by issuing a DELETE request to the specified resource URL after ensuring the proxy has been undeployed.\u003c/p\u003e\n"],["\u003cp\u003eDeleting an API proxy does not trigger a rollback to a previous version.\u003c/p\u003e\n"]]],[],null,["# Deleting an API proxy\n\n*This page\napplies to **Apigee** and **Apigee hybrid**.*\n\n\n*View [Apigee Edge](https://docs.apigee.com/api-platform/get-started/what-apigee-edge) documentation.*\n\n| **More Information** \n|\n| For more information, see:\n|\n| - [Best practices for API proxy design and development](/apigee/docs/api-platform/fundamentals/best-practices-api-proxy-design-and-development)\n\nWhen you delete an API proxy, Apigee\nremoves that API proxy and undeploys it from the cluster.\n\nDeleting an API proxy is similar to [undeploying an API proxy](/apigee/docs/api-platform/deploy/ui-undeploy),\nexcept that you can return to edit the revision that you undeploy. If you delete the API proxy, it is no\nlonger available to edit. \n\n### Apigee Cloud console\n\nTo delete an API proxy using the Google Cloud console:\n\n1. In the Google Cloud console, go to the **Proxy development \\\u003e API proxies** page.\n\n [Go to API proxies](https://console.cloud.google.com/apigee/proxies)\n2. In the row for the proxy you want to delete, under **Actions** , click delete **Delete**.\n3. In the confirmation dialog, click **Delete**.\n\n### Classic Apigee UI\n\nTo delete an API proxy in the Apigee UI:\n\n1. Select **Develop \\\u003e API Proxies**\n and in the **Proxies** pane, select the environment for the proxy.\n\n2. In the row for the proxy you want to delete, under **Actions**, click the trash can icon.\n3. In the confirmation dialog, click **Delete**.\n\n| **Note** : Deleting the API proxy does *not* trigger a rollback to a previous revision of the proxy.\n\nFor information on how to check the status of the newly deleted proxy, see\n[Viewing deployment status](/apigee/docs/api-platform/deploy/ui-deploy-overview#viewing-deployment-status).\n\n### Apigee API\n\nDelete an API proxy in your Apigee organization by issuing a DELETE request to the following\nresource: \n\n```\nhttps://apigee.googleapis.com/v1/organizations/$ORG/apis/$API\n```\n| **Note:** An API proxy must be [undeployed](/apigee/docs/api-platform/deploy/ui-undeploy) before you can delete it.\n\nFor example, to delete the helloworld API proxy: \n\n```\ncurl \"https://apigee.googleapis.com/v1/organizations/myorg/apis/helloworld\" \\\n -X DELETE \\\n -H \"Authorization: Bearer $TOKEN\"\n```\n\nWhere `$TOKEN` is set to your OAuth 2.0 access token, as described in\n[Obtaining an OAuth 2.0 access token](/apigee/docs/api-platform/get-started/api-get-started#oauth20). For information about the `curl` options used in this example, see\n[Using curl](/apigee/docs/api-platform/get-started/api-get-started#curl). For a description of environment variables you can use, see\n[Setting\nenvironment variables for Apigee API requests](/apigee/docs/api-platform/get-started/api-get-started#api-environment-variables).\n\nThe following provides an example of the response output: \n\n```text\n{\n \"metaData\": {\n \"createdAt\": \"1559145292799\",\n \"lastModifiedAt\": \"1559145292799\",\n \"subType\": \"Proxy\"\n },\n \"name\": \"helloworld\",\n \"revision\": [\n \"1\"\n ]\n}\n```\n\nFor more information, see the [API proxies API](/apigee/docs/reference/apis/apigee/rest/v1/organizations.apis)."]]