How to connect to Box

There is nothing to copy and paste for this connection: no API key, no client id, no account number to look up beforehand. You sign in with your own Box account, review what the application is asking for, and approve it.

Prerequisites

• A Box account you can sign in to. A free individual account is enough, and no paid plan is required.

Steps

1. Start the Box connection in the application you are connecting from. This opens Apideck Vault.
2. Click Authorize. Vault sends you to Box.
3. Sign in with your usual Box email and password, and complete two-step verification if your account uses it. You type your password on Box's own sign-in page, so Apideck never sees it.
4. Read the screen Box then shows you. It names the application that is asking for access and what it is asking to do with your files and folders. Approve it if you are happy with that.
5. You land back in Vault and the connection shows as Connected. You are done: there are no fields to fill in afterwards.

What you are granting

• Access is account-wide. The application reaches the files and folders you can already see in Box. Box does not offer a way to confine this to a single folder, so there is no folder to pick during the connection.
• Either read-only, or read and write. Which of the two it is was decided by whoever registered the application, and Box names it on the screen you approve, so that screen is worth reading before you click through.
• Your own Box permissions still apply on top. The connection can never reach anything you could not reach yourself in Box.

If your company blocks unpublished applications

This applies to some companies and not others, and many do not have it switched on.

A company can configure its Box so that applications work only once someone has enabled them. If yours is set up that way, your connection will not complete until a Box administrator at your company enables this application once. This is your own company's setting rather than anything Box has to approve, and enabling it is a single step on the administrator's side.

Ask your Box administrator to enable it. They will want the application's Client ID, which the team that operates the integration can give you. That team will find the administrator's side of this in the Box configuration guide.

Troubleshooting

The connection does not complete, and Box says the application is not enabled or not allowed

This is the company setting described above. Ask your Box administrator to enable the application, with the Client ID from the team that operates the integration, then start the connection again.

A connection that was working has stopped

Two common explanations, both fixed by authorising again from Vault:

• Apideck keeps the connection's access renewed in the background, so it does not expire just because you have not used it for a while. You only need to connect again if the authorisation is removed in Box.
• A Box user can remove a connected application from their own Box account settings. If that happened to the account that authorised this connection, it explains the same symptom.

Open the connection in Vault, click Authorize, and sign in again.

Some files or folders are missing

The connection only ever reaches what your own Box permissions allow, so content a colleague has not shared with you will not appear. Ask for access in Box to the folders you are missing, and they become available to the connection too.

Still stuck

For your Box sign-in, your Box account or access to a folder, contact your Box administrator or Box support. For anything on the Apideck side of the connection, contact Apideck Support.