# Coresignal Employee Post Search by Filter

> Coresignal Employee Post Search by Filter is a paid API for AI agents from x402.orthogonal.com, paid per call via x402, $0.021/call, status unknown (last checked 2026-09-13).

Searches professional network posts by author profile URL, keywords, or date range, returning an array of numeric post IDs for further retrieval.

## Facts

- Endpoint: POST https://x402.orthogonal.com/coresignal/v2/employee_post/search/filter
- Price: $0.021/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/coresignal-employee-post-search-by-filter-060a80e8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_heViHvs5CpetOxVQnWUmB

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability coresignal-employee-post-search-by-filter-060a80e8 -d '<json body>'
```

Example prompt: Search for LinkedIn posts by the author at linkedin.com/in/satya-nadella that mention 'artificial intelligence', published between 2025-01-01 and 2025-06-30, and give me the post IDs so I can fetch the full content.

## When to prefer this

Use this endpoint when you need to discover posts from a specific LinkedIn author or matching specific keywords and date ranges, and you plan to follow up with the Employee Posts Collect endpoint for full content. Prefer this over scraping approaches when you need structured, filterable post discovery at scale. Best suited for research, monitoring, or lead intelligence workflows where you need to identify relevant posts before fetching details.

## Known failure modes

- No matching posts found — returns empty array if filters are too narrow or author has no posts
- Invalid author_profile_url format — returns error if URL is malformed or not a recognized professional network profile
- Invalid date format — returns error if dates are not in YYYY-MM-DD format
- Rate limiting or quota exceeded — returns 429 or payment error if call budget is exhausted
- Ambiguous or overly broad keyword returns very large ID sets that may be expensive to collect in bulk

## How this service works

Search for professional network posts using filters like author profile URL or keywords. Pass filters in the request body (not a post URL). Returns an array of numeric post IDs (e.g., ["7431869637207928834", ...]). Use these IDs with the 'Employee Posts Collect' endpoint to get full post content.

## Output

An array of numeric post ID strings (e.g. ["7431869637207928834", "7431869637207928835"]) matching the filter criteria. These IDs must be passed to the Employee Posts Collect endpoint to retrieve full post content including text, media, and metadata.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "article_body": {
   "type": "string",
   "description": "Keywords to search within post content (e.g., 'artificial intelligence', 'hiring')"
  },
  "author_profile_url": {
   "type": "string",
   "description": "Professional network profile URL of the post author"
  },
  "date_published_gte": {
   "type": "string",
   "description": "Posts published on or after this date, format YYYY-MM-DD (e.g., '2025-01-01')"
  },
  "date_published_lte": {
   "type": "string",
   "description": "Posts published on or before this date, format YYYY-MM-DD (e.g., '2025-12-31')"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/coresignal-employee-post-search-by-filter-060a80e8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.orthogonal.com](https://www.zero.xyz/host/x402.orthogonal.com/llms.txt)