Everything startDatabaseImport checks, without importing. The cluster
connects to the source, which must be reachable from there, and checks
the login, TLS, its version, its extensions and that every table is
readable. It also checks that the database to import into is empty.
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/jsonAn import: where to (databaseId, or newDatabase), and from where
(url, or uploadId).
teamId*stringengine*string"postgres" or "mysql".
databaseId?|An existing, empty database of the team's to import into.
newDatabase?null|url?|The database to copy, as a URL the cluster can reach: postgres://user:password@host:5432/database or mysql://user:password@host:3306/database, with ?sslmode=require (or ssl-mode=REQUIRED), verify-ca or verify-full for TLS.
uploadId?|Or a dump uploaded first (createDatabaseDumpUpload, then its file sent).
It can be imported: source (version, sizeBytes), and extensions: turnedOn (Pyo turns them on first) and madeByImport.
application/jsoncurl -X POST 'https://your-pyo.example.com/api/v1/database-imports/check' \
-H 'Content-Type: application/json' \
-d '{
"teamId": "string",
"engine": "string"
}'{}