# Make your own API key > A key for your own scripts that reads only what you can, and stops when you lose access. A personal API key lets a script or a reporting tool of yours read Taktyl's Data API as you. It reads only the workspaces you work in, and the plan and usage only while you are an organisation admin. It only reads: nothing can be changed or deleted through it. You can make one when your organisation's plan includes the Data API. ## Make a key 1. Go to **Account › Integrations**, to **Your API keys**. 2. Press **Make a key**. 3. Give it a name, such as the script that will use it. 4. Tick what it can read. 5. Press **Make the key**, then **Copy** it straight away. Taktyl shows it only once. The key is made in the organisation you are working in, and lasts 90 days. Send it in an `Authorization: Bearer` header. The page links to the API reference, which lists every address. ## When a key stops working A key acts as you, so it follows what you can reach, on every request: - Leave the organisation, or have your account there switched off, and the key stops. - Stop being an organisation admin, and it stops reading the plan and usage. - Lose a workspace, and it stops reading that workspace. It also stops when it expires, when you revoke it, or when the organisation's plan no longer includes the Data API. ## Rotate or revoke Open the key's menu. **Rotate** makes a new key with the same name; the old one stops at once. **Revoke** stops it for good. Every key you hold is listed, whichever organisation you made it in, so you can always revoke one. Organisation admins make tokens for the whole organisation on **Organisation › Integrations › Data API**.