box-api

I am trying to determine which version of the Box api I should use. My decision hinges on the timeline of EOL of the v1 api. I don't want to finish up my app, and just before (or shortly after) the release of the app, the v1 api quits working. I would gladly use the v2 api, but I am writing a C# app. Since there is a C# SDK for the v1 api, it would be more convenient (in the short-term) to use v1 of the api; but like I said, I'm concerned about the EOL of the v1 api. We began the process of deprecating the v1 API in December of 2013. The v2 API was made generally available (GA) a year prior to

The documentation ( http://developers.box.com/oauth/ ) suggests using POSTMAN or curl. in this example, the clientID is 123, secret code is 456 and so on. I am using Postman. In a prior step, I have obtained an access code via: https://www.box.com/api/oauth2/authorize?response_type=code&client_id=123 let's say the response is xyz In the next step, I use POSTMAN to issue a POST command (urlencoded) https://www.box.com/api/oauth2/token?grant_type=authorization_code&client_id=123&client_secret=456&code=xyz I do all of this within 30 seconds of obtaining the code in step 1. The error is {"error":

We have SAML-based single sign-on (SSO) enabled between our company's Intranet Portal and Box so that the users do not use username and passwords to login to Box.com. They just click on a button on Intranet Portal which posts a SAML assertion to Box.com to authenticate. We would like to provide the ability to our users to search their Box documents directly from the Intranet Portal and the Box.com API looks like a perfect fit. However, it requires OAuth access token. The question is: Is there any way to obtain the OAuth token from SAML assertion? The Box Embed allows embedding of folders view

Each refresh token is valid for 14 days. Why do the refresh tokens expire? Peter 14 days was based on what is considered best practice in implementing OAuth2. See Why do access tokens expire? for a pretty comprehensive answer about why OAuth2 refresh tokens expire. We are interested in hearing what number bigger than 14 would work for your application. We picked 14 days based on initial feedback, surveys from application developers, as well as looking at application logins by users. A high majority of users login with apps more often than every 14 days. Can you explain your use case? What