- Enable reusable configuration templates for tenant onboarding.
- Export configuration entities from an existing tenant.
- Import configuration templates into a new tenant through a secure URL.
- Support API-driven onboarding using signed S3-backed template files.
- Enforce 4-hour access control for template URLs.
- Track template metadata & status.
The scope is limited to onboarding only. Features such as versioning, rollback, or diff support are not included.
Supported Configuration Entities
A template can include one or more of the following entities:configsruleszonesnetworksgeosattributescounterstargetConfigsppsConfigsholdConfigs
Step 1: Create and Export the Configuration Template
Use theactions/export endpoint to generate a new configuration template.
Step 2: Check the Export Status
Check the status until it reachesFINISHED.
Step 3: Send the Template to your Production Tenant
Use thedownloadUrl as the <S3_URL> value to configure your production account.
200 OK status.
Once complete, you must wait for the import to finish which can take up to 10 minutes. You can confirm if the import was successful by checking the UI or using an API GET endpoint for one of your configurations.
For example, if you imported geography configurations, you can use the /v3/location-geographies/search endpoint to make a POST request and review your data.
Notes on Expiry & Reusability
- The
downloadUrlexpires 4 hours after creation. - To refresh, call the export-status endpoint again.
- Templates are stateless and may be reused until expiry.
