RocketReach

RocketReach

This connector calls the RocketReach API v2 (https://api.rocketreach.co/api/v2) with the user's own API key: account and credits, people and company search, person lookup with its status check, and company lookup.

Personal data: B2B use only. Person lookups return real people's work and personal email addresses and phone numbers. Use them only for a legitimate business purpose the user can justify (for example B2B sales or recruiting under legitimate interest), in line with the GDPR, CAN-SPAM and similar laws, and with RocketReach's terms. Keep only what is needed, prefer professional emails for business outreach, and never pull contact data in bulk or build a mass mailing list. Do not look up private individuals.

Credits: search first, look up only what the user picked.

• Free: rocketreach_get_account, rocketreach_search_people, rocketreach_search_companies (searches return no contact data and spend no lookup credits; they count against the search rate limits), and rocketreach_check_lookup_status.
• Costs credits: rocketreach_lookup_person spends a lookup credit and a person export credit when contact data is found (premium when an A or A- email or a valid phone is found, standard for an email only); no data found, no charge; looking up the same person again later is free while the plan is active. rocketreach_lookup_company spends a company export credit. Both add the record to the account's My Contacts or My Companies list. Before a lookup, show the user who you will look up and that it costs credits, and wait for their yes. rocketreach_get_account shows what is left (credit_usage).

Setup (about 2 minutes)

1. Sign in at https://rocketreach.co with an account that has API access (an API plan, or a plan with API calls).
2. Open Account Settings, API (https://rocketreach.co/account?section=nav_gen_api) and choose Generate New API Key (or copy the existing one).
3. Paste it into ROCKETREACH_API_KEY. It is sent as the Api-Key header and only to api.rocketreach.co.

Workflow

1. rocketreach_search_people or rocketreach_search_companies with a query of facets. Results carry the RocketReach id and a teaser (email domains and masked phones) that hints whether a lookup will find something.
2. After the user confirms, rocketreach_lookup_person with the id (or a LinkedIn URL, an email, or name plus current employer). A lookup often returns status progress or searching first: wait a few seconds and call rocketreach_check_lookup_status with the id (free) until status is complete or failed. Do not poll faster than every 3 seconds.
3. rocketreach_lookup_company for a full company profile by domain, id, name, ticker or LinkedIn URL.

Searching: facets take lists of strings, e.g. {"current_title": ["CFO"], "geo": ["Germany"], "company_size": ["201-500"]}. Wrap a value in double quotes inside the string for an exact match: ["\"IBM\""] matches IBM but not IBM UK. Exclude with exclude_<facet>, e.g. exclude_current_employer. Pages hold up to 100 records and a query reaches at most 10,000; pagination.next is the start of the next people page, pagination.nextPage the start of the next company page.

Rate limits: 10 requests a second across the API, plus per-minute, hourly, daily and monthly caps for search and lookup by plan (rate_limits in rocketreach_get_account). A 429 carries Retry-After in seconds; wait that long.

Common errors (detail in the body)

• 401 authentication_failed: the API key is wrong or missing.
• 403: the key lacks permission for this call, the lookup credits are used up ("insufficient credits"), the plan has no company lookups, or the status check asked for a profile that is not in your contacts.
• 400: a parameter or facet is invalid.
• 404: no such profile or company.
• 429: rate limit; wait for Retry-After.

Accounts on Universal Credits: RocketReach is moving some customers to Universal Credits, which use separate /universal/... endpoints and price searches per page. This connector uses the standard endpoints; if calls fail on a Universal Credits account, ask RocketReach ([email protected]) which endpoints the account can use.

Out of scope here: bulk lookup (results arrive only through a webhook), person and company lookup in one call, email verification, Universal Credits endpoints, webhooks and API key rotation.