Ohhh, that looks good. I do have some wishlist points:
some specific params for GET /api/v1/journals/{username}/entries: - number of entries to fetch - offset (so it's possible to get entries in batches) - from & to timestamps (to get entries from a specific timeframe) - fetch posts by tag
/api/v1/comments/{post_id} - GET comments on a post, with these params: - number of comments to fetch - offset - from & to timestamps
Generally, I'm hoping for more "frontend" type of endpoints that would make the public data available for automatization/processing - i.e. backups, import/export. The old LJ API is geared toward content-generating apps, I'd love something more akin to Tumblr's API.
no subject
some specific params for GET /api/v1/journals/{username}/entries:
- number of entries to fetch
- offset (so it's possible to get entries in batches)
- from & to timestamps (to get entries from a specific timeframe)
- fetch posts by tag
/api/v1/comments/{post_id} - GET comments on a post, with these params:
- number of comments to fetch
- offset
- from & to timestamps
Generally, I'm hoping for more "frontend" type of endpoints that would make the public data available for automatization/processing - i.e. backups, import/export. The old LJ API is geared toward content-generating apps, I'd love something more akin to Tumblr's API.