Overview
Build and integrate tools and applications to help members manage their bookmarks on Raindrop.io
Last updated
Build and integrate tools and applications to help members manage their bookmarks on Raindrop.io
Last updated
This is the official documentation for Raindrop.io API. A reference to the functionality our public API provides with detailed description of each API endpoint, parameters, and examples.
Please note that you must register your application and authenticate with OAuth when making requests. Before doing so, be sure to read our Terms & Guidelines to learn how the API may be used.
API endpoints accept arguments either as url-encoded values for non-POST requests or as json-encoded objects encoded in POST request body with Content-Type: application/json
header.
Where possible, the API strives to use appropriate HTTP verbs for each action.
This API relies on standard HTTP response codes to indicate operation result. The table below is a simple reference about the most used status codes:
All 200 OK
responses have the Content-type: application/json
and contain a JSON-encoded representation of one or more objects.
Payload of POST requests has to be JSON-encoded and accompanied with Content-Type: application/json
header.
All timestamps are returned in ISO 8601 format:
For requests using OAuth, you can make up to 120 requests per minute per authenticated user.
The headers tell you everything you need to know about your current rate limit status:
Once you go over the rate limit you will receive an error response:
The API supports Cross Origin Resource Sharing (CORS) for AJAX requests. You can read the CORS W3C recommendation, or this intro from the HTML 5 Security Guide.
Here’s a sample request sent from a browser hitting http://example.com
:
Verb
Description
GET
Used for retrieving resources.
POST
Used for creating resources.
PUT
Used for updating resources, or performing custom actions.
DELETE
Used for deleting resources.
Status code
Description
200
The request was processed successfully.
204
The request was processed successfully without any data to return.
4xx
The request was processed with an error and should not be retried unmodified as they won’t be processed any different by an API.
5xx
The request failed due to a server error, it’s safe to retry later.
Header name
Description
X-RateLimit-Limit
The maximum number of requests that the consumer is permitted to make per minute.
RateLimit-Remaining
The number of requests remaining in the current rate limit window.
X-RateLimit-Reset
The time at which the current rate limit window resets in UTC epoch seconds.