**Requirements:** none in particular — any role can create keys for themselves. 1. Go into your **Profile** (avatar menu, top right → "Profile" — Manual 15, section 2.4) and find the **"My API keys"** panel. 2. Tap **"New key"**. 3. Type a **name** that helps you identify what this key is for — for example "Integration with my CRM". 4. Leave **"Allowed origins"** as-is (`*`) unless you know you're going to use the key from a browser and want to restrict it — full detail in section 6. 5. Choose the **expiration**: "Never", 30, 90 or 365 days. 6. Under **"What this key can do"**, leave it as-is if you want the key to have all of your role's permissions (the most common case), or tap **"Customize"** to narrow it down to only some areas — full procedure in section 7. 7. Tap **"Send code"**. **Result:** the Platform sends a **6-digit code to your own account email**, valid for 10 minutes. 1. Enter the code and tap **"Create key"**. > **Important — The key is shown ONCE only** > > As soon as it's created, the Platform shows you the full key — it's the **only** time you'll see it in > full. From that point on, in any list only the prefix is shown (`aa_xxxxxxxx…`), never the rest. Copy it > and save it in a secrets manager or environment variable **before** tapping "Done" — if you lose it, > there's no way to recover it: you'll have to revoke that key and create a new one (section 9). **Final result:** the key shows up in the "My API keys" table with its prefix, last use, expiration and **Active** status.