# Events

People posting about a conference.

In the API this is the signal type `events` (Posts about an event). You run it with the same route as every signal: a search.

## What it finds

People who post about a conference or event, and/or who react to those posts. The event is not looked up and no AI is used: the search reads the posts that use the event name you send or one of its hashtags and, with organizer_linkedin_url, the posts of that page that name the event. Event names are often shared (“HR Tech” is several events), so first find out yourself which event is meant, then send its exact name with the year, its own hashtag, or the organizer’s page.

## Rows and price

- One row per person, as the source shows it, with no AI judging it: you decide which rows fit.
- At most 100 rows per search, 25 unless you send `limit`; more with `cursor`. **1 credit** per row.
- A search that delivers nothing is free.

## The signal object

Send it as `signal` in the body of POST /searches. The other fields of the body are on [Start a search](/docs/api-reference/start-search).

- **`type`** `string` · **required** — event_posts is the old name, accepted until general availability. One of: `events`, `event_posts`.
- **`event`** `object` · **required** — An object with the fields below.
- **`event.name`** `string` · **required** — Searched literally, with the name as a hashtag: send the exact name, with the year.
- **`event.starts_on`** `string | null` — Only for a note when the event is far away or long past.
- **`event.organizer_linkedin_url`** `string | null` — This page's posts that name the event are read too, and the page's staff are left out.
- **`event.hashtags`** `string[]` — Up to 4 of the event's own hashtags, searched next to the name.
- **`leads_from`** `string` — authors = people who wrote a post; reactors = people who reacted to or commented on the busiest posts; both = merged and deduplicated. Defaults to `both`. One of: `authors`, `reactors`, `both`.

## Limits

- Attendee lists are not available: the people are those who post about the event or react to those posts.
- Namesakes are not told apart: every post that uses the name or a hashtag counts.

## Run it

- **Once**: [Start a search](/docs/api-reference/start-search) (`POST /searches`). [Preview a search](/docs/api-reference/preview-search) shows the most it can cost first. The rows are in [List search results](/docs/api-reference/search-results).
- **To follow it**: run the search again, for example every week. There are no watches.
- **From your assistant**: `search_signals` runs it ([MCP](/docs/api-reference/mcp)), on the mySDR connection the assistant signed in to, or on the Signals MCP server with a key.

## Example

A search, `POST /searches`:

```json
{
  "signal": {
    "type": "events",
    "event": {
      "name": "Web Summit 2026",
      "hashtags": [
        "websummit"
      ]
    },
    "leads_from": "both"
  },
  "limit": 25
}
```