Skip to main content
POST
Prepare File Migration

Authorizations

Authorization
string
header
required

User-principal OAuth 2.0 Bearer authentication. Send a user-scoped Auth0 access token (audience = the app API audience) as Authorization: Bearer <jwt>. The request resolves to the user's identity and is authorized by their Role on the {companyId} in the path — the same role-based permissions the web app enforces. This is the path the MCP connector uses to act on a user's behalf; endpoints that accept it list both BearerAuth and ApiKeyAuth.

Path Parameters

companyId
string<uuid>
required

Company identifier

Body

application/json
source
object
required
revision
object
required

Exact source object declaration. At least one base64 checksum from source object metadata is required. Every available common checksum must match destination storage before finalization.

metadata
object
required

Response

Durable migration state

sourceId
string<uuid>
required
fileId
string<uuid>
required
currentVersionId
string<uuid> | null
required
revision
object | null
required

Requested revision, or the active revision when none is supplied; null if absent or its version was reclaimed.

metadata
object
required
conflicts
string[]
required

Stable diagnostic codes, including deleted targets, operator version changes, superseded source revisions, reclaimed versions and infected results.