← Integration Engineering
Integration Engineering

Never Ask a Customer to Email You Their API Key

15 Oct 2026·3 min read

"Please send us your API key by email." It still happens. The key sits in an inbox, gets forwarded, maybe pasted into a chat. Nobody knows how many copies exist. It is the riskiest step of the whole integration.

How a good connect flow works

  • Your backend creates a short-lived connect session, tied to that customer. Your main API key never reaches the browser.
  • The customer picks their tool and logs in, or pastes their key, on a hosted screen.
  • The credentials go straight into secure storage. Nobody on your team has to handle them.
  • Your app gets back an account ID, and uses that ID for every call after. An account ID alone cannot log in anywhere.

The customer ID must come from the server

When you create the session, you say which customer it belongs to. If your server takes that ID from the browser’s request, any user can change it and attach their connection to another customer. Always read it from your own login session on the server.

Why this wins dealsSecurity reviews ask how you receive customer credentials. "Our staff never see them" passes. "They email them to support" does not.
Do this in 60 secondsSearch your team inbox and chat for "api key". If a customer’s key is sitting in a message, ask them to rotate it and delete the message.
Today’s AI angleAn AI agent should work with account IDs, never raw credentials. The agent says "use account 123", and your server looks up the secret. The server decides which customer the agent acts for, not the model.
Never Ask a Customer to Email You Their API Key · Ali Huzaifa