Skip to main content
GET
Learn more about Box SDK versioning strategy.

Authorizations

Authorization
string
header
required

The access token received from the authorization server in the OAuth 2.0 flow.

Headers

box-version
enum<string>
required

Version header.

Available options:
2026.0

Path Parameters

shuttle_report_id
string
required

The unique identifier for the shuttle report.

Response

Returns the 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.

id
string
required

The unique identifier for the shuttle report.

Example:

"6a3ba8d14f2c91e8370b4d12"

type
enum<string>
required

The value will always be shuttle_report.

Available options:
shuttle_report
Example:

"shuttle_report"

run_id
string
required

The unique identifier of the shuttle run this report was generated for.

Example:

"6a3ba68e810d9156194530a1:42"

status
string
required

The generation status of the report. This is an open string whose set of values is expected to grow; the currently documented values include pending, processing, complete, failed, canceled, and unknown. Keep polling pending and processing. Stop on complete, failed, canceled, and unknown. Treat any value that is not recognized the same as unknown: do not fail parsing, and do not keep polling.

Example:

"complete"

format
enum<string>
required

The output file format of the report.

Available options:
xlsx,
csv
Example:

"xlsx"

output
Shuttle report output · object
required

The generated Box file or folder. Always present; null until status is complete.

Example:
completed_at
string<date-time> | null
required

When report generation finished. Always present; null while generation is still in progress.

Example:

"2026-03-15T06:36:12Z"

sections
string[]

The sections included in the report. Echoes the sections requested on create. This is an open list whose set of values is expected to grow; the currently documented values include files_and_folders, event_log, transfer_overview, source_users, target_users, source_collaborators, target_collaborators, source_collaborations, and target_collaborations. Omitted on older reports that have no stored section list. New reports always include this field.

Minimum array length: 1

A section included in the report.

Example:
users_scope
enum<string>

Which users are included in user-related report sections.

Available options:
migrated,
all
Example:

"migrated"

created_at
string<date-time>

When report generation was requested.

Example:

"2026-03-15T06:35:00Z"

Last modified on October 26, 2026