Integration guide
Connect your systems in three steps
For company administrators. No coding needed on your side: you create a key and hand it to your IT team, software vendor or AI assistant.
Available in the Enterprise plan. See plans
What you can do
- HR system: a card opens automatically when someone joins and closes when they leave.
- Intranet, directory or CRM: shows your cards and the leads that come in through them.
- AI assistant: you ask "open a card for our new sales manager" and it does it with your permission.
Step 1: Create a key
- In the panel, open API Keys (only company administrators see it).
- Name the key after the system that will use it, for example "HR system".
- Choose only the scopes that system needs (table below). You can set an expiry date; one year is a good default.
- Copy the key right away: it is shown only once.
| Scope | Choose it when |
|---|---|
| Read cards | When an intranet, directory or CRM shows your cards. |
| Create and update cards | When your HR system opens cards on joining and closes them on leaving. |
| Read leads | When leads from card forms go to your CRM or sales team. |
Step 2: Hand it over safely
- Share the key through a password manager or a one-time secure channel, not in plain email or chat.
- Send your IT team or vendor the developer page; everything they need is there. Developer page
Step 3: Check that it works
- Once the system connects, the key's "last use" time appears on the API Keys page.
- Cards created or changed by the system appear in your card list, and every change is in the card's history.
Connecting an AI assistant
- Create a separate key for the assistant. The assistant's AI usage stays on your own AI subscription.
- If the assistant only needs to read, give it read scopes only. Especially if it reads leads, do not give it "create and update cards": lead text is written by visitors.
- Setup steps for Claude Code, Cursor and similar clients are on the developer page. AI assistant (MCP)
Keep your keys safe
- One key per system: revoking one does not affect the others.
- Give the fewest scopes that do the job.
- Keys belong to the company, not to a person. When an administrator or vendor leaves, review the key list.
- If a key may have leaked, click "Revoke" on the API Keys page: it stops working immediately. Then create a new one.
Common questions
- Does it cost extra? API access is part of the plan. Your AI assistant's usage is billed by your AI provider, not by us.
- What if the card limit is full? New cards are refused until you upgrade or deactivate a card; nothing is deleted.
- Can a connected system delete cards? No. It can only deactivate them; deactivated cards can be reactivated and every change can be restored from history.
- What happens if our plan changes? If the new plan does not include API access, keys stop working but are kept; they work again when you upgrade.