Get Started
The RocketReach API allows you to programatically search & lookup contact info over 700 million professionals, and 35 million companies. We constantly work on improving functionality and accuracy of our data. RocketReach is free to try for individual use.
To get started, signup for a free account and create your own API Key absolutely free.
For all calls to the RocketReach API, you will need the an API key. Your unique API key is
Try it Out!
Before we get any further, lets try a quick example.
E.g. To get Mark Benioff's contact info, you can call the /lookupProfile
endpoint …
Base URL
All URLs referenced in the documentation have the following base:
The RocketReach API is served over HTTPS. Unencrypted HTTP is currently supported, but highly discouraged, and maybe deprecated in the future.
Authentication
All API calls require an API key.
I.e when using your API key, your calls will always look as follows.
Your API key must be kept secret, and never exposed in publicly exposed source code, (or used directly in HTML/javascript within a browser). Anyone with access to your API key can make API calls on your behalf. If your API key has been compromised, please regenrate a new API key by going to the API section of your account page.
Need Help?
Need help? Have feedback/questions about usage, pricing? Talk to us live or Email us: sales@rocketreach.co
Authentication
Your API key is:
Request Header (Preferred Method)
Callers may specify their API Key in the Api-Key
request header.
Request Body
API Requests with a request body can include the API Key in the body.
Query Parameter (Least Preferred)
Callers may specify the api_key
query parameter to any of
the API endpoints to authenticate
For example: GET api.rocketreach.co/api/v2/account?api_key=
- Webhooks
- Setting Up a Webhook
- Options for Created Webhook URLs
- Using Webhook-Enabled Endpoints
- Errors
Webhooks
For the lookupProfile
endpoint, we offer a webhook solution so that users do not need to poll the checkStatus
endpoint until their results are available.
Setting Up a Webhook
To set up a webhook, go to your API settings. Enter your server's callback URL into the field, and hit "Create".
Options for Created Webhook URLs
For each URL created, you can perform some basic maintenance tasks:
- Test the webhook - we will attempt to send a basic JSON payload to the URL.
- Disable/enable - if you may use this URL in the future, this is an option to termporarily disable it.
- Delete - if you no longer plan using this URL, it can be deleted.
Using Webhook-Enabled Endpoints
Currently, only lookupProfile
has webhook functionality, but we anticipate supporting more in the future!
Once you call a webhook-enabled endpoint with a webhook set up in your settings, we will send back results to the provided URL.
The results returned to you should look the same as if they were queried through the REST API. In addition, the API will still respond to your REST call as normal.
Errors
If any errors occur, they will show up in the API settings page in the "Web Hook" section.
If the callback to the provided URL is unsuccessful after several attempts, the URL will be marked as disabled.
Handling Errors
Normal responses are returned with HTTP status HTTP: 200
. Error responses return HTTP: 4xx/5xx
error codes.
E.g If the profile being searched for cannot be found, we will return a 404
.
Rate Limits (HTTP:429)
If we start receiving unusually heavy call volumes on your API key,
you may receive responses with HTTP: 429 "Too Many Requests"
more than 5 calls per second
using your API key.
There are two possible solutions to this.
- If you are not on a paid plan, you will generally need to upgrade to a paid API plan. Please email sales@rocketreach.co and we can set you up with an API plan.
- If you are already on a paid API plan, please slow down and retry your requests. If you're still seeing this, please email sales@rocketreach.co or contact our live support.
You can visit the account page to review your RocketReach API limits and daily usage
In general calls to all end points are rate limited to protect against abuse/attacks. However calls to /checkStatus
do not count against your daily rate limits.
Out of Credits
If you have hit some sort of rate limit, you'll see a HTTP: 429
.
But, if you are out of credits, you will see a HTTP: 403
.
- Free plans are allowed a limited number of lookups per month, and this error is most commonly returned to free plans.
- Because paid plans are allowed to exceed their allocation, you are unlikely to encounter this error. However, if you do, check that overages are enabled, and then contact sales@rocketreach.co to set you up with an API plan.
- Lookup Contact Information for a Prospect
- Lookup Profile Examples
- A Deeper Look
- Example: Lookup Profile by 'name' and 'current_employer'
- Example: Lookup Profile by LinkedIn URL
- Parameters
- Response
- Troubleshooting
Lookup Contact Information for a Prospect
The /lookupProfile
API is used to lookup contact information for a prospect(profile).
You can identify the profile using parameters like name, current employer, LinkedIn URL, or profile id (returned
from /search).
The call is pretty straightforward – you provide information about the person you are looking for
i.e name, employer etc. and RocketReach searches for a person matching this information.
Lookup Profile Examples
Let's try some simple examples. Say you want to lookup contact info for Mark Benioff, who works at Salesforce. You
can perform a lookup with either:
LinkedIn URL:
ID:
Company:
A Deeper Look
Most of the time, the contact info will be returned immediately, along with "status":"complete"
or
"status":"failed"
.
However, in certain cases, the lookup can take longer.
If the system is busy doing a lookup, the
call to /lookupProfile
will return "status:
as
"waiting","searching" or "progress"
. In these cases, there are two options:
set up a webhook URL in your API settings, or
poll the /checkStatus endpoint
till the status changes to "complete"
or "failed"
.
Using a webhook is the preferred method.
When polling /checkStatus, please make sure that your rate limit does not exceed one call/second.
A detailed flowchart for this webservice call, is shown below.
Example: Lookup Profile by 'name' and 'current_employer'
This example shows you how to lookup information for a person using name & current employer.
Example: Lookup Profile by LinkedIn URL
This example shows you how to lookup information for a person using their Linkedln URL.
Parameters
This enpoint accepts the following parameters.
Name | Description | Schema | Example(s) |
---|---|---|---|
api_key | User's API Key | string | "3eakf968a47fc8c8eb189cfe66708eac709c" |
name | Name of the person you are looking for | string | "Marc Benioff" |
current_employer | Current employer name | string | "Salesforce", "Google" |
title | Job Title | string | "CEO", "VP of Marketing" |
li_url | LinkedIn URL | string | "https://www.linkedin.com/in/marcbenioff" |
id | RocketReach specific Id of the person you are looking for (see /search ) | string | "5244" |
Email address of the person you're looking for | string | "mbenioff@salesforce.com" | |
webhook_id | If using webhooks, submitting a webhook ID allows you to specify a different URL that is not the default | integer | 1024 |
lookup_type | Can be 'standard' or 'premium'. 'standard' is the default, and 'premium' is usually not needed unless you have multiple lookup types available in your plan. | string | "premium" |
Response
A typical response to this endpoint will look as follows:Troubleshooting
Multiple Matches
In certain cases, you may find that the lookup returns multiple matches. In such cases,
you can select one of the matching profiles, and then
call /lookupProfile
again, with a specific Id.
You can then call lookupProfile
using the right Id:
Results Don't Contain ID
There are a couple possible reasons why IDs might not be showing up in your results:
- using the wrong endpoint - /search does not return IDs
- multiple profiles were returned, and some of them did not come with IDs
- Lookup Company Information
- Lookup Company Examples
- Example: Lookup Company by Domain
- Example: Lookup Company by Name
- Example: Lookup Company by LinkedIn URL
- Example: Lookup Company by Ticker
- Parameters
- Response
Lookup Company Information
The /lookupCompany
API is used to lookup metadata information for an account(company).
You can identify the company using domain, name, or LinkedIn URL.
The call is pretty straightforward – you provide information about the company you are looking for
and RocketReach searches for a company matching this information.
Company exports are required for this endpoint. Talk to sales@rocketreach.co to purchase access.
Example: Lookup Company by Domain
Lookup company information by company domain.
Example: Lookup Company by Name
Lookup company information by company name.
Example: Lookup Company by LinkedIn URL
Lookup company information by company LinkedIn.
Example: Lookup Company by Ticker
Lookup company information by company stock ticker.
Parameters
This enpoint accepts the following parameters.
Name | Description | Schema | Example(s) |
---|---|---|---|
api_key | User's API Key | string | "3e7k0123456789abcdef0123456789abcdef" |
name | Company's name | string | "RocketReach" |
domain | Company's Domain | string | "rocketreach.co" |
linkedin_url | Company's LinkedIn URL | string | "https://www.linkedin.com/company/rocketreach.co" |
ticker | Company's Stock Ticker | string | "GE" |
Response
A typical response to this endpoint will look as follows:- Changing to Webhook Usage
- Checking the Status of Active Lookups
- Example Usage
- Rate Limits
- Parameters
- Response
Changing to Webhook Usage
Moving forward, we would like to encourage our API users to work with webhooks instead of the checkStatus endpoint. This way, you will no longer need to poll this endpoint repeatedly, and we can send you the data as it becomes available.
Checking the Status of Active Lookups
The /checkStatus
API call is used, primarily, to poll the status of active lookups initiated by the
/lookupProfile
endpoint.
When you make a call to /lookupProfile
, the response can contain one of the following 5 values:
"complete"
or "failed"
, the client must poll this endpoint till it returns
either "complete"
or "failed"
.
Example Usage
Assume that you made a call to lookup contact info for 'Mark Benioff' and the response was
You can now poll the status for this profile by calling:
Which in turn will initially return:
And after a while... will return status:"complete"
, along with the complete data.
You can also club together multiple profile Ids
in one call. E.g.
Rate Limits
Calls to this endpoint do not count against your daily rate
limits.
However, calling it too aggressively, at rates higher than once per second, may trigger HTTP 429
Parameters
Name | Description | Schema | Example |
---|---|---|---|
api_key | User's API Key | string | "3eakf968a47fc8c8eb189cfe66708eac709c" |
ids | Comma separated list of profile Ids, for which you need the status returned. | string | "5244,1234,5678" |
Response
A typical response to this endpoint will look as follows:- Search for Prospects
- Search Quickstart
- Retrieving Contact Information for Profiles
- Specifying Exact Matches
- Exclude Search Terms
- Specifying Multiple Search Parameters
- Pagination
- Ordering Results
- Request Body
- Response Body
- Errors
- Examples
Note: v2 no longer supports HTTP GETs for the search call
Search for Prospects
The /search
endpoint behaves similarly to the search in our UI. When you provide certain keywords, or facets as inputs,
this endpoint returns a list of people. The result is always a list of possible matches, without any contact info.
You can search by name, keyword, title, company or location, and more. See the full list of search parameters.
Search Quickstart
Lets look at a simple example. In this example, we will search for 'Amit Shanbhag',
who works at 'RocketReach.co',
using his name, company and title.
Retrieving Contact Information for Profiles
A call to /search
does not return contact information in the result.
In order to retrieve contact information for someone in the list,
please make a separate call to /lookupProfile?id=$id
A detailed flowchart for this webservice call, is shown below.
E.g. You may perform a search for Elon Musk like so:
which returns:
You can then make a call to /lookupProfile
to get the contact information for Elon Musk.
Specifying Exact Matches
You can specify exact matches for all your search terms. E.g. The following query matches anyone with 'Marc Benioff' in their name. I.e it will match people named both “Marc Benioff”, “Benioff Marc” and also “Marc Anthony Benioff”. It will also ignore certain typos like “Marck benoiff” etc.
This query matches anyone named 'Marc Benioff'.
This query exact matches anyone with the exact name 'Marc Benioff'. To specify exact matches,
add quotes around your search term
This approach works for all other parameters that accept strings. E.g. If you wish to exact match
people with current employer: “IBM”, you can use the following query. Note that this will exclude people who work e.g. for "IBM UK".
Exclude Search Terms
You can omit results matching any of the search terms listed in the table above.
Prepend exclude_
before the field name to change the field parameter
to exclude all matching documents.
In this specific example, we will return the best results that match
title: 'Software Engineer'
and title: 'Software Developer'
but not title: 'Senior'
or title: 'Sr'
Basically, this should match Software Engineers and Software Developers that don't
have senior anywhere in their job title.
Specifying Multiple Search Parameters
You can specify multiple keywords or titles etc. Our search system will try and find
results that match closest to your query. In this specific example, we will return the
best results that match either title:'Founder'
or title:'CEO'
If you have multiple parameters with multiple values, it’s interpreted as an “AND”
between filters, and “OR” within the filters. E.g.
(Profile.title == "IBM" OR Profile.title == "GOOGLE")
AND
(Profile.title == "Founder" OR Profile.title == "CEO")
Pagination
You can retrieve up to the first 100 results of your search using
start
and page_size
.
If you try to paginate further than this, you will get an error with status code 400
and the following response body.
For performance reasons, searches are truncated after 100 results, so please be sure to stay within the pagination boundaries.
Ordering Results
There is a parameter called order_by
separate of the query, which takes either
popularity
or relevance
, allowing you to sort results.
Request Body
Name | Description | Schema | Minimum | Maximum |
---|---|---|---|---|
query | JSON object containing a query. | object | - | - |
start | The index of the 1st element to return | integer | 1 | 10000 |
page_size | The number of profiles to return | integer | 1 | 100 |
The query inside the search request body contains a list of search terms. Each search term must contain a list of keywords to search against that term. If any of the keywords for a given search term match a profile, it will be included in the results. If multiple filters are specified at least one keyword from each must match a profile.
You can also ensure a search excludes a certain matching phrase by
prefixing the filter with exclude_
(see examples below).
Methods
- POST: Queries are executed by posting to the search endpoint a query body with the request format.
Numbers with Operators
Some fields, such as company_funding
, take strings which are numbers with
mathematical operators. For example, here are some valid values:
- "1000000+"
- "<90000000"
- "1000000>="
- "1000000-90000000"
Normalized Titles
A query should specify at most one of current_title
and normalized_title
.
Normalized titles are a relatively new feature.
They are intended to reduce the space of titles in a reliable way.
As of 2022-04-21, half of person profiles have normalized titles.
The full list of current normalized titles is available
here.
A normalized title must be specified exactly (see below) and will always be matched exactly.
Query Format
Name | Description | Schema | Example |
---|---|---|---|
name | A fuzzy-matched name, or exact if surrounded by quotes | String | "name": ["Marc Benioff"] |
company_domain | Profiles working for companies with the given domain. | String | "company_domain": ["rocketreach.co"] |
company_funding | Profiles working for companies matching the given criteria. The strings are numbers combined with various mathematical operators. | String | "company_funding": ["1000000<", "1000000+"] |
company_industry_tags | Profiles working for companies matching the given criteria. | String | "company_industry_tags": ["SAAS", "Health Care"] |
company_revenue | Profiles working for companies matching the given criteria. The strings are numbers combined with various mathematical operators. | String | "company_revenue": ["<=90000000", "1000000-90000000"] |
company_size | Profiles working for companies matching the given criteria. The strings are numbers combined with various mathematical operators. | String | "company_size": ["100>=", "9000-"] |
company_website_url | Profiles working for companies matching the given criteria. | String | "company_website_url": ["http://rocketreach.co"] |
current_employer | Profiles currently working for the given company. | String | "current_employer": ["Salesforce"] |
current_title | Profiles with the given title. | String | "current_title": ["CEO", "Founder"] |
normalized_title | Profiles with the given normalized title (full list). | String | "normalized_title": ["Chief Executive Officer (CEO)", "Founder"] |
degree | Profiles with the given degree. | String | "degree": ["BA", "MS"] |
keyword | Keyword: Any keywords in a person's profile | String | "keyword": ["Marc Benioff", "Salesforce"] |
location | Location | String | "location": ["San Francisco", "San Francisco Bay Area"] |
major | Profiles with the given major. | String | "major": ["Business", "Computer Science"] |
naics_codes | Profiles working for companies matching the given criteria. The strings are numbers combined with various mathematical operators. | String | "naics_code": ["1111-9000"] |
school | Profiles with the given school. | String | "school":["UC Berkeley"] |
sic_codes | Profiles working for companies matching the given criteria. The strings are numbers combined with various mathematical operators. | String | "naics_code": ["6021, 6022"] |
Response Body
The search response contains pagination metadata, which indicate how many results can be retrieved for this query, as well as a list of profiles that matched the search terms. The search results contain profile metadata, but exclude contact information. The included teaser indicates the email domains and partial phone numbers for any contact information that has already been discovered. Keep in mind that contact information is searched in real-time, so the results may change during a lookup from what is indicated in the teaser.
The profile status
is deprecated and doesn't serve a useful
purpose. It will be removed in future API versions.
Errors
If your JSON is not well formatted you will get an error with status 400
and a brief description of the problem and how to correct it.
For example, the following request is not formatted correctly since JSON does not allow trailing commas.
Please follow the instructions in the response to fix the formatting issue.
Another common error is including a non-existent search term.
The resulting error will explain which fields are invalid.
Examples
Retrieve Account Info
The /account
API allows you to retrieve your account information. The response will
return your basic usage and profile information.
Parameters
Name | Description | Schema |
---|---|---|
api_key | User's API Key | string |
Response
A typical response to this endpoint will look as follows:Intro to Bulk Lookups
The /bulkLookup
API is similar to the /lookupProfile
endpoint, but for
large numbers of simultaneous lookups. This endpoint requires for at least one webhook URL enabled for
this endpoint, or a webhook ID specified. Up to 100 lookups can be performed per batch.
Parameters
This enpoint accepts the following parameters.
Name | Description | Schema | Example(s) |
---|---|---|---|
api_key | User's API Key | string | "3eakf968a47fc8c8eb189cfe66708eac709c" |
queries | A list of lookups to perform. See below for more details. | list | [{"company": "Salesforce", "name": "Marc Benioff"}, {"profile_id": 5254}] |
webhook_id | If using webhooks, submitting a webhook ID allows you to specify a different URL that is not the default | integer | 1024 |
Bulk Lookup Queries
Each query in the queries
list has the following parameters.
For each query, at least one of the following is required:
linkedin_url
profile_id
company
andname
email
(warning: lower success rate than other options)
Name | Description | Schema | Example(s) |
---|---|---|---|
linkedin_url | LinkedIn URL of the desired profile | string | "https://www.linkedin.com/in/marcbenioff" |
id | RocketReach-specific ID of the person you are looking for (see /search ) | integer | 5244 |
current_employer | Employer name | string | "Salesforce", "Google" |
name | Name of the person you are looking for | string | "Marc Benioff" |
Email of the person you are looking for | string | "mbenioff@salesforce.com" |
Response
The response is a list of regular/lookupProfile
responses. For more information
on what a /lookupProfile
response looks like, refer to
the lookupProfile API page.
Example: Lookup contact info by name, company
If you are calling the RocketReach API endpoints directly, you will essentially need to use 2 calls.
First call /lookupProfile
with 3 params api_key
,name
and current_employer
.
If the status
returned by the call is not "complete"
or "failed"
,
then you will need to poll /checkStatus
till it returns either "complete"
or "failed"
.
If the status is "complete"
, then the response will also contain contact info data.
Putting it all together
The following example demonstrates a fully functional application, using the RocketReach API. Here, we lookup contact info of a person, by name and current_employer.
The source code shown below uses the RocketReach Python SDK. We start by calling initializing the client. This checks to make sure that the
api_key
is valid, and that the user has sufficient credits to perform lookups. Under the
covers, the SDK is simply calling the /account
endpoint.
If everything looks good, we now call /lookupProfile
to
lookup contact info. The library also polls /checkStatus
for you, when necessary.
Example: Lookup contact info by LinkedIn URL
This is very similar to the previous example, but calls
/lookupProfile
with the li_url
parameter.
Putting it all together
The following example demonstrates a fully functional application, using the RocketReach API. Here, we lookup contact info of a person, by name and current_employer.
The source code shown below uses the RocketReach Python SDK. We start by calling initializing the client. This checks to make sure that the
api_key
is valid, and that the user has sufficient credits to perform lookups. Under the
covers, the SDK is simply calling the /account
endpoint.
If everything looks good, we now call /lookupProfile
to
lookup contact info. The library also polls /checkStatus
for you, when necessary.
Example: Search Title (role) at Company
If you are calling the RocketReach API endpoints directly, you will essentially need to use 3 calls.
First call the /search
endpoint.
Assuming that the id
for Marc's profile is 5262
, you then call
/lookupProfile
If the status
returned by the call is not "complete"
or "failed"
,
then you will need to poll /checkStatus
till it returns either "complete"
or "failed"
.
Fully functional prototype app
In this example, we will search for people with a specific name and title, at a company. We will then lookup contact info for one of the search results.
Python SDK
The Python SDK allows you to find anyone's emails, social media and complete contact data, using only a few lines of code.
Install the SDK
Install with pip:
Manual installation:
Use one of the installation methods above to install the rocketreach package into your project's virtual environment. The code is now ready to be integrated.
Initialize the SDK
Initialization is the first step to use the SDK. You will need you API key for this step.
Call lookup() or search()
You can call any of our methods once the Gateway
class is constructed.
In this next example we will call lookup()
using a name and current employer. Then, we'll do the
same lookup using a LinkedIn URL.
By default, the lookup method blocks until /checkStatus returns complete. The caller can override this behavior and call lookup in a non-blocking context.
check_status()
can take either a single argument, or an array containing multiple IDs to lookup. Regardless of the number of arguments, the return value will always contain a person collection as an array (with 1 or more elements).
Examples
More detailed examples are listed below.
Reference
Calls are wrapped in a Result object. If the call was successful the Result object will encapsulate the return value.
Result object attributes
Name | Description | Type |
---|---|---|
request | Request object sent to the server. | requests.Request |
response | Response object received from the server. | requests.Response |
is_success | Indicates if the call succeeded. | bool |
data (optional) | Any data retrieved from the server response. | dict |
error (optional) | Any error data retrieved from the server response. Returned if is_success is False |
dict |
message (optional) | A human readable message that explains what went wrong. | str |
Successful results will also contain an attribute containing a Python object representing the returned entity.
Gateway Initialization
Usage
Arguments
Name | Description | Type |
---|---|---|
config | Gateway configuration object. | rocketreach.GatewayConfig |
api_key | User's api key, | str |
Returns
GatewayName | Description | Type |
---|---|---|
person | Access person functions, like lookup, check status and search. | rocketreach.PersonGateway |
account | Access user account functions. | rocketreach.AccountGateway |
Account Information
Usage
Arguments
None
Returns
Returns an Account
within a result object.
Name | Description | Type |
---|---|---|
api_key | User's api key. | str |
api_key_domain | User's api key domain | str |
daily_api_limit | Deprecated | int |
daily_api_num_calls | Deprecated | str |
User's email. | str |
|
first_name | User's first name. | str |
id | User's unique identifier. | int |
last_name | User's last name. | str |
lifetime_api_num_calls | Deprecated | int |
lifetime_credits_spent | Deprecated | int |
lookup_credit_balance | Deprecated | int |
plan | Metadata about the user's current subscription plan. | dict |
state | Either 'registered' or 'test_user' . |
str |
Lookup
Usage
Aguments
Name | Description | Type |
---|---|---|
id | The person's ID to lookup. Use the search result to find IDs. | int |
linkedin_url | The person's linkedin URL (should be the full URL including https://wwww.linkedin.com). | str |
extras | Wrapper for passing other parameters to lookup, such as name or current_employer . |
dict |
block | Indicate whether the call should block until the lookup status is complete. (Default: True ) |
bool |
Returns
Account
Name | Description | Type |
---|---|---|
current_employer | Person's current employer name. | str |
current_personal_email | Best guess at most up-to-date personal email for this contact. | str |
current_title | Person's current job title. | str |
current_work_email | Best guess at most up-to-date work email for this contact. | str |
emails | List of emails for this contact. | list |
id | Person's unique id. | int |
linkedin_url | Person's linkedin url. | str |
links | Social links for this contact. | dict |
location | Person's current location. | str |
name | Person's name. | str |
phones | Phone numbers associated with this contact. | list |
profile_pic | Link to a profile picture associated with this person. | str |
status | The lookup status ('complete', 'progress', 'searching', 'not queued') | str |
Note: by default, the lookup status should be complete, since the lookup
method polls check status and blocks until the lookup is finished.
Search
Usage
search()
returns a search object which can be used to modify the current query. The search object supports filter
and exclude
.
These methods have the same signature and return a copy of the search with the underlying query modified according to the method arguments. Use filter
to match people with a given criteria, or exclude
to remove them from the results.
filter
and exclude
can take multiple parameters in one call, or the calls can be chained together.
You can filter a parameter multiple times to "or" their results together.
Finally, when using exclude
, you dont need to prefix the search parameter with exclude
. The SDK handles this detail for you.
If you are unsure how your search is being interpreted, you can access the query as a dict
.
Arguments
See Search for a comprehensive list of arguments. The argument names will be the same.
Returns
PersonCollection, list of Person objects.
Pagination
Searches will only return 10 results at a time, but the API provides a pagination method that can be accessed through the Python SDK.
The Python SDK provides iterators to handle paginating through results for you. These convenience iterators are accessed through the .iterator()
method.
The search object also supports indexing and slicing to limit the range of results.
Indexing causes the search to be immediately executed with the desired result returned.
Search object slices cannot contain steps.
Ordering
The RocketReach API provides 2 methods for ordering the search results. Results can be ordered by relevance
(default) or popularity
.
- Relevance
- Return results most closely matching the search query.
- Popularity
- Ensure matching decision makers, executives and managers are closer to the top of the search results when they match the search criteria.
RocketReach Data
How Do I Know if RocketReach Has Data For a Profile?
- 87% of lookups return profiles
- "teaser" in search returns some indication of data; however, the final lookup may discover results even if the teaser is empty
- if no data is found, credits are not deducted
Do I Get Charged a Credit if No Data is Returned?
- for lookups, no
- searches are metered, but usually the first ~10,000/day are free on paid API plans
Data in a Profile Doesn't Match Data From the API
- this should almost never happen, please contact support
- on the other hand, search results and sorting may be different depending on how the search is executed
- the UI uses NLP for search facets and may have misinterpreted TODO: text for description on this incomplete
Search Results in the UI Don't Match Data From the API
- search results and sorting may be differen depending on how the search is executed
- this also uses NLP for search facets
- try changing the facet and adjusting the sorting param
I Searched for X in the UI, and Found it, but the API Doesn't Return the Same Results
- similar to above, and reach out to support if you need further assistance
The Teaser Doesn't Contain Emails, Only Phone Numbers
- teaser information is only populated if data is cached
I'm Getting Rate-Limited?
- rate limits depend on product, contact us to get on an API plan