How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Box Uploads (Chunked) API

The chunked upload endpoints support files from20MB in size and allow an applicationto upload the file in parts,allowing for more control to catch any errorsand retry parts individually.

Box Uploads (Chunked) API is one of 81 APIs that Box publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Uploads (Chunked). The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 7 operations across 5 paths, and defines 20 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.box.com/2.0.

7 operations 5 paths 20 schemas 1 DELETE2 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://account.box.com/api/oauth2
Authentication
OAuth 2.0
Contact
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Box Uploads (Chunked) API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2Security) using the authorizationCode flow, exposing 9 scopes. By default, every request must be authenticated.

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 1 DELETE, 2 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Uploads (Chunked) 7

The chunked upload endpoints support files from 20MB in size and allow an application to upload the file in parts, allowing for more control to catch any errors and retry parts in…

POST
/files/upload_sessions
Box Create upload session
post_files_upload_sessions body → 201400403404409default
POST
/files/{file_id}/upload_sessions
Box Create upload session for existing file
post_files_id_upload_sessions 1 param body → 201409default
GET
/files/upload_sessions/{upload_session_id}
Box Get upload session
get_files_upload_sessions_id 1 param → 200default
PUT
/files/upload_sessions/{upload_session_id}
Box Upload part of file
put_files_upload_sessions_id 3 params body → 200409412416default
DELETE
/files/upload_sessions/{upload_session_id}
Box Remove upload session
delete_files_upload_sessions_id 1 param → 204default
GET
/files/upload_sessions/{upload_session_id}/parts
Box List parts
get_files_upload_sessions_id_parts 3 params → 200default
POST
/files/upload_sessions/{upload_session_id}/commit
Box Commit upload session
post_files_upload_sessions_id_commit 4 params body → 201202409412default

Schemas 20

The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are UploadSession (7 properties), ClientError (7 properties), Metadata--Base (4 properties), File--Base (3 properties). Each schema is shown below with its type and property counts.

Files
object
A list of files
2 properties
ClientError
object
A generic error
7 properties
FileVersion--Mini
object
A mini representation of a file version, used when nested within another resource.
FileVersion--Base
object
The bare basic representation of a file version, the minimal amount of fields returned when using the fields query parameter.
2 properties 2 required
User--Base
object
A mini representation of a user, used when nested within another resource.
2 properties 2 required
User--Mini
object
A mini representation of a user, as can be returned when nested within other resources.
File
object
A standard representation of a file, as returned from any file API endpoints by default
File--Mini
objectnull
A mini representation of a file, used when nested under another resource.
Metadata--Base
object
The base representation of a metadata instance.
4 properties
UploadPart--Mini
object
The basic representation of an upload session chunk.
3 properties
FileOrFolderScope
object
A relation between a resource (file or folder) and the scopes for which the resource can be accessed
2 properties
UploadedPart
object
A chunk of a file uploaded as part of an upload session, as returned by some endpoints.
1 property
File--Full
object
A full representation of a file, as can be returned from any file API endpoints by default
UploadParts
object
A list of uploaded chunks for an upload session.
Folder--Mini
object
A mini representation of a file version, used when nested under another resource.
UploadPart
object
The representation of an upload session chunk.
Metadata
object
An instance of a metadata template, which has been applied to a file or folder.
Folder--Base
object
The bare basic representation of a folder, the minimal amount of fields returned when using the fields query parameter.
3 properties 2 required
UploadSession
object
An upload session for chunk uploading a file.
7 properties
File--Base
objectnull
The bare basic representation of a file, the minimal amount of fields returned when using the fields query parameter.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

box-uploads-chunked-api-openapi.yml Raw ↑

Other APIs Box publishes across the network.

Box Authorization API
Box Authorize API
Box Classifications API
Box Classifications on Files API
Box Classifications on Folders API
Box Collaboration Whitelist Entries API
Box Collaboration Whitelist Exempt Targets API
Box Collaborations API
Box Collaborations (List) API
Box Collections API
Box Comments API
Box Device Pinners API
Where this information came from

This is an independent, third-party profile of Box Uploads (Chunked) API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.