Quick start

1. Generate a token

Go to Savee → Settings → Developer and click Generate token. Copy the raw sv_live_… value immediately — Savee stores only a hash, so the raw value is shown exactly once.

Treat it like a password: don't commit it, don't paste it into client-side code, rotate it if it leaks.

2. Make a request

curl https://api.savee.com/v1/me \
  -H "Authorization: Bearer sv_live_…"

Response:

{
	"id": "63e1...d8f2",
	"username": "you",
	"name": "Your Name",
	"url": "https://savee.com/you/",
	"avatar_url": "https://dm.savee.com/user-avatar/original/…jpg",
	"plan": { "active": true, "tiers": ["pro"] }
}

3. List your saves

curl 'https://api.savee.com/v1/saves?limit=5' \
  -H "Authorization: Bearer sv_live_…"

Each save includes a stable id, the canonical url on savee.com, the source_url the user originally saved from, created_at, total_saves (how many users on the platform have saved this asset), and a media block with the image / video URLs.

Pagination

The save-listing endpoints (/v1/saves, /v1/feed, /v1/boards/{id}/saves) take limit (default 30, max 100) and cursor. The response includes next_cursor and has_more; pass next_cursor back as the next page's cursor until has_more is false.

curl 'https://api.savee.com/v1/saves?limit=50&cursor=1715276400000' \
  -H "Authorization: Bearer sv_live_…"

Cursors are opaque — don't try to parse them. Always pass next_cursor through verbatim; the format may change in a future v1.x release without notice.

/v1/boards is the exception: it returns every board the caller can see in a single response (typically dozens, rarely a few hundred), so there's nothing to paginate.