Create a key for an integration, copy it the one time it is shown, and revoke it when you stop using it.
An API key lets a system you or your developer built talk to your Fine Structure account without your password. Keys live on the API Keys page: open the account menu, then Developers, then API Keys, or go to /api-keys. If you want an AI tool such as Claude or Cursor to work on your apps, you need an MCP token instead, with its own permissions: see Connect AI tools.
1. Click New Key: At the top of the page click + New Key. A box called Create New API Key opens. Give the key a name that says where it is used, for example "Booking sync" or "Production". A key without a name is saved as Default.
2. Click Generate Key: A green box appears: Your new API key (shown once!). Click Copy and paste the key into the system that needs it, or into your password manager. When you are done click Dismiss.
3. Revoke a key you no longer use: Every key appears under Your API Keys with its name, the first characters of the key and Created with the date. Click Revoke and confirm. The key stops working and stays in the list with the Revoked label.
The key is shown once: Fine Structure keeps only a fingerprint of the key, not the key itself, so nobody can show it to you again. If you lost it, revoke it and create a new one.
The API Usage box at the bottom of the page shows the format. The key goes in the Authorization header of every request, from a server only. Never put it in a web page, an app's front end or a public repository.
Authorization: Bearer fse2_your_api_key_here
Word | What it means
API | The way one computer system talks to another, without a person clicking.
API key | A long password made for a system instead of a person. Whoever holds it can act for your account, so treat it like your bank PIN.
Header | A line of hidden information sent with every request, before the content.
Authorization header | The header that carries the key. Its value is the word Bearer, a space, and the key.
From a server only | The key lives on a computer you control (your developer's server, or an automation tool such as Make). Never inside a web page or an app that runs on the visitor's phone, where anyone can read it.
In an automation tool the request usually has a place for headers with two boxes. You fill them like this:
Name: Authorization Value: Bearer fse2_your_api_key_here
Which address the request goes to, and what it sends, comes from the integration you are building. If you are not sure, give this page to your developer. For the most common jobs there is a ready tool: see the table below.
You want to | Use
Let Claude, Cursor or another AI tool build and edit your apps | An MCP token
Let your CRM create contracts and read signed ones | A contracts API key
Store a password or key that your apps and agents use | A global secret
Get notified when an agent writes a message | An agent webhook
Have your website send files into the Business Brain | A notebook webhook
Q: I closed the box before copying the key. Can I see it again?
A: No. Revoke it and create a new one.
Q: Does revoking a key delete it?
A: It stops working at once. It stays in the list marked Revoked, so you can see which keys existed.
Q: How many keys can I have?
A: Make one key per system. Then you can revoke one without breaking the others.
Q: What happens to my keys if I delete my account?
A: All of them are revoked as part of deleting the account.
Q: The system I connected says the key is not accepted.
A: Check three things: the value starts with Bearer and one space, the key was copied whole, and its row is not marked Revoked. If all three are right, the address you call may not take account keys; ask your developer, or use the tool from the table above that fits the job.
Q: Can I put the key in my app so it works in the browser?
A: No. Anything inside a web page can be read by any visitor. Keep keys in Secrets and use them from a server function.
Related: Connect AI tools: Claude, ChatGPT, Cursor and more, Global secrets: one key for many apps and agents, Webhooks for agent events, Advanced contract tools