Offset limit on v2/user/likes

[Martin Spier]

I'm trying to implement a client that fetches all liked posts from a specific user. Logic I'm using a loop that requests x posts from  /v2/user/likes, increases the offset by x and makes another request, until there are no more posts (empty response). POST body is "offset=y&limit=x", y being increased by x every iteration and x being a fixed number of posts to fetch each request, 20 for example.

This worked fine for users with less than 1000 likes. For other users, when the loop reached an offset higher than 1000, API starts returning same response as offset=0. Is this an API limit?

Regards,

[felix bonkoski]

Yes 1000 "likes" seems to be an API limit. Larger offsets just start loading likes from the beginning again.

Why can't we fetch more than 1000? I don't know. Maybe Mr. Bunting has something to add.  :)

felix

[Stefan Strigler]

Any updates on this? I'm about to write a tool that allows to backup all of your likes but with this limit it's not very useful at the moment. Any chances to get this limit raised or maybe even removed entirely? What's the reason behind it anyway?

-Steve

[John Bunting]

Hey,

Yep 1000 likes is the upper limit of what we expose on the API. So it's the last 1000 likes the user has liked.

-- 

John Bunting

Simplicity is a prerequisite for reliability

   --Edsger W. Dijkstra

[felix bonkoski]

The real question I think we are wondering is, will this be changed?  If so, when?  If not, why not?

Felix

[Steven Pears]

Where there are arbitrary limits in place on API calls like this, could we add a request for an offset_limit property in the meta object that is returned with the result? That way we could avoid giving duplicate data back to our users - and stop the need for us asking for this kind of detail.

 

Thanks

 

Steven

 

[felix bonkoski]

Really, that information *should* all be in the API documentation.  (*wink* John)

Or ideally, there should be a JSON (or XML etc) interface to get all the "documentation" information about the API.  Google provides such things for their public API's -- a call to get the "description" the API.

Felix

[John Bunting]

You guys are right. This should be in the documentation. I've been working on getting some auto generated documentation handy for use internally as well as externally. 

The idea of the description route is quite interesting. I'll have to mull that one over, as well meta fields for things like rate limit and the such.

-- 

John Bunting

Simplicity is a prerequisite for reliability

   --Edsger W. Dijkstra

[felix bonkoski]

The auto-generated documentation would probably feed quite nicely into an "API Description" interface as well.

Felix

[John Bunting]

I do want to take the time to thank you all for your suggestions and information.  I read every email that comes across the list and even if sometimes I don't respond right away (or at all because I get a lot of email >.<), I appreciate the input. 

Any other community improving ideas are welcome and you guys can always drop me a line on this email or the list. 

-- 

John Bunting

Simplicity is a prerequisite for reliability

   --Edsger W. Dijkstra

[mrjason]

+1 to John. 

[felix bonkoski]

Yes. +1 for John. You deserve a raise :P  I'd drop a note on http://www.davidslog.com/ask -- but somehow I doubt Mr. Karp reads those hahaha.

But hey, since you're in such a good mood this afternoon...  maybe I'll just put a tiny wish list here for you...

1. Ability to get the Post Author information on posts from Group Blogs  (Now supported in Tumblr Themes, although it wasn't for a long time. Not sure when they added it, but it must have been fairly recently. In the Theme Code, you've got {PostAuthorName}  {PostAuthorTitle}  {PostAuthorURL} etc.  That sure would be nice to get with the Blog post info through the API)

   I've got a few clients who could use this feature.  Right now I just have to use hacky workarounds.

2. Pwetty pweez let us fetch more than 50 blog posts at once again?  I know it was a *bug* when i used to be able to fetch 250 posts at a time.... but it was just soooo much faster that way.

I know you're not Santa Claus, though, so.... Anyway, thanks for all your hard work. Everyone here in this group appreciates you very much!

Felix Bonkoski

--

Felix Bonkoski