Page History
Table of Contents |
---|
Limitations
Box API request limitation
In certain cases, Box needs to enforce rate-limiting in order to prevent abuse by third-party services and/or users. In the event that an excessive level of usage is reached, a standard 429 Too Many Requests error will be returned, with an indication of when to retry the request. In the event that back-to-back 429s are received. RETRY HEADER HTTP/1.1 429 Too Many Requests Retry-After: {retry time in seconds}
Please see more information at, https://developers.box.com/docs/#rate-limiting
Box API Errors
The Box API communicates errors through standard HTTP status codes
# 200 success # 201 created # 202 accepted # 204 no_content # 302 redirect # 304 not_modified # 400 bad_request # 401 unauthorized # 403 forbidden # 404 not_found # 405 method_not_allowed # 409 conflict # 412 precondition_failed # 429 too_many_requests # 500 internal_server_error # 503 unavailable
Incremental limitations
- When there is a change on a Box Note will not reflect in the incremental crawl.
Save your content source before creating or editing another one
Failing to save a content source before creating or editing another content source can result in an error.
ERROR [aspire]: Exception received attempting to get execute component command com.searchtechnologies.aspire.services.AspireException: Unable to find content source
Save the initial content source before creating or working on another.
Advanced Topics
Create Box Application
Describes the steps necessary to create a Box Content application and get Client Id, Client Secret and API Key.
Generate Access and Refresh tokens
Describes the steps necessary to generate the access and refresh tokens.