--- title: "Search posts" method: POST path: "/v1/{account_id}/search/posts" tags: ["Search"] --- # Search posts `POST /v1/{account_id}/search/posts` ## Request - Base URL: `https://api.curviate.com` - URL: `https://api.curviate.com/v1/{account_id}/search/posts` - Auth: HTTP bearer Searches LinkedIn posts using structured filters. To search from a pasted LinkedIn search URL instead, use POST .../search. Returns text, counts, author and attachments; the text can repeat fragments around links, mentions and hashtags, so get the post by its id for the clean body. ## Path parameters - `account_id` string, required ## Query parameters - `offset` integer - `limit` integer - `cursor` string ## Request body - object - `keywords` string: Full-text keyword search in posts. - `sort_by` 'relevance' | 'date': Sort order: relevance (default) or date (newest first). - `date_posted` 'past_day' | 'past_week' | 'past_month': Filter by post recency. - `content_type` 'videos' | 'images' | 'live_videos' | 'collaborative_articles' | 'documents': Filter by content type (single value, not an array). - `posted_by` object: Filter to posts by specific authors (members, companies, yourself, connections, or people you follow). - `member` string[]: Opaque member IDs from GET /v1/{account_id}/search/parameters?type=PEOPLE. - `company` string[]: Opaque company IDs from GET /v1/{account_id}/search/parameters?type=COMPANY. - `me` boolean: Restrict to your own posts. - `first_connections` boolean: Restrict to posts by your 1st-degree connections. - `people_you_follow` boolean: Restrict to posts by people you follow. - `mentioning` object: Filter to posts mentioning specific members or companies. - `member` string[]: Opaque member IDs from GET /v1/{account_id}/search/parameters?type=PEOPLE. - `company` string[]: Opaque company IDs from GET /v1/{account_id}/search/parameters?type=COMPANY. - `author` object: Filter to posts by author attributes (industry, company, or keywords). - `industry` string[]: Opaque industry IDs from GET /v1/{account_id}/search/parameters?type=INDUSTRY. - `company` string[]: Opaque company IDs from GET /v1/{account_id}/search/parameters?type=COMPANY. - `keywords` string: Free-text keyword match on the author. ## Response `200` A page of posts matching the filters. Each item carries post text, engagement counters, author details, and attachments when available. - object - `object` 'post_search_result', required: Response type discriminator. - `items` object[], required: Post search result items. - `id` string, required: Opaque platform id identifying the post. - `share_url` string: Shareable post URL. Present when available. - `text` string: Post text content. Present when available. Can repeat fragments around links, mentions and hashtags; get the post by its id for the clean body. - `created_at` string, nullable, required: ISO-8601 UTC datetime the post was published, derived from the post's own activity identity (the same source as get-post's `created_at`). null when the result carries no activity identity to derive it from. - `author` object: Post author object. Present when available. - `id` string - `name` string, nullable: Author's display name, on the shape that carries `name`. Read `name` when present, else `display_name`. - `display_name` string: Author's display name, on the shape that carries `display_name` instead of `name`. - `is_company` boolean - `type` string: Author entity type (for example individual or organization), on the shape that carries `display_name`. - `public_identifier` string, nullable - `permissions` object: Interaction permissions on this post. Present when available. - `can_react` boolean - `can_share` boolean - `can_post_comments` boolean - `is_repost` boolean: true if this post is a repost. Present when available. - `attachments` object[]: Post attachments array. Present when the post carries attachments. - `reactions` object[]: Per-reaction-type breakdown. Present when the post has reactions. - `type` string: Reaction type (e.g. like, celebrate). - `count` number - `reaction_count` number, required: Total reaction count, the sum of reactions[].count. - `comment_count` number, required: Total comment count on the post. - `repost_count` number, required: Total repost count on the post. - `paging` object, required: Paging metadata. - `total_count` number, nullable, required: Always null on this search. LinkedIn stopped reporting how many results match, so there is no total to page toward; walk the pages with cursor until it comes back null. A short or empty page is not the end: only a null cursor is. - `cursor` string, nullable, required: Opaque next-page cursor; null on the last page. - `notices` object[]: Present only when there is something to report about this page. Each entry names a condition that is true of the response but not visible in it, so a result set is never misleading by omission. Absent when there is nothing to report. - `code` 'FILTER_VALUE_UNRESOLVED' | 'FILTER_VALUE_UNCHECKED' | 'SOME_RESULTS_HIDDEN' | 'ALL_RESULTS_HIDDEN' | 'PAGE_TRUNCATED', required: FILTER_VALUE_UNRESOLVED: the value matched no known filter option, so it was sent on as an id we could not check. FILTER_VALUE_UNCHECKED: the value already looked like an id, so it was never looked up, and this page came back empty. SOME_RESULTS_HIDDEN: some people on this page were not disclosed to the connected account, so those entries cannot be read back. ALL_RESULTS_HIDDEN: none of the people on this page were disclosed, so the page yielded nothing you can act on, even when more pages follow. PAGE_TRUNCATED: this page is short because the search stopped fetching upstream pages, not because the results ran out; follow cursor, and treat only a null cursor as the end. Branch on this rather than on message. - `message` string, required: One sentence explaining the condition and how to resolve it. - `field` string: The request field the notice is about, dotted for nested filters. - `value` string: The offending value. - `safety_warning` SafetyWarning: Present on a successful response when this account crossed an account-safety ceiling while the affected budget row is on the default warn posture. The action still happened. Field-identical to the BUDGET_EXHAUSTED error body except that blocked is false and hint.message describes the outcome, so one branch handles both postures and switching the account to enforce is a configuration change rather than a client rewrite. - `row` string, nullable, required: The budget row that breached, for example profile_views or pending_invites. Null when the breach is not about a row: an activity_window warning on an action that spends no budget of its own (editing a message, dismissing a notification, a Recruiter or Sales Navigator admin action) is still governed by the hours the account works in. Read hint.parameter for what to change; whenever this is null it names posture, because the activity window edges are set per action type and this action has none, so the levers that reach it are the account timezone and posture. - `reset_at` string, nullable, required: The instant the refusal lifts: the window roll on a ceiling refusal, the next window open on an activity-window one. Null in the two cases no clock frees, the pending_invites gauge and InMail credits (row inmail). - `hint` object, required - `parameter` string, required: The settable parameter on PATCH /v1/{account_id}/safety-policy. - `message` string, required: What the condition is and what changing that parameter would do. This is the one field whose text differs from the BUDGET_EXHAUSTED refusal: here it says the action went through, and on a ceiling breach how far past the ceiling this row now stands, rather than telling you to set posture to warn when it already is. Branch on parameter, reason and blocked, never on this text. - `reason` 'ceiling' | 'activity_window', required: Which rule was crossed. ceiling means the row's configured limit is spent; activity_window means the account is outside the hours it works in, which is a different fact with a different remedy. hint.parameter names the right setting for each. - `blocked` boolean, required: Always false here. True on the BUDGET_EXHAUSTED refusal carrying the same payload. ## Other responses - `400`: Invalid request body, malformed filter, malformed cursor, or invalid content_type. A filter value that matches no filter option is NOT rejected here: it is sent on as an id and reported in notices[] on the 200, because a value we cannot resolve by name may still be a valid id. - `401`: Missing or invalid API key. - `404`: The supplied account_id does not belong to this tenant. An id whose connection was replaced or removed also stops resolving here, and it is already absent from the list, so re-read `GET /v1/accounts` for the current id. - `413`: Payload too large, the request body exceeds the size limit. - `422`: Either FILTER_CANDIDATES_REQUIRED, meaning a filter value matched several options and you must choose one, or ACCOUNT_RESTRICTED, meaning the connected account cannot perform searches. On FILTER_CANDIDATES_REQUIRED the body carries unresolved[], listing every offending field with its value and the candidate ids to pick from, plus a next_action sentence. Re-send the request with a chosen id. - `429`: Rate limited, slow down and retry after the hinted delay. - `500`: Internal error. - `502`: A temporary error occurred. Please try again. - `503`: Service unavailable. - `504`: Gateway timeout. --- [API](https://skmtc.dev/curviate/apis/curviate-api.md) · [All operations](https://skmtc.dev/curviate/apis/curviate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/curviate/apis/curviate-api/revisions/eab848801d95?raw)