---
title: "Get posts behind search results"
method: POST
path: "/v1/search-results/posts"
tags: ["Evidence"]
---

# Get posts behind search results

`POST /v1/search-results/posts`

## Request

- Base URL: `https://api.toksta.com`
- URL: `https://api.toksta.com/v1/search-results/posts`
- Auth: HTTP bearer
- TypeScript: <https://skmtc.dev/toksta/apis/toksta-public-api/docs/v1/search-results/posts/post.ts> (a function with typed inputs; its response is checked against the schema)

Return the LinkedIn posts behind search results (keyword evidence) for a creator selection.

**Keywords:** provide `keywords` (array of strings) OR a `result_set_id`/`result_set_ids` (keywords are then inferred from the saved search). Sending `creator_ids` alone, with no keywords and no result set, returns `400`.

## Request body

- object
  - `creator_ids` string[]: Creator UUIDs to operate on. Takes precedence over result_set_id / result_set_ids when provided.
  - `result_set_id` string: A single `result_set_id` returned by a prior discovery search. Resolved to its ranked creators.
  - `result_set_ids` string[]: Multiple result set IDs to merge (dedupe) into one creator selection.
  - `top_n` integer: When selecting from result set(s), take only the top N ranked creators.
  - `ranks` integer[]: When a single result_set_id is provided, select specific 1-based ranks (e.g. [1,3,5]).
  - `keywords` string[]: Keywords to match posts against. Required unless a result_set_id/result_set_ids is provided.
  - `posts_limit_per_creator` integer: Evidence posts per creator (1-10). Defaults to 3.
  - `detail_level` 'summary' | 'full': Response verbosity. `summary` (default) returns trimmed fields; `full` returns the complete records.

## Response `200`

Keyword evidence posts per creator.

- object: Keyword evidence posts per creator.
  - `success` true, required
  - `data` object, required: Operation payload. See the example for the exact field structure.
  - `meta` object, required
    - `request_id` string, required
    - `trace_id` string

## Other responses

- `400`: Bad request or validation error (`BAD_REQUEST` / `VALIDATION_ERROR`).
- `401`: Missing, invalid, or revoked API key.
- `402`: Insufficient credits for this operation.
- `403`: API access disabled or workspace entitlement required.
- `404`: Resource not found, or result expired past retention.
- `429`: Rate limit exceeded — back off per `Retry-After`.
- `500`: Unexpected server error.
- `501`: Endpoint is registered but not implemented yet.

---

[API](https://skmtc.dev/toksta/apis/toksta-public-api.md) - [All operations](https://skmtc.dev/toksta/apis/toksta-public-api/llms.txt) - [OpenAPI document](https://skmtc.dev/toksta/apis/toksta-public-api/revisions/a8cf8189fdd1?raw)
