Find people who have participated in specific events (demo days, conferences, podcasts). All fields except event are optional, allowing flexible queries such as:
- All attendees at an event: Search by event name only
- Company-specific attendees: Filter by company to find which employees attended
- Role-filtered search: Find CTOs, founders, or other roles at specific events
- Location-based: Discover attendees from specific geographic regions
Results are generated asynchronously and provide accurate, current data.
Related Endpoints
Overview
API Endpoint
https://api.nyne.ai/person/events
- Endpoint:
POST /person/events - Delivery: Asynchronous. Receive a
request_idimmediately, then poll or provide a callback URL. - Credits: Charges the
person_eventsaction per completed request. - Freshness: Focuses on recent event attendance.
Authentication
Authenticate each request with your API key and secret:
X-API-Key: your_api_key_hereX-API-Secret: your_api_secret_here
Rate Limits
Person events requests respect your account's configured usage limits:
- Per Minute: 60 requests
- Per Hour: 1000 requests
- Monthly: Varies by plan
Credit Usage
API credits are consumed for each person events search request:
- Events Search: 3 credits per completed request
Credit Efficiency
Credits are charged upon successful completion. If no event attendees are found, the request still consumes credits as the search was performed.
POST /person/events
Queue an event-based person search.
POST /person/events
Request Body
| Field | Type | Required | Description |
|---|---|---|---|
event |
string | required | Public event, conference, podcast, etc. (e.g. "YC Demo Day", "TechCrunch Disrupt"). |
company_name |
string | optional | Filter by company to find employees who attended (e.g. "Google", "Stripe"). |
role |
string | optional | Filter by job title or role (e.g. "Founder", "CTO", "VP Engineering"). |
industry |
string | optional | Filter by industry sector (e.g. "Health Tech", "Fintech", "SaaS"). |
location |
string | optional | Geographic filter for attendees (e.g. "San Francisco", "New York"). |
callback_url |
string | optional | HTTPS endpoint for automatic delivery when results are ready. |
Example Requests
Example 1: All attendees at an event
Example 2: Company-specific attendees
Example 3: Role and industry filters
Example 4: With callback URL
Immediate Response
GET /person/events
Poll for completion or retrieve cached results.
GET /person/events
Query Parameters
request_id(string, required) – identifier returned by the POST call.
Completed Response
Callback Payload
If callback_url is provided, the same JSON payload is POSTed to your endpoint once results are ready.
POST https://example.com/webhooks/person-events
Content-Type: application/json
{
"request_id": "pevents_64f2d8e4_1700000789",
"status": "completed",
"result": {
"people": [
{
"name": "Alex Doe",
"title": "Co-founder",
"company": "HealthPulse",
"linkedin_url": "https://www.linkedin.com/in/alexdoe",
"event": "YC Demo Day Summer 2025"
}
]
},
"created_at": "2025-11-10T22:44:03Z",
"completed_at": "2025-11-10T22:44:35Z"
}
Error Codes
missing_parameters–eventfield is required.invalid_callback_url– Callback URL must be HTTPS.subscription_required– Account lacks search access.rate_limit_exceeded/monthly_limit_exceeded– Usage limits exceeded.insufficient_credits– Account credits depleted.
Next Steps
- Test live requests in the Person Events Playground.
- Explore Person Search and Company Needs for complementary workflows.