Remove or document REST API limits/throttling
At the moment, the REST API is throttled and limited in a nearly completely undocumented manner.
A simple attempt to upload a few GBs of data was met with a 420 request throttled response after ~5GB.
It'd be great if you offered some way for us to get these limits lifted and at the very least you should document them more thoroughly.
Our new API supports uploading large files up to 10 GB and has relaxed throttles compared to our previous API. Please give it a try! http://aka.ms/onedriveapi
Apart from the file size limitation are there any other limitation that developer has to know while using OneDrive Rest API? For example: is there any limit on number of call to REST API?
Thank you. But could you consider lifting the 10 GB file size limit?
As a subscriber I feel you are hindering my experience. I signed up for OneDrive after Bitcasa decided to screw over its users that were part of the original unlimited plan. I liked the fact that I could get Office 365 and 1TB of storage for a decent price each month. What is horrible is that I cannot upload data without being throttled. I have been trying for 3 days now to upload 17GB of data using a 50Mb fiberline and I still have over 14GB of data to go due to the throttling....
Tell me how this is protecting my service experience that I PAY for? I am strongly considering switching to something else...
@Mat, it may be unrealistic but this is what I expect coming from providers like AWS, Google Storage and even Azure.
And you might think that level of service for the price I'm paying might be unrealistic but given the service they promise I think it's entirely reasonable. What's the point of unlimited storage if you can only upload 1GB a week?
@casey Penk - Thank you for the documentation. I reached out to the developers of Syncovery and they implemented the new protocol etc. as described in your document. Things were goind well when suddenly after copying 14 GB i get this error - (REQUEST THROTTLED AT 000000000170328E.CHECKPOINTS: TGGETORPUTEX:REQUEST THROTTLED)
@Lucas: I do not think Microsoft's priority should be to accommodate the case you are describing (100GB transfer/hour). The level of service you are expecting for the price you are paying is unrealistic. Your complaint is actually counterproductive as it shows that these restrictions are actually necessary. I hope Microsoft finds a balance so that 90% of all users can use the service without constant interruptions: 502 service not available, timeouts etc. If it's necessary put limits into place I'm all for it.
Some approaches to this that would work for me are:
- Prompt the user for confirmation before throttling. Give the user a chance in case they know they're doing something they normally wouldn't (e.g. moving from another cloud to OneDrive using Otixo or Mover.io)
- Prompt the developer before throttling. Let the developer assume all liability if their use of the API causes issues for the user
- Allow the developer/user to request higher limits from Microsoft for their application using an ACCESSIBLE form (they should be able to go to the developer center and see a nice big message saying "Your application has been throttled, please click here to request higher limits")
I appreciate that you're working on this, I'm just afraid of it not being enough. There should definitely be a path for applications to take that allows them to reach ANY rate of API calls, as long as the number can be justified to Microsoft.
Really I think the throttling should be in the hands of the users and developers, since they're the ones you're trying to protect and unless you set the limits extremely high (for example I could legitimately and easily make roughly a million requests and send 100GB of data in an hour as it is right now, uploading backups from a high performance server), you're always going to run into something you didn't consider.
Ugh - the limitations are weird. I am not sure how to use the 1 TB space since it keeps giving 420 errors.
API throttling is just ridiculous. This has to be either fixed or publicly documented, having an unlimited/10Tb OneDrive account is just pointless if you can't get your stuff there in time (say before 2050?).
I have a 100mb/s upload connection but OneDrive client won't get anything sent over 5mbps so I must rely on 3rd parties software in order to get something uploaded. Back when I was a Google Drive and DropBox user I didn't need a single thing other than their regular clients.