# Person Events

> Retrieve notable life/career events for a person.

- **Endpoint:** `POST https://api.nyne.ai/person/events`
- **Group:** Person APIs (https://api.nyne.ai/documentation/person.md)
- **Auth:** `X-API-Key` + `X-API-Secret` headers
- **Mode:** Asynchronous - submit returns a `request_id` (normally with `202 Accepted`); poll `GET /person/events?request_id=<request_id>` with the same auth headers until the endpoint reports a terminal response. Where supported, a `callback_url` can notify you when queued work finishes; follow this endpoint's retrieval notes.
- **HTML version:** https://api.nyne.ai/documentation/person/events

Event-based contact discovery - finds people linked to a key event (fundraise, conference, product launch, etc.) for timely outreach. `event` is the only required field; the remaining context fields (`company_name`, `location`, `role`, `industry`) narrow the search. The request is queued and returns a `request_id` to poll, or a `callback_url` receives the result.

## Authentication

All `/person/*` and `/company/*` endpoints authenticate with an API key and secret sent as HTTP headers on every request: `X-API-Key` and `X-API-Secret`. Create keys from your Nyne.ai dashboard and keep the secret server-side. Rate limits: 100 requests/minute, 1,000 requests/hour. Full guide: https://api.nyne.ai/documentation/authentication.md

## Parameters

| Name | Type | Required | Description | Example |
| --- | --- | --- | --- | --- |
| `event` | string | **yes** | The event to discover contacts around (e.g. a fundraise, conference, or announcement). Required. | "Series B fundraise" |
| `company_name` | string | no | Narrow to people at this company. | "Acme" |
| `location` | string | no | Narrow by location. | "San Francisco" |
| `role` | string | no | Narrow by job role/title. | "VP Sales" |
| `industry` | string | no | Narrow by industry. | "Fintech" |
| `callback_url` | string | no | If set, the completed result is POSTed here when the job finishes. Must be a valid HTTP(S) URL on an allowed host when a callback allow-list is configured. | "https://hooks.example.com/result" |

## Polling for the result

A newly queued submit normally returns `202 Accepted` with a `request_id`. Poll the same path until `status` is `completed` (results stay available afterwards). Where supported, pass a `callback_url` on the submit to receive a webhook when queued work finishes; keep the documented GET as a recovery and retrieval path:

```bash
curl "https://api.nyne.ai/person/events?request_id=<request_id>" \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "X-API-Secret: YOUR_API_SECRET"
```

## Credit usage

| Item | Credits | Condition |
| --- | --- | --- |
| Events Search | - | Charged upon successful completion |
| No attendees found | - | The search itself is billed: a completed search with no results still consumes credits |

## Responses

| Code | Meaning |
| --- | --- |
| `200` | Status poll result - returns the current request status and result/error fields when available |
| `202` | Request queued - poll the status endpoint (or wait for the callback) with the returned request_id |
| `400` | Malformed JSON, missing required parameters, or an invalid field |
| `401` | Missing or invalid API credentials |
| `402` | insufficient_credits - not enough credits to complete the request |
| `403` | subscription_required or ip_not_allowed |
| `404` | request_not_found - no matching request is available for this API key |
| `429` | rate_limit_exceeded |
| `503` | service_unavailable - the API is temporarily unavailable |

## Example request

### cURL

```bash
curl -X POST https://api.nyne.ai/person/events \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "X-API-Secret: YOUR_API_SECRET" \
  -H "Content-Type: application/json" \
  -d '{
    "event": "Series B fundraise",
    "company_name": "Acme",
    "industry": "Fintech"
  }'
```

### Python

```python
import requests

resp = requests.post(
    "https://api.nyne.ai/person/events",
    headers={
        "X-API-Key": "YOUR_API_KEY",
        "X-API-Secret": "YOUR_API_SECRET",
    },
    json={
        "event": "Series B fundraise",
        "company_name": "Acme",
        "industry": "Fintech",
    },
)
data = resp.json()
print(data)
```

### Node

```javascript
const resp = await fetch("https://api.nyne.ai/person/events", {
  method: "POST",
  headers: {
    "X-API-Key": "YOUR_API_KEY",
    "X-API-Secret": "YOUR_API_SECRET",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    event: "Series B fundraise",
    company_name: "Acme",
    industry: "Fintech",
  }),
});
const data = await resp.json();
console.log(data);
```

### PHP

```php
<?php
$ch = curl_init("https://api.nyne.ai/person/events");
curl_setopt_array($ch, [
  CURLOPT_POST => true,
  CURLOPT_RETURNTRANSFER => true,
  CURLOPT_HTTPHEADER => [
    "X-API-Key: YOUR_API_KEY",
    "X-API-Secret: YOUR_API_SECRET",
    "Content-Type: application/json",
  ],
  CURLOPT_POSTFIELDS => json_encode([
    "event" => "Series B fundraise",
    "company_name" => "Acme",
    "industry" => "Fintech",
  ]),
]);
$data = json_decode(curl_exec($ch), true);
print_r($data);
```

## Example response

```json
{
  "request_id": "a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4_1717000000_4271",
  "status": "completed",
  "completed": true,
  "result": {
    "people": [
      {
        "name": "Jane Doe",
        "title": "Head of Product",
        "company": "Acme",
        "linkedin_url": "https://linkedin.com/in/janedoe",
        "event": "Series B fundraise"
      },
      {
        "name": "John Smith",
        "title": "VP Engineering",
        "company": "Acme",
        "linkedin_url": "https://linkedin.com/in/johnsmith",
        "event": "Series B fundraise"
      }
    ]
  },
  "completed_on": "2026-01-15T10:35:00Z"
}
```

---

All documentation pages are available as Markdown by appending `.md` to their URL. Index: https://api.nyne.ai/llms.txt