Credit cost: 1 export credit per non-empty record returned for contacts already viewed in Radar. Contacts not yet viewed in Radar incur no credits on the initial search query.
Endpoint
POST /api/v1/search/people
Request
Headers
| Header | Value |
|---|---|
X-API-KEY | Your Clodura API key |
Content-Type | application/json |
Body Parameters
Page number for paginated results. Accepted range:
1–100.Number of records to return per page. Maximum:
100.Clodura’s unique identifier for a person. Use this to fetch or re-fetch a specific contact record directly.
First name of the person. Typically combined with
lastName for name-based searches.Last name of the person. Typically combined with
firstName.Standard LinkedIn profile URL for the person (e.g.,
https://www.linkedin.com/in/kapilkhangaonkar/). Sales Navigator URLs are not supported.Filter by job seniority level. Accepted values:
Founder, Chairman, President, CEO, CXO, Vice President, Director, Head, Manager, Senior, Junior, Entry Level, Executive.Job titles to filter by (e.g.,
"marketing manager", "sales rep"). May return approximate matches unless includeSimilarTitles is set to false.When
false, enforces strict matching on personTitle. Defaults to true (approximate matching enabled).Filter by department or business function. Accepted values include:
Admin, Analytics, Engineering, Finance, HR, IT, Marketing, Operations, Product Management, Sales, Security, Support, and more.The person’s current city of residence. Refer to the supported cities list.
The person’s current state of residence. Refer to the supported states list.
The person’s current country of residence. Refer to the supported countries list.
When
true, excludes people in the specified location filters instead of including them.Filter by email verification status. Accepted values:
verified, unverified, unavailable.Clodura’s unique identifier for a company. Use the Search Organizations endpoint to look up this value.
The name of the employer organization. Use
organizationId when possible for more precise matching.One or more employer domain names (e.g.,
google.com, clodura.ai). Do not include www. or @. Maximum 10 domains per request.Filter by headcount range. Accepted values:
0 - 1, 2 - 10, 11 - 50, 51 - 200, 201 - 500, 501 - 1000, 1001 - 5000, 5001 - 10000, 10000+.The company’s headquarters country.
The company’s headquarters state.
The company’s headquarters city.
When
true, includes contacts from all office locations, not just HQ. Defaults to false.When
true, omits contacts you have already viewed or unlocked. Useful for discovering net-new leads. Defaults to false.Filter by industry sector. Refer to the supported industries list.
Keywords related to the industry to refine results further (e.g.,
AI, FinTech, SaaS).Filter by estimated annual company revenue. Accepted values:
< 1M, 1M-10M, 11M-100M, 101M-500M, 501M-1B, 1B+.Filter by funding round type. Accepted values include:
Seed Round, Series A through Series J, Pre Seed Round, Venture Round, Angel Round, Private Equity Round, Post-IPO Equity, and more.Start date for filtering by funding events. Format:
YYYY-MM-DD.End date for filtering by funding events. Format:
YYYY-MM-DD.Filter by company business model. Accepted values:
Product, Services, Solutions.Filter by technologies used by the company. Refer to the supported technologies list.
Keywords found on the company’s website (e.g.,
CRM, automation, cloud).Example Request
Response
A successful200 response returns an array of matching people records.
Clodura’s unique identifier for this person. Use this value with Reveal Email and Reveal Phone.
The person’s first name.
The person’s last name.
URL of the person’s LinkedIn profile.
Seniority levels associated with the person’s current role.
Job title(s) associated with the person.
Department or functional area the person belongs to.
City of the person’s current location.
State of the person’s current location.
Country of the person’s current location.
Verification status of the person’s email address:
verified, unverified, or unavailable.Clodura’s unique identifier for the person’s current employer.
Name of the person’s current employer.
Domain name(s) associated with the employer.
Headcount range for the employer.
Country where the company’s headquarters is located.
The current page number returned.
Number of records returned per page.
Example Response
Webhook Tracking
The Search People API is asynchronous for email and phone reveals. When you submit a request to the Reveal Email or Reveal Phone endpoints, the API immediately returns atrackingId. Use this ID with the GET /api/v1/search/people/track/{trackingId} endpoint to poll for results or have them delivered to your webhookUrl. See Credit Usage to monitor your remaining balance.
Error Codes
| Status | Meaning |
|---|---|
400 | Bad request — check parameter values (e.g., domain count exceeds 10) |
401 | Unauthorized — your API key is missing or invalid |
402 | Payment required — credits exhausted; upgrade your plan or add credits |
403 | Forbidden — this endpoint requires a paid Clodura plan |
404 | No results found — try adjusting your filters |
422 | Unprocessable entity — invalid parameter combination or missing required parent filters |
429 | Rate limit exceeded — slow down requests or upgrade your plan |
