API Keys & Integrations
How to manage API keys for integrations and third-party access to your Buyer24 organization — including connecting Buyer24 to Claude.
Overview
API keys let external systems interact with your Buyer24 organization. They're used for:
- Third-party integrations that need to create or read RFQs
- AI assistants like Claude, connected through the Buyer24 connector
- Automation workflows connecting Buyer24 to other tools
Only organization admins can create and manage API keys. If you don't see Settings → API Keys, ask your admin — see Understanding Roles.
Creating an API Key
- Go to Settings → API Keys
- Click Generate New Key
- Enter a name that describes the key's purpose (e.g., "ERP Integration", "Claude Connector")
- Copy the generated key immediately — it will only be shown once
Managing Keys
The API Keys page shows all active keys with:
- Name — The label you gave the key
- Created — When the key was generated
- Last used — When the key was last used to make a request
You can revoke a key at any time. Revoking a key immediately disables any integration using it.
Connect Buyer24 to Claude
Buyer24 has a connector for Claude. Once connected, you can work with your procurement data by simply asking — for example:
- "Browse my suppliers and show me who does CNC machining"
- "Review the quotes on RFQ REQ-20260515 and compare them"
- "Draft an RFQ for 500 aluminum brackets, responses due next Friday"
Claude can find matching suppliers from your directory, compose the RFQ, and create it in Buyer24 — but anything Claude drafts stays a draft for your review. It never sends RFQs to suppliers on its own; you review and send from Buyer24.
You can also pair the Buyer24 connector with other connectors — for example QuickBooks — and move data between systems in plain language: "find completed RFQs that haven't been pushed to QuickBooks as a purchase order yet, and push the first one."
To connect, add Buyer24 in Claude's connector settings and authorize access (or use an API key from this page as the credential).
Tip: Treat the connector like any other integration — give it its own key, and revoke it here if you stop using it.
Security Best Practices
- One key per integration — If your ERP system and an automation tool both connect to Buyer24, use separate keys. This way you can revoke one without affecting the other.
- Revoke unused keys — If an integration is decommissioned, revoke its key.
- Never expose keys in client-side code — Keep keys on the server side only.
- Check "Last used" — A key that hasn't been used in months is a candidate for revocation.
- Grant only what's needed — When a key or connector only needs to read data (e.g., reporting), don't give it write access.
Troubleshooting
| Symptom | Likely cause | What to do |
|---|---|---|
| Integration suddenly stops working | The key was revoked | Generate a new key and update the integration |
| "Unauthorized" errors | The key was copied incorrectly or is from a different environment | Re-copy the key; if lost, revoke it and generate a new one |
| "Permission denied" on a specific action | The key doesn't have access to that capability | Create a key with the required access, or ask Claude/your integration to stay within read-only actions |
Note: A key's value is only shown once, at creation. If you lose it, there's no way to view it again — revoke the old key and create a new one.