Can resellers embed the same topics shown on the public Discover page?

Yes. GET /api/v1/discover returns the same items for the same source snapshot, supports title and source-tag filters, and returns public fields only. Third-party titles and URLs are preserved. Refresh times can differ from the public page.

API DOCS

OpenAPI Status Support Get API key

Browse API docs

Endpoints

Discover feed API

Was this page helpful?

Pull the public Discover page feed into reseller links, embeds, and content workflows.

By Wilson Sik Founder, Reviral Last updated September 25, 2026

Pull the public Discover feed

curl "https://reviral.ai/api/v1/discover?page=1&limit=24" \
  -H "Authorization: Bearer $REVIRAL_API_KEY"

Who lands here and from where: Reseller developers arrive from the API overview, search results, generated documentation, or the machine-readable endpoint index when they need content to link or embed.
What they must see first: The authenticated curl example above works as written after REVIRAL_API_KEY is set.
How it ranks and gets cited: The keyword-focused Discover feed API title, OpenAPI response schema, FAQ structured data, sitemap-derived docs URL, and llms.txt endpoint row make the contract indexable and citable.
What it upsells: Turn a selected topic into media with generate-media, then review plans and credits on the pricing page.

Frequently asked questions

Can resellers embed the same topics shown on the public Discover page?: Yes. GET /api/v1/discover returns the same items for the same source snapshot, supports title and source-tag filters, and returns public fields only. Third-party titles and URLs are preserved. Refresh times can differ from the public page.

GET

/api/v1/discover

List the public Discover feed

Returns the same trending topics and public video metadata as the public Discover page for the same source snapshot; refresh times can differ. Sources are YouTube, Hacker News, Wikipedia, Google Trends, and TikTok. Third-party titles and URLs are preserved. Internal descriptions and model metadata are excluded. Filter titles with q or select one visible source with tag. Requests are limited to 60 per minute per API key; invalid queries count toward this limit. This endpoint requires a configured, available rate-limit store. If it is unavailable, requests return 503 rate_limit_unavailable with Retry-After: 60 to keep throttling enforced.

Authentication: Bearer API key required

curl "https://reviral.ai/api/v1/discover" \
  -H "Authorization: Bearer $REVIRAL_API_KEY"

Query parameters

page integer (min 1) · Optional: One-based result page. Default: 1.
limit integer (min 1, max 100) · Optional: Items per page. Default: 24.
q string · Optional: Case-insensitive title filter, matching the public page search box. max length 200.
tag string: youtube | hackernews | wikipedia | google_trends | tiktok · Optional: Visible source tag from the public page.

Responses

200: Paginated Discover page feed
400: Invalid query parameters
401: Key is missing, revoked, or invalid
429: Too many requests
502: Discover feed unavailable
503: Models or rate limiting are temporarily unavailable

Quickstart Models Errors