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 File Requests API

File Requests provide a fast andsecure way to request files and associated metadatafrom anyone.Users can create new file requestsbased on an existing file request,update file request settings, activate, deactivate, and deletefile requests programmatically.

Box File Requests API is one of 81 APIs that Box publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include File Requests. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 2 paths, and defines 10 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

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

4 operations 2 paths 10 schemas 1 DELETE1 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://account.box.com/api/oauth2
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Box File Requests API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (OAuth2Security) using the authorizationCode flow, exposing 9 scopes.

Paths & Operations 4

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

File Requests 4

File Requests provide a fast and secure way to request files and associated metadata from anyone. Users can create new file requests based on an existing file request, update file…

GET
/file_requests/{file_request_id}
Box Get file request
get_file_requests_id 1 param → 200401404405default
PUT
/file_requests/{file_request_id}
Box Update file request
put_file_requests_id 2 params body → 200401403404405412default
DELETE
/file_requests/{file_request_id}
Box Delete file request
delete_file_requests_id 1 param → 204401404405default
POST
/file_requests/{file_request_id}/copy
Box Copy file request
post_file_requests_id_copy 1 param body → 200401403404405default

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are FileRequest (15 properties), FileRequest_2 (15 properties), ClientError_2 (7 properties), ClientError (7 properties). Each schema is shown below with its type and property counts.

ClientError
object
A generic error
7 properties
User--Mini
object
A mini representation of a user, as can be returned when nested within other resources.
Folder--Mini
object
A mini representation of a file version, used when nested under another resource.
FileRequestUpdateRequest
object
The request body to update a file request.
6 properties
FileRequest
object
A standard representation of a file request, as returned from any file request API endpoints by default.
15 properties 5 required
FileRequestCopyRequest
object
The request body to copy a file request.
1 required
User--Base
object
A mini representation of a user, used when nested within another resource.
2 properties 2 required
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
ClientError_2
object
A generic error
7 properties
FileRequest_2
object
A standard representation of a file request, as returned from any file request API endpoints by default.
15 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

box-file-requests-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 File Requests 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.