Skip to main content
Endpoints for managing Box Shuttle, the service that migrates content into Box from external sources. Use these endpoints to manage the systems that Shuttle migrates content from and the migration jobs that Shuttle runs.

Shuttle agent credentials

The installation credentials issued for a Windows shuttle system. The registration token is pasted into the Windows agent installer to register the agent with its system.
Example

Shuttle discovered subject

A subject discovered on the source system during a scan, with an optional suggested Box target.
Example

Shuttle discovered subjects

A paginated list of subjects discovered on the source system.
Example

Shuttle job

A standard representation of a shuttle job. A shuttle job describes a migration of content from a source system into Box, including its current state, mapping-preparation state, and mapping configuration.
Example

Shuttle job create request

The request body used to create a new shuttle job.
Example

Shuttle job permission conflict strategy

The strategy used to resolve permission conflicts.
Example

Shuttle job schedule

A schedule that starts runs of a shuttle job. A schedule is either time-based or triggered by another job’s run. Schedules cannot start a run in scan mode.
Example

Shuttle job schedule create request

The request body used to create a shuttle job schedule.
Example

Shuttle job schedule trigger

When a shuttle job schedule should start a run. Exactly one trigger variant is present, discriminated by type.
Example

Shuttle job schedule trigger by job

A job-based trigger that starts this schedule after another shuttle job’s run meets a condition.
Example

Shuttle job schedule trigger by time

A time-based trigger that starts the schedule at a wall-clock time and optionally repeats.
Example

Shuttle job schedule update request

The request body used to update an existing shuttle job schedule. Only the fields supplied in the request body are changed.
Example

Shuttle job schedules

A paginated list of shuttle job schedules.
Example

Shuttle job start request

The request body used to start a shuttle job.
Example

Shuttle job update request

The request body used to update an existing shuttle job. Only the fields supplied in the request body are changed.
Example

Shuttle jobs

A paginated list of shuttle jobs.
Example

Shuttle mapping error

A problem encountered while preparing path, subject, or permission mappings for a shuttle job.
Example

Shuttle mapping errors

A paginated list of shuttle mapping errors.
Example

Shuttle path entries

A paginated list of shuttle path entries.
Example

Shuttle path entry

A browsable entry on the source or target system used to build shuttle path mappings. Shared fields describe the node. scope is a discriminated object that identifies the mapping namespace so a path mapping can be created from this row without extra browse state.
Example

Shuttle path entry account scope

The mapping scope of a path entry that lives under a user or service account. type is the discriminator. The remaining fields are the account itself, flattened onto this object — they are not a nested account wrapper. id here is the account identifier, not the path entry id. Copy these fields onto account when creating an account-scoped path mapping.
Example

Shuttle path entry scope

Which mapping namespace this path entry belongs to. Discriminated by type: account flattens the owning account onto the object; shared_space carries the shared container name. File versus folder is not part of scope. Use is_directory on the path entry.
Example

Shuttle path entry shared space scope

The mapping scope of a path entry that lives under a shared container such as a site, team drive, bucket, or file share. type is the discriminator. Copy space onto a shared-space path mapping location when creating a mapping from this row.
Example

Shuttle path mapping

A standard representation of a shuttle path mapping. A path mapping connects a source location on the migrated system to a destination in Box, or marks the source path as skipped.
Example

Shuttle path mapping account

The account that owns an account-scoped path mapping location.
Example

Shuttle path mapping account input

The account that owns an account-scoped path mapping location. Provide at least one of id or email.
Example

Shuttle path mapping account location

A path mapping location scoped to a user or service account.
Example

Shuttle path mapping account location input

An account-scoped source location supplied when creating or updating a path mapping.
Example

Shuttle path mapping account location target input

An account-scoped destination location supplied when creating or updating a path mapping.
Example

Shuttle path mapping create request

The request body used to create a new shuttle path mapping.
Example

Shuttle path mapping import create request

The request body used to import a shuttle job’s path mappings from a spreadsheet already stored in Box.
Example

Shuttle path mapping location

One side of a path mapping. The object shape is determined by type.
Example

Shuttle path mapping location input

A source location supplied when creating or updating a path mapping. The object shape is determined by type.
Example

Shuttle path mapping shared space location

A path mapping location scoped to a shared container such as a site, team drive, bucket, or file share.
Example

Shuttle path mapping shared space location input

A shared-container source location supplied when creating or updating a path mapping.
Example

Shuttle path mapping shared space location target input

A shared-container destination location supplied when creating or updating a path mapping.
Example

Shuttle path mapping target location input

A destination location supplied when creating or updating a path mapping. The object shape is determined by type. Destination input does not include is_directory; that flag is taken from the source.
Example

Shuttle path mapping update request

The request body used to update an existing shuttle path mapping. Only the fields supplied in the request body are changed. job_id, id, and type are immutable.
Example

Shuttle path mappings

A paginated list of shuttle path mappings.
Example

Shuttle report

A report generated asynchronously for a shuttle job run. Keep polling while status is pending or processing. Stop when status is complete, failed, canceled, or unknown. The generated Box file or folder is null until generation finishes.
Example

Shuttle report create request

The request body used to generate a report for a shuttle run. Generation is asynchronous: the created report is returned immediately in pending or processing status. Poll GET /shuttle_reports/{shuttle_report_id} while status is pending or processing. Stop when status is complete, failed, canceled, or unknown. Repeating this request with the same parameters reuses the existing report instead of creating a duplicate.
Example

Shuttle report output

A reference to the generated Box file or folder.
Example

Shuttle reports

A paginated list of shuttle reports.
Example

Shuttle run

A historical instance of a shuttle job run. A run is created each time a job is started. Run IDs have the form {job_id}:{run_number}.
Example

Shuttle runs

A paginated list of shuttle runs.
Example

Shuttle subject

A subject discovered on the source migration system, such as a user or group.
Example

Shuttle subject mapping

A standard representation of a shuttle subject mapping. A subject mapping connects a discovered source subject to a Box user or group, or marks the subject as skipped.
Example

Shuttle subject mapping create request

The request body used to create a new shuttle subject mapping.
Example

Shuttle subject mapping import create request

The request body used to import a shuttle job’s subject mappings from a spreadsheet already stored in Box.
Example

Shuttle subject mapping update request

The request body used to update an existing shuttle subject mapping. Only the fields supplied in the request body are changed. job_id, id, type, source, discovered_subject_id, and revision are immutable.
Example

Shuttle subject mappings

A paginated list of shuttle subject mappings.
Example

Shuttle system

A standard representation of a shuttle system. A shuttle system describes a source or destination that Shuttle can migrate content to or from, along with its current connection state.
Example

Shuttle system create request

The request body for creating a shuttle system. Only Windows agent systems can be created through the public API, so system_type must be windows.
Example

Shuttle system update request

The request body for updating a shuttle system. Only the fields supplied are changed.
Example

Shuttle systems

A paginated list of shuttle systems.
Example

Shuttle target subject

A Box user or group that a source subject is mapped to.
Example

Shuttle target subject input

A Box user or group to map a source subject to.
Example
Last modified on October 26, 2026