Content Filters: Search Inside LinkedIn, Twitter/X & YouTube Signal Content

Shipped June 4, 2026.

Search endpoints now accept an optional content_filters object that searches inside the enriched content of social signals - e.g. "companies whose LinkedIn posts mention churn" or "contacts posting about Salesforce, excluding hiring posts."

Where it works

POST /v1/companies/search and POST /v1/contacts/search, for the seven social signal types: linkedin-post-company, linkedin-post-contact, linkedin-comments-contact, twitter-company-posts, twitter-contact-posts, youtube-company, youtube-contact. Sending content_filters with any non-social signal_types returns a 400 invalid_request.

The five filter fields

Each is a { "contains": [...], "not_contains": [...] } clause (up to 20 terms per clause, 1-500 chars per term):

• keywords - case-insensitive substring match across post/comment/video text and summaries
• tech_mentioned - exact (case-insensitive) match on extracted technologies_mentioned[].name
• competitors_mentioned - exact match on extracted competitors_mentioned[].name
• pain_points - substring match on extracted pain_points[].topic
• initiatives - substring match on extracted initiatives[].topic

Terms within a contains array are OR'd; not_contains excludes on any hit; the five fields AND together.

Example

{
  "signal_types": ["linkedin-post-company"],
  "detected_after": "2026-06-01",
  "content_filters": {
    "keywords": { "contains": ["churn"], "not_contains": ["hiring"] },
    "tech_mentioned": { "contains": ["Salesforce"] }
  }
}

Tips

• Prefer the structured fields (tech_mentioned, competitors_mentioned, pain_points, initiatives) over keywords when they fit - they run against indexed extracted fields and are typically sub-second.
• Keep broad keywords searches to a ≤30-day detected_after window, or pair them with a selective clause. A query that's too broad returns a 408 query_timeout with specific narrowing suggestions in the body - it is not charged.

Questions? [email protected]