Import & Export
Zerq supports bulk import and export of collections as JSON. Use this to copy configurations between environments, back up your API catalog, or migrate from another gateway.
Exporting collections
Export a single collection
- Open the collection detail page
- Click Export (download icon)
- A JSON file is downloaded containing the full collection and all its proxies
Bulk export
- Go to the Collections list
- Check the boxes next to the collections you want to export
- Click Export Selected
- A single JSON file is downloaded with all selected collections
Importing collections
- Go to Collections
- Click Import
- Upload the JSON file
- Choose the import mode:
| Mode | Behavior |
|---|---|
| Merge | Add new collections; update existing ones if IDs match |
| Replace | Delete all existing collections and replace with the imported set |
Replace mode
Replace mode permanently deletes all existing collections. Use with caution.
- Click Import to confirm
All imported proxies are created in draft status regardless of their status in the export file. Review and publish them after import.
JSON format
The export format is a JSON array of collection objects:
[
{
"name": "Payments API",
"description": "Payment processing endpoints",
"base_path": "/payments",
"endpoint": "https://payments.internal",
"status": "published",
"proxies": [
{
"name": "List Transactions",
"path": "/transactions",
"methods": ["GET"],
"target_path": "/v2/transactions",
"status": "published"
}
]
}
]
Use cases
Promote from dev to production
- Export the collection from your dev environment
- Import it into production with Merge mode
- Review and update the target endpoint (dev backend → prod backend)
- Attach production credentials
- Publish
Backup
Regularly export all collections and store the JSON files in version control or object storage.
Migrate from another gateway
Export your API configuration from another gateway, convert it to Zerq's JSON format, and bulk import. Use the OpenAPI import for gateway configs that can be exported as OpenAPI specs.