Decomprimi il proxy API sul sistema locale. Ciò è utile per configurare
lo sviluppo di proxy API basati su file nel controllo del codice sorgente o per visualizzare la versione
basata su file delle risorse. Se modifichi la configurazione del proxy API localmente,
puoi caricare le modifiche come nuova revisione del proxy API.
Per visualizzare i contenuti del pacchetto di configurazione del proxy API, crea una nuova directory ed espandi il file zip utilizzando un'utilità come unzip,
come mostrato nell'esempio seguente:
Caricamento di un pacchetto di configurazione di proxy API
Prima di caricare un pacchetto di configurazione di proxy API, ricomprimi la directory del pacchetto di configurazione di proxy API se l'hai modificata,
inclusi eventuali file nuovi o modificati. Puoi utilizzare un
utilità come zip, come mostrato nell'esempio seguente:
Seleziona la revisione del proxy API che vuoi scaricare nel menu a discesa Revisione.
Seleziona Revisione n > Importa revisione.
Fai clic su Scegli file, vai al file zip nella directory locale e fai clic su Apri.
Fai clic su Carica.
Se ricevi un errore, ad esempio Bundle is invalid. Empty bundle, assicurati che
la directory di primo livello del file zip sia /apiproxy. In caso contrario, archivia nuovamente i file di configurazione del proxy API dalla radice della directory espansa.
Dopo aver caricato la nuova configurazione del proxy API, Apigee incrementa il numero di revisione e
visualizza la nuova revisione. Apigee non esegue il deployment della nuova revisione automaticamente dopo il caricamento. Per eseguire il deployment della nuova revisione, consulta Deployment di un proxy API.
[[["Facile da capire","easyToUnderstand","thumb-up"],["Il problema è stato risolto","solvedMyProblem","thumb-up"],["Altra","otherUp","thumb-up"]],[["Difficile da capire","hardToUnderstand","thumb-down"],["Informazioni o codice di esempio errati","incorrectInformationOrSampleCode","thumb-down"],["Mancano le informazioni o gli esempi di cui ho bisogno","missingTheInformationSamplesINeed","thumb-down"],["Problema di traduzione","translationIssue","thumb-down"],["Altra","otherDown","thumb-down"]],["Ultimo aggiornamento 2025-09-04 UTC."],[[["\u003cp\u003eThis guide details how to download and upload API proxy configuration bundles in Apigee and Apigee hybrid.\u003c/p\u003e\n"],["\u003cp\u003eDownloading an API proxy bundle can be done through the Apigee UI by exporting a specific revision or by using the Apigee API.\u003c/p\u003e\n"],["\u003cp\u003eAPI proxy bundles can be downloaded to import into another organization, set up file-based development, or review file-based versions.\u003c/p\u003e\n"],["\u003cp\u003eUploading an API proxy bundle through the Apigee UI can create a new API proxy or a new revision of an existing proxy, while using the Apigee API allows for updating an existing revision.\u003c/p\u003e\n"],["\u003cp\u003eUploaded API proxy bundles must have \u003ccode\u003e/apiproxy\u003c/code\u003e as the top-level directory in the zip file, and a new revision is not automatically deployed after upload.\u003c/p\u003e\n"]]],[],null,["# Downloading and uploading an API proxy configuration bundle\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\nYou may want to download an API proxy configuration bundle (as a zip file) from Apigee to perform one of the following tasks:\n\n- Import an API proxy using the API proxy configuration bundle to another organization, as described in [Importing an API proxy from an API proxy bundle](/apigee/docs/api-platform/fundamentals/build-simple-api-proxy#importinganapiproxyfromanapiproxybundle).\n- Unzip the API proxy to your local system. This is useful for setting up file-based API proxy development in source control or viewing the file-based version of the resources. If you modify the API proxy configuration locally, you can [upload your changes as a new revision of your API proxy](#upload).\n\n\nThe following sections describe how to [download](#download) and [upload](#upload) an API proxy configuration bundle.\nFor information about the expanded contents of the zip file, see\n[API proxy configuration directory structure](/apigee/docs/api-platform/reference/api-proxy-configuration-reference).\n\nVideo\n-----\n\n| **Note:** This video was recorded with a previous version of the Apigee UI; however, the concepts are still valid.\n\nWatch the following video to learn more about downloading and uploading an API proxy configuration bundle.\n\nDownloading an API proxy configuration bundle\n---------------------------------------------\n\n\nDownload an API proxy configuration bundle, as described in the following sections. \n\n### Apigee Cloud console\n\nTo download an API proxy configuration bundle 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. Select the desired API proxy.\n3. Click the **Develop** tab.\n4. Select the API proxy revision that you want to download in the **Revision** menu.\n5. Click more_vert **More revision actions \\\u003e Export revision \u003cvar translate=\"no\"\u003en\u003c/var\u003e** , where \u003cvar translate=\"no\"\u003en\u003c/var\u003e specifies the selected revision.\n\n### Classic Apigee UI\n\nTo download an API proxy configuration bundle using the Apigee UI:\n\n1. [Open the API proxy in the API proxy editor](/apigee/docs/api-platform/develop/ui-edit-proxy).\n2. Click the **Develop** tab.\n3. Select the API proxy revision that you want to download in the **Revision** drop-down.\n4. Select **Revision \u003cvar translate=\"no\"\u003en\u003c/var\u003e \\\u003e Export revision \u003cvar translate=\"no\"\u003en\u003c/var\u003e** , where \u003cvar translate=\"no\"\u003en\u003c/var\u003e specifies the selected revision.\n\n### Apigee API\n\n\nTo download an API proxy configuration bundle using the API, see [Get API proxy revision](/apigee/docs/reference/apis/apigee/rest/v1/organizations.apis.revisions/get).\n\n\nTo view the contents of the API proxy configuration bundle, create a new directory and expand the zip file using a utility such as `unzip`,\nas shown in the following example: \n\n mkdir myappdir\n unzip ./my-app_app_rev3_2019_04_20.zip -d myappdir\n\nFor more information about the expanded contents of the zip file, see\n[API proxy configuration directory structure](/apigee/docs/api-platform/reference/api-proxy-configuration-reference#apiproxystructure).\n\nUploading an API proxy configuration bundle\n-------------------------------------------\n\n\nBefore you upload an API proxy configuration bundle, re-archive the API proxy configuration bundle directory if you have modified it,\nincluding any new or changed files. You can use a\nutility such as `zip`, as the following example shows: \n\n```\nzip my-new-proxy.zip -r .\n```\n\nThe top-level directory in the zip file must be `/apiproxy`. For more information about the required directory structure,\nsee [API proxy configuration directory structure](/apigee/docs/api-platform/reference/api-proxy-configuration-reference#apiproxystructure).\n| **Note:** There are no special requirements for the zip file name. For example, you do not need to increment the revision number or specify the date in the file name, unless you find it useful for debugging or source control.\n\n\nUpload an API proxy configuration bundle, as described in the following sections. \n\n### Apigee Cloud console\n\nTo upload an API proxy configuration bundle and create a **new revision of an existing API proxy**:\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. Select the desired API proxy.\n3. Click the **Develop** tab.\n4. Click more_vert **More revision actions \\\u003e Import revision**.\n5. Click **Browse** and navigate to the zip file in your local directory and click **Open**.\n6. Click **Import**.\n\n### Classic Apigee UI\n\n\nTo upload an API proxy configuration bundle and **create a new API proxy** , see\n[Importing an API proxy from an API proxy bundle](/apigee/docs/api-platform/fundamentals/build-simple-api-proxy#importinganapiproxyfromanapiproxybundle)\n\nTo upload an API proxy configuration bundle and create a **new revision of an existing API proxy**:\n\n1. [Open the API proxy in API proxy editor](/apigee/docs/api-platform/develop/ui-edit-proxy).\n2. Click the **Develop** tab.\n3. Select the API proxy revision that you want to download in the **Revision** drop-down.\n4. Select **Revision \u003cvar translate=\"no\"\u003en\u003c/var\u003e \\\u003e Import revision**.\n5. Click **Choose File** and navigate to the zip file in your local directory and click **Open**.\n6. Click **Upload**\n\n If you get an error, such as `Bundle is invalid. Empty bundle`, then make sure\n your zip file's top-level directory is `/apiproxy`. If it isn't, re-archive your\n API proxy configuration files from the root of the expanded directory.\n\nAfter uploading your new API proxy configuration, Apigee increments the revision number and\ndisplays the new revision. Apigee **does not** deploy the new revision automatically after you upload it. To deploy the new revision, see [Deploying an API proxy](/apigee/docs/api-platform/deploy/ui-deploy-new).\n\n### Apigee API\n\n\nTo upload an API proxy configuration using the API, see [Update an existing API proxy revision](/apigee/docs/reference/apis/apigee/rest/v1/organizations.apis.revisions/updateApiProxyRevision)"]]
