Export Package
POST/exportTransportPackage
This API creates a compressed file containing objects specified for T2P migration.
The Authorization
must have Bearer
followed by Token
.
Mandatory params:
exportonline
(can be true or false) - Determines if package needs to be exported online, exportpath
(if exportonline is false) - Local path where export package will be generated, environmentname
(if exportonline is true) - Name of the environment which can be created at the following path : Admin -> Global Configurations -> Misc -> Transport -> Add New Transport, objectstoexport
- Supported objects : savRoles
, emailTemplate
, roles
, analyticsV1
, analyticsV2
, globalConfig
, workflows
, connection
, appOnboarding
, userGroups
, scanRules
, organizations
, securitySystems
Optional params:
updateuser
- username of the user exporting the package, transportmembers
(can be true or false) - option to transport members for selected objects such as SAV role, transportowner
(can be true or false) - option to transport owners for selected objects, businessjustification
Request
- application/json
Body
objectstoexport
object
Responses
- 200
Export Package - Success
Response Headers
Date
string
Set-Cookie
string
Strict-Transport-Security
string
Vary
string
X-Content-Type-Options
string
- application/json
- Schema
- Example (from schema)
- Export Package - Success
Schema
{
"errorcode": 0,
"fileName": "transport_admin_2023-01-13_10-19-11(UTC).zip",
"msg": "success",
"msgDescription": "Export Requested. If other requests are currently processing, your export will begin after they complete. You can call /transportPackageStatus API to check the status of your export."
}
{
"errorcode": 0,
"fileName": "transport_admin_2023-01-13_10-19-11(UTC).zip",
"msg": "success",
"msgDescription": "Export Requested. If other requests are currently processing, your export will begin after they complete. You can call /transportPackageStatus API to check the status of your export."
}