Parse.com - saveAll on PFObject does it account for 1 API call?

Question

I have an IOS app and I want to make sure I minimally use the API request to parse.com due to the 30/sec request limitation on the free tier. Could some one please clarify i

Answer 1

From Parse:

saveAll attempts to do as few API calls as possible. Usually a call to saveAll results in only one API request. However, if any of the objects in the set has a relation to another unsaved object, that object will have to be saved first, resulting in more API requests.

https://www.parse.com/questions/saveall-how-many-api-requests

Answer 2

From what I have seen using Parse, saving many PFObjects accounts as 1 API call.

However, the thing I don't know about is that if there are any limits on the number of objects to be saved at once and still be considered as 1 API call.

Also I recommend that you test it yourself. Try saving multiple objects at once and see how your API calls number change in the dashboard.

Please note that batch operations will fail as a whole if one object fails (e.g. object does not exist).

Answer 3

With Parse moving to the new pricing model they also changed the way batch operation requests (e.g. saveAll) are counted:

Where previously batch requests counted as a single request, it now takes n requests (where n is the number of objects passed to saveAll).

There was a extension of the old way of counting for apps that were already depending on it, but as of February 2015 batch operations like saveAll use 1 request per object

Answer 4

For me saveAll is also using as many API calls as objects are saved. I think they changed this with the new pricing and this is a non-sense, since one user saving multiple data at once generates an insane peak on the Api consumption.

Answer 5

I'm using PFObject saveAllInBackground:block and regardless if there's a relation to another unsaved object, my api count in Analytics always increases by the number of objects in the array.