us_congress_trades

Search US Congress stock trades

Returns STOCK Act disclosures across the House and Senate. Filter by ticker (AAPL or AAPL:US), politician last name, party, chamber, sector, transaction type, and publication date range. Sort by publication date, trade date, disclosed value, or reporting gap. Page with offset. Each row has the politician, issuer, ticker, buy/sell/exchange, disclosed value, dates, and reporting gap in days.

get/us_congress_trades/trades

Request

  • Base URL: https://www.socialcrawl.dev/v1
  • URL: https://www.socialcrawl.dev/v1/us_congress_trades/trades
  • Auth: API key in header x-api-key

Query parameters

tickerstring

Stock ticker. Bare symbols such as AAPL are sent as AAPL:US. Use AAPL:US when the search filter would otherwise miss.

politicianstring

Politician last name (case-insensitive).

party'democrat' | 'republican'

democrat or republican.

chamber'senate' | 'house'

senate or house.

sectorstring

Issuer sector slug, for example information-technology or health-care.

tx_type'buy' | 'sell' | 'exchange'

buy, sell, or exchange.

start_datestring

Publication date lower bound (YYYY-MM-DD).

end_datestring

Publication date upper bound (YYYY-MM-DD).

sort'pub_date' | 'tx_date' | 'value' | 'reporting_gap'

pub_date (default), tx_date, value, or reporting_gap.

order'asc' | 'desc'

desc (default) or asc.

limitinteger

Page size, 1 to 100. Default 20.

offsetinteger

Rows to skip. Prefer the universal cursor parameter. Native upstream cursor param. Send the universal cursor instead: the API maps it to this name for you.

cursorstring

Universal pagination cursor. Send pagination.next_cursor from the previous response back verbatim: the API maps it to this endpoint's native offset (offset style). You never construct, decode, or look up a cursor. Omit it for page 1.

Headers

Cache-Controlstring

Send no-cache to bypass the response cache and force a live fetch. Billed at the normal endpoint cost; the fresh result is written back to cache for the next caller. Only the no-cache directive triggers this. See the Response Schema guide for details.

Idempotency-Keystring

Optional UUID that makes the request safely retriable. The key is reserved atomically per account before billing. A concurrent retry receives 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After of 1 second while the original is young, growing to a quarter of the time it has been running (at most 30); a crashed reservation expires after 5 minutes. A replay keeps the cached payload immutable except for billing metadata: credits_used becomes 0, idempotent_replay becomes true, and credits_remaining is refreshed to the current balance. A known current balance appears in both the body and X-Credits-Remaining header; no balance row resolves to 0. On a transient lookup failure, body credits_remaining is null and X-Credits-Remaining is omitted. Completed outcomes expire after 24 hours. If the claim store is unavailable, the request fails closed before billing. GET endpoints do not combine idempotent replay with Server-Sent Events: use Accept: application/json when sending this header. The unsupported key-plus-SSE combination is rejected before billing.

Response

Successful response

successboolean required

Whether the request succeeded

platformstring required

Platform name

endpointstring required

API endpoint path

credits_usedinteger required

Number of credits consumed

credits_remaininginteger nullable required

Current account balance, or null when this response could not establish one. Free cache hits always return null because they do not establish an authoritative post-request balance. An idempotency replay also returns null when its current-balance lookup fails. It is never a fabricated zero, so a zero here means the account really is empty. The authoritative reading is the one on a billed response, which comes straight from the deduction.

request_idstring required

Unique request identifier for support

cachedboolean required

Whether the response was served from cache

idempotent_replayboolean

True only when this response is an idempotency replay

Example response

{
  "success": true,
  "platform": "us_congress_trades",
  "endpoint": "/v1/us_congress_trades/trades",
  "credits_used": 1,
  "credits_remaining": 4999,
  "request_id": "req-abc123",
  "idempotent_replay": true,
  "meta": {
    "hint": {
      "code": "search_multi",
      "message": "You searched \"matcha\" on 3 platforms one call at a time; /v1/search/multi returns each platform's own search rows in one call at the same price per platform, and a platform with no rows is not charged.",
      "method": "GET",
      "path": "/v1/search/multi?query=matcha&platforms=instagram,tiktok,youtube"
    }
  },
  "pagination": {
    "next_cursor": "sc.eyJ2IjoyLCJjIjoiMiIsInAiOiJwYWdlIn0",
    "has_more": true,
    "page_size": 30,
    "stopped_at": "known_id"
  }
}

Changes

No recorded changes to this operation across all 1 revision of this API.