Skip to main content
* * Recoloring the span has been unreliable (Tailwind utility CSS * specificity quirks, deploy lag), so we just remove the overlay * entirely with display:none. The anchor's own background then * becomes the visible color, which is exactly what we want. The * mobile variant has no overlay span, so display:none on the * span is a no-op there and the anchor bg wins by default. */ #navbar a[href="https://app.nango.dev/signup"] { background-color: #29abe3 !important; background-image: none !important; border: 1px solid #29abe3 !important; color: #ffffff !important; } #navbar a[href="https://app.nango.dev/signup"] > span:first-child, #navbar a[href="https://app.nango.dev/signup"] span.absolute, #navbar a[href="https://app.nango.dev/signup"] span[class*="bg-primary"] { display: none !important; } #navbar a[href="https://app.nango.dev/signup"]:hover { background-color: #217ea6 !important; border-color: #217ea6 !important; color: #ffffff !important; } /* ══ HIDE BOTTOM CHAT ASSISTANT INPUT ════════════════════════════ */ /* * Mintlify pins an "Ask a question..." chat-assistant input at the * bottom of every doc page. The navbar already has a separate Ask AI * button, so this bottom input is redundant. Mintlify doesn't expose * a docs.json toggle for it. * * Two layers needed: * 1. The floating input bar itself (.chat-assistant-floating-input). * 2. Its rounded-2xl wrapper div — which also appears identically * inside the Ask AI sidebar panel, so the rule must be scoped to * #content-area to avoid hiding the panel's own input container. * * Do NOT use [class*="chat-assistant"] (hides the panel) or * #chat-assistant-textarea (that ID is duplicated on the panel * textarea and would hide it too). */ .chat-assistant-floating-input, #content-area div.rounded-2xl.pointer-events-auto[class*="bg-background-light"] { display: none !important; }

🚀 Quickstart

Connect to Box with Nango and see data flow in 2 minutes.
1

Create the integration

In Nango (free signup), go to Integrations -> Configure New Integration -> Box. Nango doesn’t provide a test OAuth app for Box yet. You’ll need to set up your own by following these instructions. After that, make sure to add the OAuth client ID, secret, and scopes in the integration settings in Nango.
2

Authorize Box

Go to Connections -> Add Test Connection -> Authorize, then log in to Box. Later, you’ll let your users do the same directly from your app.
3

Call the Box API

Let’s make your first request to the Box API (fetch the profile of the currently signed-in user). Replace the placeholders below with your secret key, integration ID, and connection ID:
curl "https://api.nango.dev/proxy/2.0/users/me" \
  -H "Authorization: Bearer <NANGO-SECRET-KEY>" \
  -H "Provider-Config-Key: <INTEGRATION-ID>" \
  -H "Connection-Id: <CONNECTION-ID>"
Or fetch credentials with the Node SDK or API.✅ You’re connected! Check the Logs tab in Nango to inspect requests.
4

Implement Nango in your app

Follow our Auth implementation guide to integrate Nango in your app.To obtain your own production credentials, follow the setup guide linked below.

📚 Box Integration Guides

Nango maintained guides for common use cases. Official docs: Box API docs

🧩 Pre-built syncs & actions for Box

Enable them in your dashboard. Extend and customize to fit your needs.

Files

Function nameDescriptionTypeSource code
filesSync the metadata of specified files or folder paths from Box. A file or folder ID can be provided.Sync🔗 Github

Users

Function nameDescriptionTypeSource code
usersFetches a list of users from Box. Requires an enterprise account.Sync🔗 Github

Others

Function nameDescriptionTypeSource code
collaborationsSync collaborations from BoxSync🔗 Github
foldersSync folders from BoxSync🔗 Github