Docs

User Guide

User Guide / People

Adding Provider Keys

Rox allows Enterprise customers to supply their own API keys instead of using Rox’s shared keys. This lets your organization use its own provider agreements, manage usage and quotas independently, and keep enrichment running even if shared-key capacity is constrained. This feature is available on Enterprise plans only — self-serve accounts cannot add provider keys (except for HG Insights).

Adding a Key

There are two ways to add a provider key. Both methods store the key at the organization level, making it available to all users and all future enrichment columns that use the same provider.

Method 1: Via an Enrichment Column

  • Open or create an enrichment column for a provider that supports custom keys (e.g., Find Work Email using Hunter).

  • In the column configuration panel, locate the key input field for that provider and enter your API key.

  • Save the configuration. The key is automatically stored in your organization’s settings and will be available for any future enrichment column that uses the same provider.

Method 2: Via Organization Settings

  • Navigate to Settings from the main navigation.

  • Locate the Enrichment Provider Keys section and find the provider you want to configure.

  • Enter your API key and save. The key is immediately available for selection in any enrichment column that uses that provider.

Using a Stored Key for Enrichments

Once a provider key has been stored (via either method above), it is available across all enrichment columns in your organization. When adding or configuring an enrichment column for that provider, you will see a toggle or selector indicating that a connected key is available. Click it to activate your key for that column - the column will then use your organization’s key rather than Rox’s shared key. The stored key is shown as “connected” once selected.

Self-serve users can add keys for HG Insights only, following the instructions above.
Enterprise users can add keys for all supported providers listed in Rox, with the exception of HG Insights.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.

Rox is committed to the privacy and security of its users. Customer data processed through the Rox platform is encrypted in transit and at rest using AES-256 encryption and is never used to train generalized machine learning models. Rox maintains SOC 2 Type II compliance and undergoes independent third-party security audits on an annual basis. All AI-generated outputs, including but not limited to prospect recommendations, message drafts, meeting summaries, and pipeline scoring, are provided for informational purposes and should be reviewed by authorized personnel before any action is taken. Performance metrics referenced on this website, including pipeline generation figures, response rates, and revenue impact, reflect results reported by individual customers under specific configurations and may not be representative of all deployments. Actual results will vary based on factors including but not limited to data quality, CRM configuration, outreach volume, market conditions, and target audience. Rox does not guarantee specific revenue outcomes. The Rox platform integrates with third-party services including Salesforce, HubSpot, Gmail, Microsoft Outlook, Slack, and others; availability and functionality of third-party integrations are subject to the respective providers' terms of service and may change without notice. Features described as "autopilot," "autonomous," or "automated" operate within user-defined parameters and require initial configuration and ongoing oversight. Rox, the Rox logo, and "Revenue on Autopilot" are trademarks of Rox Data Corp. All other trademarks are the property of their respective owners. Service availability is subject to the terms outlined in your enterprise agreement. For questions regarding data processing, compliance certifications, or platform capabilities, contact security@rox.com.