Your team has an API key. You use it to authenticate calls to the businesscards.io API, including the Zapier integration and any custom script or backend you build. The key is per-team, not per-user.
Who can see the key
Only team owners. Regular members can't see or generate API keys. The API itself requires a plan that includes integrations (Team and above).
Where to find it
- Sign in to businesscards.io.
- Open Settings → Integrations.
- Look for the API key section.
- Click Reveal to show the key, or click Copy to copy it to your clipboard.
Treat the key like a password. Anyone with it can read and write data on your team. Don't paste it into public code, GitHub repos, or chat logs.
What you can do with it
The API key authenticates requests to our Zapier-compatible API. Endpoints include:
/api/v1/zapier/cards — list and create cards on the team./api/v1/zapier/cards/:id/contacts — list contacts captured on a given card./api/v1/zapier/subscriptions — subscribe and unsubscribe webhooks for new-contact events./api/v1/zapier/user — verify the key and view the team it belongs to.
Pass the key as a header: Authorization: Bearer YOUR_KEY.
Refreshing the key
If a key is exposed (committed to a public repo, leaked in a Slack channel, anything like that), refresh it immediately.
- Open Settings → Integrations.
- Click Refresh API key.
- Confirm.
The old key stops working as soon as the new one is generated. Update any integration using the key (Zapier, custom scripts, your CRM) with the new value.
Connecting to Zapier
Zapier uses the API key under the hood. See connecting businesscards.io to Zapier for the full setup.