POST
Import schemas
Request · Response · Guide: Extract fields
Request:
  • Content-Type: multipart/form-data
  • file (file, required): The exported zip file
Response:
  • success (boolean): Whether the import was successful
  • importedBlueprintsCount (number): Number of blueprints imported
  • importedSchemasCount (number): Number of schemas imported
  • conflictBlueprintsCount (number): Number of blueprints that had conflicts
  • conflictBlueprints (string[]): List of conflicting blueprint class names
  • blueprintIds (string[]): IDs of the imported blueprints
  • schemaIds (string[]): IDs of the imported schemas
Notes:
  • All imported blueprints and schemas will be assigned new IDs
  • Metadata (organization, workspace, user) will be updated to the importing user
  • If a blueprint with the same class name already exists, the import will fail

Authorizations

x-api-key
string
header
required

API key for authentication

Headers

Idempotency-Key
string

Optional opaque key (max 255 chars, UUIDv4 recommended) making this request idempotent for 24h: a retry with the same key and body replays the original response with Idempotent-Replayed: true.

Body

application/json

Exported zip file

file
file

Response

Schemas imported successfully

success
boolean
required

Import success status

importedBlueprintsCount
number
required

Number of blueprints imported

importedSchemasCount
number
required

Number of schemas imported

conflictBlueprintsCount
number
required

Number of conflicting blueprints

conflictBlueprints
string[]
required

List of conflicting blueprint class names

blueprintIds
string[]
required

List of imported blueprint IDs

schemaIds
string[]
required

List of imported schema IDs