Per-community activity preferences
Each community the caller is a member of, with the effective switch for each activity type (the community's own, else the global one).
Sends a real request with your token. Prefer a read-only token; it is kept in this browser's storage.
Each community the caller is a member of, with the effective switch for each activity type (the community's own, else the global one).
AuthorizationBearer <token>A personal access token (rsk_…) or a Supabase access token.
The communities
application/json- response
items*array<unknown>curl -X GET 'https://www.ressource.social/api/v1/notifications/preferences/communities'{ "items": [ null ]}Resolve a URL's title, description, preview and category POST
What the source form shows before saving. Counted against the caller's metadata windows (`metadata_per_hour`, `metadata_per_day`; 429 with `details` when spent). Every outbound request is SSRF-checked, including redirects and an `image` hint. Needs the `write` scope: the preview image is stored as the caller's media. With `bookmark_id` (one of the caller's imported rows, `pending`, same URL) the import window is spent instead and the row is filled in and marked `completed` — or put back to `pending` on a 429, or `failed` when the fetch fails.
The caller's notification preferences GET
One row per (source_type, notification_type), defaults included — the global switches of the settings page. A community's own settings are read from `/notifications/preferences/communities`.