Audience
GET /audience
Retrieve a list of developers who have recently interacted with specific technologies in open-source repositories.
🔑 Credits
- Cost: 1 credit per request (only if results are returned)
Parameters
Name | Type | Required | Description |
---|---|---|---|
tech | array | ✅ Yes | A list of technologies to search for (e.g., tensorflow,kubernetes ) |
required_fields | array | ❌ No | Limit results to user profiles that include specific fields. Options include: full_name , company_country , first_name , company_industry , company_linkedin , company_website , linkedin_username , title , country , work_email , company_size , email , company_founded , company_name , last_name , emails |
since | string | ❌ No | Only return results with events after this date (yyyy-mm-dd ) |
types | array | ❌ No | Filter events by type. Options include: commit , created_branch , created_repo , created_tag , delete , forked_repo , issue_comment , issues , pull_request , push , release , star , watch |
next_page | string | ❌ No | Pagination token to retrieve the next page of results |
include_fields | array | ❌ No | By default, profiles returned do not contain repos , commits , issues , and only events matching the tech query are returned. To receive all data for these fields, include them in this parameter e.g., repos,commits |
Example
Find people that have used twilio
Request
Response (First Result)
Paginating through results
Each response returns up to 10 profiles. If more profiles can be fetched for this query, the response will return a field next_page
that can be passed into the api again to return more results. This behavior can be continued until there are no more results remaining.
Example
Make a request
If next_page
exists in the response, use it to pull more results
To receive consistent results, pass the same parameters you passed in the first query. The only parameter you should modify as you paginate through results is the next_page parameter.
Each next_page
token is only valid for 30 seconds.
Data
Total Results
The first request returns a field total
, which is the total number of profiles matching the query
New Fields
Profiles that are returned include the following fields:
Full profile urls:
linkedin_url
: the person’s linkedin urlx_url
: the person’s x urlgithub_url
: the person’s github url
Signals:
signals
: signals you can use to determine the relevancy of the profile.signals.event_types
: a list of ways in which the person has interacted with the queried technologiessignals.matched_terms
: a list of technologies in the query the person has interacted withsignals.number_of_event_types
: the number of ways in which the person has interacted with the queried technologiessignals.ratio_of_matched_events_past_2_years
: the ratio of the person’s interactions over the past 2 years that match the queried technologiessignals.ratio_of_matched_events_past_year
: the ratio of the person’s interactions over the past year that match the queried technologies
Events:
events.match
: whether the event matches the technologies queried. by default, only events matching the queried technologies are included. To include all events for profiles returned, includeevents
in theinclude_fields
parameterevents.matched_terms
: technologies in the query the match the event
Examples
People who have interacted with twilio
People who have interacted with twilio or sendgrid
People who have interacted with twilio or sendgrid in 2025
People who have interacted with twilio or sendgrid in 2025, who have a linkedin
People who have interacted with twilio or sendgrid in 2025, who have a linkedin and an email
People who have interacted with twilio. Include all data on their repos, commits, issues, and events