Save URLs with a read-later API.

Save a URL from a script

The Sleevy API accepts a web address and adds it to the reading queue for your account. That makes it possible to save a URL from a shell script, a shortcut, an internal tool, or any service that can send an HTTP request.

Authenticate with a personal API key in the Authorization header. The API documentation includes a curl request you can run as a first test before connecting a larger automation.

Use one queue instead of another bookmark store

API captures appear beside links saved through the iPhone Share Sheet, Chrome extension, Raycast extension, and web companion. A script can therefore feed the same personal queue you already use manually.

This is useful when the source of a link is predictable but the time to read it is not: a recurring report, a URL copied from another tool, or a page selected by a small personal workflow.

Keep the automation small

Start with one capture request and confirm that it reaches your queue. Then add the trigger that suits your workflow. Keeping the saving step separate from the trigger makes failures easier to understand.

The public API supports the endpoints documented on the Sleevy site. Do not build around an assumed webhook or integration that is not listed there.

Manage saved links through the API

The REST API also exposes documented operations for listing and updating your saved links. Use the endpoint reference for current request fields, responses, and authentication requirements.