CampaignStack
Bring your own API keys for email sending and enrichment: which tools allow it and why it matters

Bring your own API keys for email sending and enrichment: which tools allow it and why it matters

CampaignStack9 min read

"Bring your own key" means you connect accounts you already own, instead of buying the same thing again through your outreach tool. For outreach that covers two things. Sending: your emails go out from your own mailboxes on your own domain. Enrichment: emails and phone numbers are looked up with your own account at a data provider (Apollo, for example), billed by that provider, not resold as the tool's credits.

It matters for two reasons. Cost: you pay the provider once, at the rate on your own plan, and you keep the account if you switch tools. Deliverability: your domain's reputation is built by your own mail. The servers your mail leaves from are shared in every setup. Who you share them with is what changes.

We checked every vendor claim below on the vendor's own pages on October 26, 2026. We make CampaignStack and say where it fits at the end.

Sending: your mailbox, or theirs?

Every cold email tool sends from some mailbox. The question is whose servers carry the mail and whose reputation it rides on.

Google says it plainly in its sender guidelines: "The activity of any senders using a shared IP address affects the reputation of all senders for that shared IP address." It also warns that "over time, user spam reports can lower your domain's reputation," and asks senders to keep spam rates "below 0.10%" and never reach "0.30% or higher".

Shared servers are part of every setup. Mail from a Google Workspace mailbox leaves from Google's servers, the same ones that carry everyone else's Gmail, and Microsoft 365 works the same way. What you own is the domain. Connect your own mailbox and the mail goes out from your domain, so that domain's reputation reflects your sending and nobody else's. When a tool relays mail through its own servers, you share those servers with the tool's other customers, and what they send affects the IPs your mail goes out on.

What the main tools document:

  • Instantly connects Google mailboxes by Google sign-in (OAuth) for Workspace or an app password for personal Gmail, Microsoft by sign-in, and any other provider over IMAP and SMTP, the standard protocols for reading and sending mail. It needs both: "It's not permitted to connect email accounts with only SMTP." Its pricing page says you can "connect and warm as many accounts as you need from any provider."
  • Smartlead has two modes. With "Smartlead's Infrastructure", "Smartlead's servers relay your emails." With "Your Email Network" (formerly "Your Private Infrastructure", on the Smart and Prime plans), mail goes through "your private OAuth credentials".
  • lemlist connects Google and Microsoft with "one-click OAuth" and other providers over IMAP/SMTP. It does not support relay services such as SendGrid, Mailgun, Amazon SES or Postmark.

Enrichment: your key, or their credits?

This is where costs pile up quietly. A tool that resells data charges its own credits per email found. If you also pay Apollo or another provider directly, you can end up paying twice for the same kind of lookup.

  • Clay lets you plug in your own keys. Its pricing page lists "Bring your own API key" on every plan, Free included, while its help article says it is for paid plans, so check yours. The pricing page: "Each run will count as one Action, but no Data Credit will be used." Its help docs list OpenAI, Anthropic, Apollo, email finders like Findymail and Prospeo, and verifiers like Debounce and NeverBounce.
  • One catch with Clay: its own key is selected by default, so you pick yours when you set up the enrichment. And Clay says AI runs on its own keys are about twice as fast, because of the rate limits it negotiated. That's a fair point in Clay's favor.
  • Apollo, when you call it with your own API key, charges "only if credit-consuming data is found". Its docs put one person's enrichment at 1 to 9 credits without waterfall enrichment, and "0 credits" when nothing is found.
  • Instantly sells lead data through its own credit bundles ("Database of 450M+ B2B Leads"). That is Instantly's data, not a key you bring.

Who pays the data provider: with your own key you pay the provider directly and the tool charges no data credits for the lookup; with the tool's credits the tool buys the data and resells it per lookupWho pays the data provider: with your own key you pay the provider directly and the tool charges no data credits for the lookup; with the tool's credits the tool buys the data and resells it per lookup

Sending and enrichment, side by side

Tool Send from your own mailbox Enrich with your own provider key
Instantly Yes: Google, Microsoft, any IMAP/SMTP provider (both protocols required) Not stated on the pages we read; its lead data is sold as Instantly credits
Smartlead Yes, in "Your Email Network" (Smart and Prime plans); otherwise Smartlead's servers relay Not stated on the pages we read
lemlist Yes: Google and Microsoft OAuth, IMAP/SMTP; relay services not supported Not stated on the pages we read
Clay Not a sending tool Yes; one Action per run, no Data Credit (plan rules differ between its pricing page and its help docs)
CampaignStack Yes: Gmail and Google Workspace only Yes: Apollo and Instantly keys, 0 CampaignStack credits per lookup

"Not stated" means the vendor pages we checked on October 26 didn't say either way. It doesn't mean the feature is missing.

What bringing your own keys costs you in work

Keys are not free of effort.

  1. You open an account with Apollo or another provider yourself, pick a plan, and watch its credit balance.
  2. You buy the domains and mailboxes, then set up SPF and DKIM. Past 5,000 messages a day to Gmail, Google also requires DMARC and one-click unsubscribe.
  3. You respect the limits. A Google Workspace user can send 2,000 messages a day, 500 on a trial. Go over and Google says "users can't send new messages for up to 24 hours."
  4. You keep the keys safe. An API key is a password. Rotate it when someone leaves.

For an agency, that work is worth it. The mailboxes and the provider account stay with you (or with your client) when a tool changes. And your domain's reputation is built by your own campaigns, not by another customer's.

A cost example in credits

Arithmetic, not a customer result. Say you need emails for 500 leads, and 300 of them can be found.

  • With a resold finder at CampaignStack's Contact Finder price (10 credits per email found, nothing when nothing is found): 300 x 10 = 3,000 credits.
  • With your own Apollo key inside CampaignStack: 0 CampaignStack credits. You pay Apollo instead, at the rate on your own Apollo plan.

Which one is cheaper depends on your Apollo plan and how much of it you already pay for and don't use. That's the point of bringing your own key: you get to choose.

A contact step set up with your own keys first: Apollo on your key, then Instantly on your key, then the CampaignStack Contact Finder only for the leads both missed, stopping at the first one that finds an emailA contact step set up with your own keys first: Apollo on your key, then Instantly on your key, then the CampaignStack Contact Finder only for the leads both missed, stopping at the first one that finds an email

How CampaignStack handles your keys

CampaignStack runs LinkedIn and email outreach in one workflow, on accounts you already own.

  • Your own mailbox. You connect Gmail or Google Workspace with Google sign-in. Mail goes out through Google's servers, from your address, so the domain reputation is yours. CampaignStack plans each day below Google's ceiling: after 90 days a Workspace mailbox tops out at 1,600 a day and a personal Gmail at 400. New mailboxes start lower and grow by at most 25% a day.
  • Your own data keys. Connect Apollo or Instantly with an API key. A lookup through them costs 0 CampaignStack credits.
  • A finder for when you have no key. The built-in Contact Finder costs 10 credits per email and 50 per phone it finds. Credits held for a miss come back.
  • Your order. The contact step tries the providers you add, top to bottom, and stops at the first that finds an email. Put your own keys first and the Contact Finder last, and you only pay credits for the emails your keys missed. Or remove the finder and spend only your own keys.
  • Your CRM. HubSpot connects with a private app key (in Beta) to sync contacts.

What it doesn't do, so you can rule it out fast: no SMTP sending, no Outlook or Microsoft 365 mailboxes, no Smartlead or lemlist connection, and no slot for your own AI model key.

Sending reputation: with your own mailbox, your domain's reputation is built by your own mail; with a shared relay, many senders share one pool of IPs, and Google says each sender's activity affects all of themSending reputation: with your own mailbox, your domain's reputation is built by your own mail; with a shared relay, many senders share one pool of IPs, and Google says each sender's activity affects all of them

What to watch out for

  • Check that your key is really the one used. Clay, for one, keeps its own key selected until you switch. Run one test row and check the provider's usage page.
  • Rate limits move with the key. Your own key gets your provider's limits, so big runs can slow down.
  • As many mailboxes as you like doesn't mean as much sending as you like. Each mailbox still has the provider's daily limit, and every mailbox you add needs its own DNS setup and warm-up.
  • Read the data terms. When you look up personal data with your own key, your contract with that provider applies. Make sure it covers the countries you prospect in.

Takeaway

Send from mailboxes you own, on a domain you own, and enrich with provider accounts you already pay for. Then pick the outreach tool that connects to them, instead of the one that resells them.

Sources

  1. docs.apollo.io/reference/people-enrichment
  2. help.instantly.ai/en/articles/6222224-how-do-i-connect-my-accounts-to-instantly
  3. help.lemlist.com/en/articles/4536030-connect-your-email-provider-to-lemlist
  4. helpcenter.smartlead.ai/en/articles/446-how-to-connect-your-mailbox-to-smartlead
  5. instantly.ai/pricing
  6. knowledge.workspace.google.com/admin/gmail/gmail-sending-limits-in-google-worksp
  7. support.google.com/a/answer/166852
  8. support.google.com/a/answer/81126
  9. university.clay.com/docs/clay-credit-conservation
  10. clay.com/pricing