canonical: https://jentic.com/apis/raindrop.io/raindrop

# Raindrop.io API

**UNOFFICIAL** OpenAPI specification of Raindrop API. This OpenAPI spec has been made by hand with reference to official documentation because it is not provided by Raindrop.io. Because official documentation not maintained well, there are very (highly) likely to have mismatch in schemas. As we can't inspect and address all issues, schema being updated as we find issues. Any contributions are welc. The API exposes 48 endpoints secured with bearer, oauth2 authentication.

## For AI agents

Programmatically get root collections, reorder all collections. Covers 48 operations with bearer, oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for storage and databases only.

## Capabilities

- Get root collections
- Reorder all collections
- Remove multiple collections
- Merge collections
- Create collection

## Use cases

### Storage and Databases Operations

Use the Raindrop API (Unofficial) to perform storage operations programmatically. The API provides 48 endpoints covering core functionality including get root collections, reorder all collections, remove multiple collections.

Example prompt: Call GET /collections to get root collections

### Automated Collections Management

Automate collections operations by combining multiple Raindrop API (Unofficial) endpoints. Agents can reorder all collections and then remove multiple collections in a single workflow.

Example prompt: Call PUT /collections to reorder all collections, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Raindrop API (Unofficial) endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer, oauth2 tokens manually.

Example prompt: Search Jentic for 'get root collections', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/collections` | Get root collections |
| PUT | `/collections` | Reorder all collections |
| DELETE | `/collections` | Remove multiple collections |
| GET | `/collections/childrens` | Get child collections |
| PUT | `/collections/merge` | Merge collections |
| PUT | `/collections/clean` | Remove all empty collections |
| POST | `/collection` | Create collection |
| GET | `/collection/{id}` | Get collection |

## Key resources

- **Collections** — Manage bookmark collections
- **Sharing** — Collection sharing and collaboration
- **Raindrops** — Manage individual bookmarks (raindrops)
- **Multiple Raindrops** — Bulk operations on bookmarks
- **Tags** — Manage tags

## Why Jentic

- **Setup:** Wiring Raindrop.io by hand means learning its bearer and OAuth2 flows and hand-coding requests across its collections, raindrops, and tags endpoints. Through Jentic you install once, import the Raindrop.io API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Raindrop puts the collection id in the URL path (`/collection/{id}`), so a rule can pin your agent to one collection: it can read and update items in that collection and nothing else. You choose the operations it may call, so destructive ones like deleting a collection or emptying the trash are not included unless you add them.
- **Credential handling:** Your Raindrop token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list my bookmark collections' or 'save a new raindrop', and Jentic returns the matching Raindrop operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Dropbox** — Alternative storage API
- **Box** — Alternative storage API
- **Googleapis** — Complementary storage API

## FAQ

### What authentication does the Raindrop API (Unofficial) use?

The Raindrop API (Unofficial) uses bearer, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get root collections with the Raindrop API (Unofficial)?

Yes. Use the GET /collections endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Raindrop API (Unofficial)?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get root collections through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get root collections'. Jentic returns the matching Raindrop API (Unofficial) operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Raindrop API (Unofficial) have?

The Raindrop API (Unofficial) exposes 48 endpoints covering collections, sharing, raindrops operations.

### Can I limit what my agent is allowed to do with the Raindrop API?

Yes. Because you run Jentic One yourself, your own rules decide which Raindrop operations and which stored token the agent may use. Since Raindrop puts the collection id in the URL path, such as `/collection/{id}`, you can pin the agent to a single collection so it only reads and updates items there and nothing else. You also choose the operations it may call, so destructive ones like deleting a collection or emptying the trash stay out of reach unless you explicitly add them.