Introduction
Overview of the SnitchFeed HTTP API.
The SnitchFeed HTTP API is for searching public posts on LinkedIn and X (Twitter), plus a read-only billing usage endpoint. There are no other data or management endpoints in this API today.
Endpoints
| Method | Path | Description |
|---|---|---|
POST | /v1/data/twitter/searchTweets | Search posts on X |
POST | /v1/data/linkedin/searchPosts | Search posts on LinkedIn |
GET | /v1/billing/usage | Credit usage for the current billing period (read-only) |
Search calls deduct credits on each successful response; see Credits (API).
Base URL
All API requests are made to:
https://api.snitchfeed.com/v1Paths above are relative to that base (for example, POST https://api.snitchfeed.com/v1/data/twitter/searchTweets).
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 and per search surface (Twitter vs LinkedIn). See Rate limits.