POST /post_keyword_search • Credits: 0.1 credits per returned post

Post Keyword Search finds public LinkedIn posts that match a keyword. The response holds a content array of posts with the author, the post text, the engagement counts and the share URL. Each returned post costs 0.1 credits, so a full page of 50 posts costs 5 credits.

A marketing team needs to know who talks about a topic on LinkedIn. Post Keyword Search runs one keyword query across public LinkedIn posts and returns the matches as JSON. Seven filters narrow the search by date, by content type, by author and by company. The data source is LinkedIn. One call returns one page of posts, plus totalElements and totalPages for the whole result set. The other post endpoints start from a known company or a known person. Post Keyword Search starts from a topic and finds the authors for you.

Post Keyword Search accepts the POST method only. Every parameter goes in the JSON request body. If you send GET, the API returns 405 with the message post_keyword_search only supports POST.

CAUTION: Set limit on every request. Each returned post costs 0.1 credits, so a full pass over 483 posts costs 48.3 credits.

Post Keyword Search accepts ten parameters. Only keyword is required. The names below are the real request body names.

If you omit sort, the API sorts by RELEVANCE. If you omit datePosted or contentType, the search applies no date filter or content filter.

The request body accepts the ten names in the parameter table and no others. If the body holds any other key, the API returns 400 with the message Unknown input field(s): <name>.

One name often causes this failure. The page size parameter is limit. The request body rejects size.

Post Keyword Search has seven filter parameters. Combine them in one request body to narrow the result set.

The example below finds video posts about developer tools from the past week. The author job title must match Head of Growth.

Post Keyword Search returns one page per call. Set limit to the page size and page to the page number. The page count starts at 0, so page: 0 returns the first page.

To read the next page, send the same request body again with page set to 1. Keep every other parameter the same, so that the result set and the order stay stable. Read totalPages to find how many pages the result set holds. Read totalElements to find the total number of matched posts. The first and last booleans mark the first page and the last page of the result set.

Each returned post costs 0.1 credits. The page size changes the number of calls, not the total cost.

Post Keyword Search turns a topic into a list of named authors and ranked posts. Follow these steps for a weekly social listening run.

To find the people who reacted to a post, send the post URN to the RichAPI Post Activities endpoint. To enrich an author, send the profile URL to the RichAPI Profile Enrichment endpoint.

The example below shows one post from a page of 10. A full page holds up to limit posts.

Each object in the content array holds the fields below.

Post Keyword Search costs 0.1 credits for each post in the response. One credit costs $0.02 on the 1,000 and 5,000 credit packs, so one post costs $0.002 there. Larger packs cost less per credit.

RichAPI charges 0.1 credits for each post in a 2xx response. A response outside the 200 range costs nothing.

Cost of one call, by page size:

Cost of many calls, at 50 posts per call:

Because the price is per post, the page size does not change the cost of a full pass. A result set of 483 posts costs 48.3 credits at every limit value.

Post Keyword Search is billed per result: 0.1 credits for each post on the page that you receive. totalElements does not change the price.

A search that returns one page of 50 posts costs 5 credits. A search that returns one page of 10 posts costs 1 credit. The keyword can match 40 posts or 4 million: only the posts that you receive count.

The totalElements value in the response tells you how many posts match your keyword across all pages. It is a count, not a charge. To read more of that set, send more pages. Each post on them costs 0.1 credits.

RichAPI charges no credit for any response outside the 200 range.

Post Keyword Search costs 0.1 credits per returned post, so a full page of 50 posts costs 5 credits. That is $0.10 on the 1,000 and 5,000 credit packs. Larger packs cost less per credit. The totalElements count in the response does not change the price.

Post Keyword Search charges 0.1 credits per returned post. It does not bill from totalElements. A call that returns 50 posts costs 5 credits, and a call that returns 1 post costs 0.1 credits.

Post Keyword Search is a POST endpoint at https://api.richapi.ai/api/v1/post_keyword_search. Every parameter goes in the JSON request body. A GET request returns 405.

The request body parameter for the page size is limit, not size. The request body rejects size with a 400 error.

One Post Keyword Search page returns up to 50 posts in the content array. Set limit to the page size. Read numberOfElements for the count on the page that you received.

Send the same request body again with page set to 1. The page count starts at 0, so page: 0 is the first page and page: 1 is the second page.

A Post Keyword Search call that returns zero posts costs 0 credits, because the price is per returned post.

Set fromCompany to an array of company entity URNs. To read the whole feed of one company page, use the RichAPI LinkedIn Company Posts endpoint. That endpoint costs 0.2 credits per returned post.

Each post holds numReactions, numComments and a reactionType object. The reactionType object holds one count per reaction type, for example like, interest and appreciation.