Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.box.com/llms.txt

Use this file to discover all available pages before exploring further.

An enterprise that normally restricts creating collaborations can add domains, such as example.com, to a list for which collaborations may be created within the enterprise. 
curl -i -X POST "https://api.box.com/2.0/collaboration_whitelist_entries" \
     -H "authorization: Bearer <ACCESS_TOKEN>" \
     -H "content-type: application/json" \
     -d '{
       "domain": "example.com",
       "direction": "inboud"
     }'
The will require the domain to allow the collaborations between, and a direction, which may be set to:
  • inbound: Whether external users may be collaborated in on content in your enterprise.
  • outbound: Whether your enterprise managed users may be collaborated in on content owned within an external enterprise.
  • both: Both of the above.
Supply both parameter to set up the new allowed domain. 
curl -i -X POST "https://api.box.com/2.0/collaboration_whitelist_entries" \
     -H "authorization: Bearer <ACCESS_TOKEN>" \
     -H "content-type: application/json" \
     -d '{
       "domain": "example.com",
       "direction": "inboud"
     }'