Reads the platform again (as previewPlatformImport) and creates the
picked things (items, all by default): a project per project there,
its services with their variables (secret ones sealed), domains (live
after the first deploy), ports and empty volumes, a project per Compose
stack, and databases. A Postgres or MySQL database reachable from
outside the platform is copied by a database import; others are made
empty or left for you. Services aren't deployed unless deploy.
Running it again skips what an earlier import made. Owners and admins.
API key access: full.
apiKeyAuthorizationBearer <pyo_…>An API key from the dashboard's API keys page: Authorization: Bearer pyo_…. Keys can expire, and an expired one gets a 401.
application/jsonteamId*stringplatform*Platform"coolify""dokploy"url*stringtoken*stringRead again for this request, never stored.
clusterId?|Where the services and databases go. The team's default cluster when omitted.
items?array<string>|The keys to import, from the preview. All of them when omitted.
deploy?booleanDeploy each service once it's made. Off: they're saved, stopped, to deploy when you like.
What became of each picked thing.
application/jsonok*booleanresults*array<>curl -X POST 'https://your-pyo.example.com/api/v1/platform-imports' \
-H 'Content-Type: application/json' \
-d '{
"teamId": "string",
"platform": "coolify",
"url": "string",
"token": "string"
}'{
"ok": true,
"results": [
{
"key": "string",
"name": "string",
"state": "string",
"message": "string",
"id": "string",
"projectId": "string"
}
]
}