You have deleted each data source that your API is not using or that your API does not require. For example, you might have test/dev data sources.
For more information about how to delete a data source, see Database Connectivity.

Export using API Creator.
Export using scripts or API calls.

From the APIs page, open the API that you want to export.
The API Properties Details tab appears.
Click 
Export
.
Complete the following fields, and then click 
Export
:
Export type
 
The type of file you want 
CA Live API Creator
 to use as your exported API.
Options:
 
JSON formatted project:
 You want to export your API in JSON file format.
Compressed ZIP file: 
You want to export your API in ZIP file format, with the API details reflected in a hierarchy of directories and files.
Password Export
 
Defines if you want 
CA Live API Creator
 to include your data source password in the API export file, and if you want it included, in what form you want it included.
 
Options:
 
Do not export data source passwords:
 You do not want to include your data source passwords in the API export file. This option is the most secure.
 
Encrypt data source passwords:
 You want to include your data source passwords in the API export file in encrypted form.
Export data source password in plaintext:
 You want to include your data source passwords in the API export file in plaintext form. This option is not secure.
Best Practice: 
If you are in the early stages of development, we recommend that you export data source passwords in plaintext. You can change your passwords after you import an API or (if you are scripting the import process) while you are scripting the import process.
For more information about the team development best practices, see Team Development.

cURL commands to call the CA Live API Creator Admin project API (Admin API) 
The CA Live API Creator Admin command-line interface (Admin CLI) 
The Node SDK 

curl -H "Authorization:CALiveAPICreator ${apikey}:1"
    -X GET "http://localhost:8080/rest/abl/admin/v2/@export?projectId=2000" -o "demo_local.json"

curl -H "Authorization:CALiveAPICreator ${apikey}:1"
    -X GET "http://localhost:8080/rest/abl/admin/v2/@export?urlfragment=demo" -o "demo_local.json"

-- Import API in JSON format
curl -H "authorization: CALiveAPICreator ${apikey}:1" --output import.log  --insecure  -v --fail  
   --form "[email protected];type=application/json" 
   "$http://localhost:8080/rest/abl/admin/v2/@import?namecollision=rename_new&errorhandling=standard"
-- Import API in ZIP format
curl -H "authorization: CALiveAPICreator ${apikey}:1" --output import.log  --insecure  -v --fail  
   --form "[email protected];type=application/zip" 
   "$http://localhost:8080/rest/abl/admin/v2/@import?namecollision=rename_new&errorhandling=standard"

$lacadmin api use --url_name demo
$lacadmin api export --file project_demo.zip --format zip

$lacadmin api export --file project_demo.json --format json --passwordstyle plaintext

$lacadmin api import --file /users/jdoe/project_demo.json --namecollision replace_existing --errorhandling standard

$lacadmin api import --file project_demo.zip --namecollision disable_and_rename_existing --errorhandling best_efforts

{d} - Directory
{f} - File
  File Extensions:
     .json JSON object definition files
     .js JavaScript for a specific object (zero byte files are placeholders)
     .sql SQL definitions used by FreeSQL and Rule qualifications
     .html HTML formatted files used in topics
     .md Markdown format for Readme files (placeholder for empty directories)

"{f}api.json": {    
   "name": "demo_new",    
   "urlFragment": "test",    
    "comments": null,    
    "isEnabled": true,    
    "authProviderName": "Built-in authentication"  
  },  
  "{f}exportoptions.json": {    
    "passwordStyle": "ENCRYPTED"  
  }

 Import using API Creator.
 Import using scripts or API calls.

In API Creator, from the APIs page, click 
Import
.
The Import API window opens.
Complete the following steps:
Click 
Select file to upload
, select the exported JSON or ZIP file that you want to import, and then click 
Open
.
Select one of the following options from the 
Import Options
 drop-down, and then click 
Import
:
Rename API if API name or URL fragment exist
Disable and rename existing API if API name or URL fragment match
Do not import if API name or URL fragment conflict
 
Replace existing API if API name or URL fragment match
Default:
 Rename API if API name or URL fragment exist
The JSON or ZIP file is imported into API Server as a new API.
If you imported the API from an exported JSON file that includes active connections and listeners, enable your API.
CA Live API Creator
 marks the connections as active and restarts the listeners.
For more information about connections and listeners, see Creating Listeners.

Stop all nodes in the cluster.
Import your API.
Restart the nodes.

Respecify the data source password by completing the following steps:
With your API open, in the Create section, click 
Data Sources
.
Respecify the data source password in the 
Password
 field, and then save your changes.
If you imported the API from an exported JSON file that includes active listeners and connections, respecify the passwords for each connection by completing the following steps:
In the Manage section, click 
Listeners
.
Click the 
Connections
 tab.
Click the 
Parameters
 tab.
Respecify the 
password
 parameter value, and then save your changes.
Verify the authentication provider and the URL name for your API by completing the following steps:
In the Create section, click 
API Properties
.
The Details page appears by default.
Verify the authentication provider in the 
Authentication provider
 field.
(Optional) Respecify the URL name for your API in the 
URL fragment
 field, which includes the timestamp of the import, and then save your changes.
If you are using the 
built-in authentication
 authentication provider, specify the passwords for the API users by completing the following steps:
In the Manage section, click 
Users
.
The API Users page appears. 
Specify the password for the API user in the 
Password
 field, and then save your changes.
For more information about how to manage API users, see Manage API Users using the Built-in Authentication Provider.

$lacadmin api use --url_name demo
$lacadmin api extract --file project_demo.zip --directory /Users/johndoe/temp/demo --synchronize replace

$lacadmin teamspace exportRepos --file allmyapis.zip --format zip --passwordstyle encrypted

lacadmin api export --section listeners --section_filter “name=xyz” --file listeners.zip --format zip

passwordstyle

skip

encrypted

plaintext

librarystyle

emit_all

in_use_only

namecollision

fail

rename_new

replace_existing

disable_and_rename_existing