## linkedin/search-posts-native

`GET /v1/linkedin/search-posts-native`

Search public LinkedIn posts beyond the external search index, with post links, text, dates, author and available engagement. Ordinary posts have no title; article.title is the attached article title. Author websites are included when supplied. Coverage is incomplete, source totals may change, and there is no exhaustive or real-time guarantee. Relevance order; dates filter the acquired page. For bounded author-location and public-contact enrichment, use /examples/linkedin-post-search.mjs with separately priced profile lookups and an explicit credit cap. Author location is not post origin. Existing indexed search remains four credits.

*Post search*

| Parameter | Required | Description |
| --- | --- | --- |
| `query` | yes | Keywords, 1–200 characters. Results use relevance order. Coverage is incomplete and freshness is not guaranteed. — e.g. `OpenAI` |
| `date_posted` | no | Source window: last-day, last-week or last-month (default). Keep unchanged with the cursor. Local timestamp filtering also excludes unknown dates and records outside the requested window. — e.g. `last-month` |
| `date_from` | no | Optional inclusive UTC date YYYY-MM-DD, applied only to the acquired page within date_posted. It does not expand historical coverage. Unknown dates are excluded and counted. |
| `date_to` | no | Optional inclusive UTC date YYYY-MM-DD. Same bounded-page scope as date_from. Empty filtered pages can still have continuation. |
| `cursor` | no | Complete opaque continuation from this endpoint, same account, query and filters. Expires one hour after the first page. Each further source page has the normal five-credit price; source totals can change. |
| `dry_run` | no | Read a zero-credit estimate without fetching sources, running AI, or reserving credits. Cache status is a snapshot, not a guarantee at execution. Accepted values: 1, 0, true, false. Case, spaces, hyphens and underscores are interchangeable. — e.g. `1` |
| `judgments` | no | Add bounded AI labels to eligible returned records (default on). off preserves the original data shape. Unclassified records remain present; labels depend on evidence, time, capacity and the existing request budget. No label surcharge. Accepted values: on, off. Case, spaces, hyphens and underscores are interchangeable. — e.g. `on` |
| `label` | no | Set none to disable labels; default enables the endpoint’s label set. Equivalent to judgments=off. Accepted values: default, none. Case, spaces, hyphens and underscores are interchangeable. — e.g. `none` |
| `label_evidence` | no | Include exact supporting sentences and zero-based sentence indexes when a label has validated evidence. No extra charge or change to decisions. Accepted values: 1, 0, true, false. Case, spaces, hyphens and underscores are interchangeable. — e.g. `1` |
| `exclude` | no | Optionally remove confidently labelled engagement bait. Uncertain and unclassified records stay; removed IDs and an owner-bound recall reference are returned. Accepted values: engagement_bait. Case, spaces, hyphens and underscores are interchangeable. — e.g. `engagement_bait` |
| `fit` | no | Use goal to replace confidently irrelevant records with recall stubs. Keeps first, last, relevant and uncertain records; preserves order. Full evidence is stored for 24 hours when available. Accepted values: goal. Case, spaces, hyphens and underscores are interchangeable. — e.g. `goal` |
| `goal` | no | Required with fit=goal: describe the task in at most 600 characters. Supplied text is task context, never permission to act on posts. — e.g. `Find concrete product complaints` |
| `tokens` | no | Optional soft response target for fit=goal, 256–32000. Safety and evidence retention take priority, so the returned result may exceed it. — e.g. `4000` |

**Cost:** 5 credits at list price per successful uncached response; variable-cost operations may quote or settle a different charge. Confirmed uncharged or refunded failures report zero. Pending reconciliation can report credits_used:null; retain request_id and the original idempotency key.

```bash
curl "https://www.monocrawl.com/v1/linkedin/search-posts-native?query=OpenAI" \
  -H "x-api-key: mn_your_key_here"
```

### Response data

Illustrative abbreviated data; documented core fields are optional and may be null. Additional source fields are allowed.

```json
{
  "items": [],
  "count": 0,
  "retrieved_count": 0,
  "cursor": null,
  "has_more": false,
  "total": null,
  "source_total": 0,
  "completeness": "unknown"
}
```

[Field reference](https://www.monocrawl.com/docs/endpoints/linkedin/search-posts-native#response) · [JSON Schema for response.data](https://www.monocrawl.com/schemas/linkedin/search-posts-native.json)