public

Find public posts by topic or by who posted

Changed on Oct 22, 2026

Search public posts by topic or hashtag, by one person (author), by the people at a company (authorCompany), or by a kind of person (authorTitle, authorLocation). Each post carries who published it and when, and can be mined for people with collect_engagers. The people who wrote the posts are saved to the list unless save is skip. Cost: posts by one person cost one search by the posts it brings back: 4 credits for up to 10, 11 for 25, 24 for 50; any other post search costs by the posts it asks for and the authors it checks: 9 credits for up to 10 posts, 24 for 25, 49 for 50 (19 for 10 when a company or a place is checked), plus about 1 credit for every 2 authors checked; nothing when no post comes back; reading the posts in full adds 1 credit a page of results. creditsUsed says what the call spent.

post/public/post-search

Request

Base URL: https://api.bereach.ai
URL: https://api.bereach.ai/public/post-search
Auth: HTTP bearer

Request body

querystring

Topic keyword or hashtag to search posts for. Optional when who posted is given.

authorstring

One person whose own posts are wanted: their profile address, or their full name, with no search for the person first.

authorCompanystring

Only posts by people who work at this company now.

authorTitlestring

The role of the people whose posts are wanted. It steers the search; each post's authorHeadline shows the role its author states.

authorLocationstring

Only posts by people based in this country or city.

limitinteger

Target number of posts.

sincestring

Only posts published on or after this date, as YYYY-MM-DD. Omitted, the last 30 days, or every date for one named author; pass an earlier date for older posts.

untilstring

Only posts published on or before this date, as YYYY-MM-DD.

sentencestring

The person's own words for the posts they want. query is still needed beside it: the posts found are checked against it.

includeTextstring

A short phrase the posts should contain, other than the words of query. Not with author or authorCompany.

excludeTextstring

A short phrase the posts should not contain.

moreboolean

Continue past what an earlier call on this same ask already returned, instead of returning it again. What counts as already returned is kept server side.

commentersboolean

Also return the people who commented on each post: name, profile link and what they wrote.

save'keep' | 'skip'

keep (the default) saves the people who wrote the posts into the list; skip only when the posts are a step toward something else.

Response

Matched posts

source'public' required

creditsUsedinteger required

Credits this call spent, net of anything given back. 0 when nothing was charged: a free read, a cached answer, nothing delivered.

providerstring required

The lane that answered.

querystring nullable required

The topic that was searched, so a thin result set can be read rather than guessed at. Null when only who posted was asked.

savedinteger nullable

How many post authors this call wrote to the contact list. Absent when the write did not answer.

pooledinteger

How many of those authors were linked into the list.

moreAvailableboolean required

Whether asking again with more can still reach rows you have not seen. False means this ask is walked out; say so and do not call more again.

duplicatesinteger

Rows a continuation re-reached and dropped as already delivered. Normal bookkeeping, never a failure.

notestring

Present only when nobody posts about this topic and the answer is deliberately empty. Report it as a topic with no posts, not as a failure, and do not ask again for more.

returnedinteger

When who posted was asked: the posts the search found before each author was checked.

keptinteger

When who posted was asked: of those, the posts whose author is who was asked for.

authorNotestring

When who posted was asked: how many posts the author check kept, and on what. Relay it.

Changes

Oct 22, 2026549f4adbbfcf Revision changes
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  the response's body type changed from object to no type for status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- breaking
  removed the required property from the response with the status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added subschema #1 subschema #2 to the response body anyOf list for the response status
- info
  added the required property to the response with the status
Oct 22, 2026f591efe431c1 Revision changes
- info
  added the optional property // to the response with the status

Operation history (11 revisions)