Verita Content Service API (1.1.0)

Internal endpoint called by user-service during account deletion. Soft-deletes authored posts and comments, removes user-owned bookmarks and votes, and refreshes affected counters. The operation is idempotent.

General-purpose endpoint for fetching a batch of posts with optional topic filtering. Intended for use cases such as topic-based browsing, admin tooling, or any client that needs raw paginated post data.

Not the homepage feed — the personalised and trending feeds are served by the Recommendation Service (GET /api/v1/feed/personal and GET /api/v1/feed/trending). Those endpoints apply algorithmic ranking and return enriched post payloads.

The topic parameter performs an exact-match filter and returns results in reverse-chronological order. For popularity-ranked topic browsing, use GET /api/v1/feed/trending?topic= in the Recommendation Service instead.

Returns PostCard objects (no article body) for the given post IDs, preserving the order of the ids parameter. Called by the frontend after receiving a postIds list from the Recommendation Service to populate feed cards.

Full-text keyword search across post titles and content. Returns results ranked by relevance to the query string, not by time or popularity.

This endpoint is driven by user intent (the user typed something to find) and is distinct from feed discovery. Future iterations may back this with a dedicated search engine (e.g. Elasticsearch) without changing the contract.

Authentication is optional. When a valid Bearer token is present, isLikedByMe and isBookmarkedByMe are populated per the authenticated user; otherwise they default to false.

Updates only the fields provided in the request body; omitted fields are left unchanged. Use this for single-field updates such as unpublishing a post ({"status": "DRAFT"}) without re-sending the full post payload. For full replacement (e.g. the post editor), use PUT.

Only the post author may patch a post.

Returns the AI summary state for a single post. Uses the same visibility rules as post detail: published posts are public, drafts are visible only to their author, and non-visible posts return 404.

Union of the caller's personal digests (digest_type = PERSONAL, target_user_id = me) and the public digests assigned to the caller on days they had no subscriptions, newest first, paginated. Auth-required (fails closed).

Returns the newest PUBLIC digest, readable without authentication so the logged-out /digest surface has something to show (ADR-0018/0019). Responds 404 when none exists.

Optional authentication (ADR-0006/0016). A PERSONAL digest whose target_user_id is not the caller responds 404; a PUBLIC digest is open (including logged-out).

Deprecated service-only endpoint (gated by X-Internal-Service-Token, ADR-0007). Existing callers may still persist an already-generated digest, but content-service ignores the request title and applies its deterministic personal/public title rule. Scheduled and admin generation persist in-process and do not call this endpoint.

Service-only manual trigger for the same generation orchestration used by the scheduled daily digest job. Branches on whether the user has topic subscriptions: subscribers get a freshly generated PERSONAL digest; zero-subscription users are assigned the day's PUBLIC digest (ADR-0018/0019). By default, skips when the user already has a digest for the current Platform Day; force=true regenerates.

Send LIKE or DISLIKE to cast/change a reaction. Send NONE to remove any existing reaction.

Send LIKE to cast a like. Send NONE to remove an existing like.

Returns bookmarked posts for the given user. Visibility is controlled by the user's showBookmarks preference (from UserPreferences). The current user can always access their own bookmarks; other users' bookmarks are only visible when showBookmarks is true.

Returns liked posts for the given user. Visibility is controlled by the user's showLikes preference (from UserPreferences). The current user can always access their own likes; other users' likes are only visible when showLikes is true.

Returns all topics with full stats, grouped by category. Used by the Manage Topics page.

Returns minimal { id, name } objects for the given topic IDs — for callers that only need to resolve names (e.g. recommendation-service populating subscribed-topic names). Unknown IDs are silently omitted; the caller tolerates gaps.

This is a dedicated sibling of GET /api/v1/topics (which returns the full category-grouped catalog with stats), mirroring the GET /api/v1/posts/cards?ids= pattern: one operation, one response shape.

Service-only endpoint (gated by X-Internal-Service-Token, ADR-0007). Increments or decrements follower_count for each named topic. +1 = follow, -1 = unfollow.

Accepts a single image as multipart/form-data, validates type and size, stores it in object storage, and returns its public URL for use as a cover image or inline post image.

Returns the live (provider, model) pair GenAI is currently using — the in-memory override when an admin has set one, otherwise GenAI's environment default — plus every supported provider and whether its API key is configured.