Introduction

Overview of the SnitchFeed HTTP API.

The SnitchFeed HTTP API searches public posts on LinkedIn, X (Twitter), and Hacker News, fetches LinkedIn company and person data, and reads your own organization's data — mentions, listeners, feeds, and billing usage.

Endpoints

Your organization's data (read-only)

MethodPathDescription
GET/v1/mentionsList mentions matched by your listeners, cursor-paginated, sortable by newest or AI fit score
GET/v1/mentions/{id}Get a single mention by id
GET/v1/mentions/countCount mentions matching a set of filters
GET/v1/listenersList listeners (brand/keyword monitors)
GET/v1/listeners/{id}Get a single listener by id
GET/v1/feedsList saved feeds (filtered views)
GET/v1/feeds/{id}Get a single feed by id
GET/v1/organization/contextBrand/business context for the organization this API key belongs to (same info as the dashboard's Brand Context page)
GET/v1/organization/usageCredit usage for the current billing period

These endpoints are read-only and do not consume credits.

MethodPathDescription
POST/v1/data/twitter/tweets/searchSearch posts on X
POST/v1/data/linkedin/posts/searchSearch posts on LinkedIn
POST/v1/data/linkedin/company/getFetch a LinkedIn company page
POST/v1/data/linkedin/person/postsFetch posts from a LinkedIn person profile
POST/v1/data/linkedin/person/commentsFetch comments authored by a LinkedIn person
POST/v1/data/linkedin/posts/commentsScrape comments on a LinkedIn post
POST/v1/data/linkedin/posts/reactionsScrape reactions on a LinkedIn post
GET/v1/data/linkedin/industriesSearch LinkedIn industry codes (read-only)
POST/v1/data/hackernews/searchSearch Hacker News stories and comments

Metered data calls deduct credits on each successful response; see Credits (API). LinkedIn search, person posts, and person comments always return the full page.

POST /v1/data/linkedin/person/comments is comments by a person (profile URL). POST /v1/data/linkedin/posts/comments is comments on a post (post URL).

Mentions, listeners, and feeds use _-prefixed public ids (men_..., lis_..., svw_...) rather than sequential numbers.

Base URL

All API requests are made to:

https://api.snitchfeed.com/v1

Paths above are relative to that base (for example, POST https://api.snitchfeed.com/v1/data/twitter/tweets/search).

Authentication

Use a Bearer token on every request. See Authentication.

Response format

All responses are JSON. Successful responses use 2xx status codes. Errors return a structured body:

{
  "requestId": "01HXYZ…",
  "error": {
    "code": "unauthorized",
    "message": "Invalid or revoked API key."
  }
}

Validation errors may include an issues array with field paths and messages. Rate limit and LinkedIn outage responses may include retryAfter (seconds) and a matching Retry-After header.

Rate limits

Limits apply per organization: 20 requests per minute per search surface, and at most 2 in-flight requests across all v1 endpoints. See Rate limits.

On this page