public

Find people to contact because something just happened at their company

Changed on Oct 22, 2026

Two steps from public data. mode events returns dated events (a raise, an appointment, a job opening) for a description of the event, each with its title, date, source page and an id. mode resolve takes companies read in those events, each with a role to reach or the person the event names, and returns the company's LinkedIn page and the people found, each with their profile and the event. A company whose page is not found returns nobody. Events and people already returned never come back; an events ask with includeText keeps its own record, so it can return an event a wider ask already gave. The people found are saved to the list unless save is skip. Each event carries its date; the people come from our index, about 3 weeks old at the median, so a recent job move can be missing. Cost: each search costs by the results it brings back: 4 credits for up to 10, 11 for 25, 49 for 100; in mode resolve, each company costs its searches plus 1 credit for every 2 profiles read, and nothing when nobody comes back. creditsUsed says what the call spent.

post/public/signals

Request

Base URL: https://api.bereach.ai
URL: https://api.bereach.ai/public/signals
Auth: HTTP bearer

Request body

mode'events' | 'resolve' required

events finds dated events; resolve turns companies read in those events into people, each with their company's page.

descriptionstring

events: the event as a headline or a job posting would state it.

kind'news' | 'any'

events: news for raises and appointments; any for every kind of page, job postings included.

sincestring

events: only events published on or after this date, as YYYY-MM-DD. Omitted, the last 30 days.

includeTextstring

events: a phrase of at most five words every page must contain, other than the words of description.

limitinteger

events: how many events to return.

save'keep' | 'skip'

resolve: keep (the default) saves the people found into the list; skip only when they are a step toward something else.

Response

Dated events, or the people they lead to

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.

mode'events' | 'resolve' required

alreadyReturnedinteger

events: events this search found again that were already returned, left out. Normal bookkeeping, never a failure.

savedinteger nullable

resolve: how many people this call wrote to the contact list. Null when that write failed.

pooledinteger

resolve: how many were linked into the list.

notestring

events: present when no new event was found, and says why. 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, 202655b30b093819 Revision changes
- info
  added the new optional request property

Operation history (3 revisions)