From the My APIs page, you can export a single Custom API, OData Service, or API Proxy or a group of APIs into an API Pack (JSON file). The default JSON export file,
apis-export.apk, automatically downloads and saves in your default download folder. The filename increments by one every time you use the export functionality. Each file may be used as a local backup or archive.
The import functionality within the My APIs page allows you to import one or more Custom APIs, OData Service APIs, and API proxies using the
apis-export.apk JSON file. You can migrate a copy of development APIs into testing and production environments or import APIs into a different organization as needed.
You can export a single Custom API, OData Service, or API Proxy directly from the My APIs index page. The API may be published or saved as a draft.
Once you have selected Export, the
apis-export.apk file containing the API metadata downloads automatically.
Select API(s): All APIs within the selected environment display. Click the checkbox in the header row to select all of the APIs. Click the associated checkbox for one or more APIs to select a specific API for export.
apis-export.apkfile automatically downloads to your default download folder.
Warning: You must create new security profiles within the import environment and assign the appropriate profile to each imported API. Once the imported APIs are published, they are immediately public and accessible. By default, the APIs are anonymous until new security profiles are created and assigned to the APIs.
apis-export.apkJSON file that has been exported from API Manager.
apis-export.apkfile. In this step you will select the APIs to import:
apis-export.apkfile display. Click the checkbox in the header row to select all APIs. Click the associated checkbox for one or more APIs to select a specific API for import.
Select APIs: Click the checkbox in the header row to publish all APIs. Click the associated checkbox for one or more APIs to select the specific API(s) to publish in the new environment.
NOTE: The APIs that are not selected will be imported in a draft status.
A popup windows may appear with a message indicating that APIs are invalid for import. Each invalid API along with the specific error will be listed:
NOTE: The selected APIs are published in the new environment and are immediately accessible. The APIs that were not selected to publish are saved in the new environment as drafts. The draft APIs are not accessible in the new environment until they are individually published. To publish the APIs, hover over each API card, select View/Edit on the back side of the card, and select Save & Publish on the Summary & Confirmation page.