The Nestr api allows manipulation of items from outside the Nestr application. The api can be used to create an integration with other applications, or to easily add items from anywhere.
To get started, go to your workspace settings where you will find a tab called Integrations

There you will find the Workspace API access integration. Click configure and create a new API key.

You can optionally name the API key and give a description. If you have multiple integrations, it pays to setup a key for each one and name them accordingly. Once you have named your API key, click Create API key. This will generate and store the key for you. We will only show you the key once, so make sure you copy it and store it securely in a password manager.
The key above is a workspace API key. It belongs to the workspace and acts for the workspace as a whole, not for a person. You can also create a personal API key. A personal API key acts as you.
Personal API keys do not expire. A key works until you revoke it. When you create one you can tick Read-only, so the key can read data but cannot create, change or delete anything.
The API Keys card on https://app.nestr.io/profile#integrations lists more than the keys you created yourself. It also lists every app and integration you have authorized through OAuth to access your account, for example Zapier or an AI assistant such as Claude or ChatGPT connected through MCP. Each entry shows:
Click Revoke next to an entry to remove its access straight away. For a personal key, the key stops working. For an app you authorized through OAuth, revoking removes that grant, so the app loses access and has to ask you to authorize it again before it can reconnect. Any integration still using a revoked key or grant will start failing.

Workspace API keys are not in this list. You manage those in the workspace settings, as described above.
The Nestr API key is a Bearer token. You can find the full API documentation and examples on our API documentation page.
Send the key in the Authorization header of every request, for example Authorization: Bearer YOUR_API_KEY. This works the same for workspace keys and personal keys.