Apigee in Cloud console

To edit an API proxy and save your changes using the Apigee Cloud console:

1. In the Google Cloud console, go to theProxy development> API proxies page.

   Go to API proxies

2. Select the proxy that you want to edit from the list of proxies. The UI displays theOverview tab for that proxy in the Google Cloud console.

   
3. Click theDevelop tab to make your changes to the proxy.
   
   For example, to add a policy, click the+ icon next toPolicies, select the policy to add, enter a name and an optional display name, clickCreate, and configure the policy in the interface.
   
4. When you are done making changes, you can do one of the following:
   • To save your changes butnot create a new revision, click theSave button. (You should do this periodically to ensure that your changes are not lost if you end the session).
   • To save your changes as a new revision (when you are getting ready to deploy and test), click the drop-down menu next to theSave button and selectSave as new revision:

     

     The Apigee UI saves your changes and generates a new revision of the proxy for you. It does not deploy the new bundle to the runtime; you must explicitly do that, as described inDeploying an API proxy.

Classic Apigee

To edit an API proxy and save your changes using the classic Proxy Editor:

1. Sign in to theApigee UI.
2. ClickAPI Proxies in the main view.

   Alternatively, you can selectDevelop > API Proxies in the left navigation menu.

3. Select the environment that contains the proxy you want to edit.

   The Apigee UI displays a list of API proxies for the selected environment:

   

4. Click the proxy that you want to edit. The UI displays theOverview tab for that proxy in the Proxy Editor:

   

5. Click theDevelop tab in the upper right of the view.
6. Use the proxy editor to make your changes to the proxy. When you are done making changes, you can do one of the following:
   • Save your changes but do not create a new revision (most common; you should do this periodically to ensure that your changes are not lost if you end the session).
   • Save your changes as a new revision (when you are getting ready to deploy and test).
7. To save butnot create a new revision, clickSave in the upper right of the UI:

   

   The Apigee UI saves your changes so that you can leave the page and resume working later.

8. To save your changes as a new revision, click the drop-down arrow next toSave and selectSave as new revision:

   

   The Apigee UI saves your changes and generates a new proxy bundle for you. It does not deploy the new bundle to the runtime; you must explicitly do that, as described inDeploying an API proxy.

   The UI displays aNew revision saved message:

   

   After you create a new revision, you typically deploy it to your cluster, as described inDeploying an API proxy.

Apigee API

Edit an API proxy to create a revision in your Apigee organization by issuing aPOST request to the following resource:

https://apigee.googleapis.com/v1/organizations/$ORG/apis

You must define the name of the API proxy using thename query parameter. Restrict the characters used in the name to the following:A-Za-z0-9._\-$ %

Optionally, you can import an API proxy configuration bundle by performing the following steps:

• Set theaction query parameter toimport
• Set theContent-type header tomultipart/form-data
• Pass the name of the API proxy configuration bundle on your local file system

The following example demonstrates how to edit an API proxy by importing an API proxyconfiguration bundle (helloworld-config.zip) on your local file system using theAPI.

export TOKEN=$(gcloud auth print-access-token)export ORG=ORGANIZATION_NAMEcurl "https://apigee.googleapis.com/v1/organizations/$ORG/apis?name=helloworld&action=import" \  -X POST \  -H "Authorization: Bearer$TOKEN" \  -H "Content-type: multipart/form-data" \  -F "file=@helloworld-config.zip"

Where$TOKEN is set to your OAuth 2.0 access token, as described inObtaining an OAuth 2.0 access token. For information about thecurl options used in this example, seeUsing curl. For a description of environment variables you can use, seeSettingenvironment variables for Apigee API requests.

The following provides an example of the response output:

{"basepaths":["/helloworld"],"configurationVersion":{"majorVersion":4},"createdAt":"1559145292799","displayName":"helloworld","entityMetaDataAsProperties":{"bundle_type":"zip","subType":"Proxy","lastModifiedAt":"1559145292799","createdAt":"1559145292799"},"lastModifiedAt":"1559145292799","name":"helloworld","policies":["verify-api-key","remove-query-param-apikey","OAuth-v20-1"],"proxies":["default"],"proxyEndpoints":["default"],"resourceFiles":{},"targetEndpoints":["default"],"targets":["default"],"type":"Application","revision":"1","description":"Hello world"}

For more information on editing an API proxy, see theapis.create method in the Apigee API. To see all the methods available for API proxies, see theAPI proxies API.