Skip to main content
GET https://xquik.com/api/v1/radar
Free. This endpoint does not consume credits.
Build a social media monitoring feed from ranked public topics. Radar covers Reddit, GitHub, technology news, search trends, Wikipedia, prediction markets, and startup growth. Apply the relevant source, category, region, and time window to each request. Authenticate every Radar request. You need no active subscription. Radar consumes no credits.

What is a social media monitoring API?

A social media monitoring API returns public posts and trends as structured records. Radar exposes those records through one REST API endpoint. Each response uses structured JSON and stable field names. Radar gives every supported public source the same RadarItem shape. The GET /radar endpoint filters items by source, category, region, and age. The response ranks recent topics. Radar is not an exhaustive source archive. Radar combines several public topic sources. It does not mirror every social network. It also does not return X tweets, replies, followers, or timelines. For X-specific monitoring, Search Tweets finds brand mentions, hashtags, replies, and keyword matches. Use stable fields to compare titles, regions, timestamps, and scores. You need no separate adapter per source. Keep full social listening data in a dedicated platform API. Radar is not a social listening API for every major social platform. It does not replace platform APIs for unsupported social platforms. Radar returns ranked topics, not complete post, comment, or brand-mention records. Radar provides no keyword search volume or long-term history. Radar includes no more than 168 hours of history.
Use Radar as a trending topics API for dashboards, alerts, and research queues. Start with a narrow time window. Apply source and category together or separately.
  1. Call GET /radar with your API key.
  2. Filter one source when the request names a platform.
  3. Limit the region when location affects the result.
  4. Sort or filter records by score in your application.
  5. Store each id to prevent duplicate dashboard rows.
  6. Continue with nextCursor while hasMore stays true.
Use source=reddit for Reddit posts. Use source=github for trending repositories. Other source identifiers work the same way. One request format covers every supported feed.
Radar returns recently indexed topics. It does not stream every new event. Use publishedAt for source timing. Use createdAt for indexing timing. Start each scheduled poll without after. Use nextCursor only for later pages within that poll. The contract guarantees neither cross-poll cursor lifetime nor snapshots. Deduplicate records by items[].id. Never use an item ID to order separate polling runs. Respect every 429 rate limit response. Wait before the next poll. Polling tracks recent changes. It promises no delivery deadline.

Can Radar track brand mentions and sentiment?

Radar has no keyword query. Radar does not provide a complete brand monitoring index. Compare returned titles and descriptions against a saved brand dictionary. That comparison covers only the current Radar feed. Radar does not analyze sentiment. The score value measures relevance, not sentiment. Do not classify a high score as positive or negative sentiment. Use Search Tweets to query exact X (Twitter) mentions. Use Radar for ranked cross-source topics. Radar does not cover every brand mention.

How do you evaluate Radar topic accuracy?

Evaluate each item against the source fields. A high trend score does not prove a claim is correct or popular everywhere.
  1. Match source and sourceId to the intended feed.
  2. Open url when present. Compare its title and description with the item.
  3. Compare publishedAt with createdAt to separate publication from indexing.
  4. Confirm region, category, and language match the intended alert.
  5. Interpret metadata with the source-specific fields documented below.
  6. Deduplicate by id, then retain the score used for that polling run.
Radar does not guarantee complete source coverage or independent fact verification. Review the original source before publishing an alert, report, or customer-facing dashboard entry.

Integrate Radar into a monitoring dashboard

Request one page, validate the response, and render each RadarItem. Save the item ID, source, source ID, score, region, and timestamps. Group rows by source for a multi-feed dashboard. Rank dashboard rows by the returned score value, then filter them by publishedAt. Open the returned url when present. Use hasMore and nextCursor for background ingestion. Never construct a cursor. Keep it with matching filters during one pagination run. Changing source, category, region, or hours starts a different result set. Choose a searchable news API for exact keyword or domain matching. Use Radar for normalized records from its documented sources only.

Headers

Query parameters

Response

RadarItem fields

Metadata

Use source to interpret metadata. Multiword fields use camelCase in the default REST response and snake_case through API MCP.

Reddit

Every Reddit item identifies author, subreddit, and sourceFormat. Items include available post content, media, and engagement metrics. Older items can hold fewer fields.Reddit does not publish exact upvote and downvote counts. Treat estimatedUpvotes and estimatedDownvotes as estimates because Reddit may fuzz public score and ratio. numberComments is a count. Radar returns no comment bodies.

Startup growth

Startup growth items always include mrr, growthPercent, last30Days, total, customers, activeSubscriptions, and onSale.Radar orders these items by reported 30-day revenue growth. metadata.rank is the revenue rank reported by the source. It does not equal the result position. The top-level imageUrl contains the startup logo when available.

Other sources

Examples

Response.

Pagination

Radar uses cursor-based pagination. When hasMore is true, pass nextCursor as after to fetch the next page.
Next steps.

Response examples

200 example

  • 400 { "error": "invalid_input", "message": "Invalid input. Check the request body." }
  • 401 { "error": "unauthenticated", "message": "Authentication required. Provide a valid API key or bearer token." }
  • 403 { "error": "api_key_paused", "message": "This API key is paused. Resume it at dashboard.xquik.com/api-keys to use it again." }
  • 429 { "error": "rate_limit_exceeded", "message": "Too many requests. Try again later.", "retryAfter": 60 }