API Keys
API keys let you access ParseSphere programmatically. Even if you only use the dashboard, you'll need an API key for certain integrations.
Creating an API Key
- Go to API Keys in your dashboard
- Click New API key
- Enter a name (e.g., "Production Server", "Development") — this is optional but recommended
- Click Create key
- Copy the key immediately — it won't be shown again!
Important
API keys are only displayed once when created. Store them securely — you cannot retrieve them later.
Managing API Keys
The API Keys page shows all your keys with:
| Column | Description |
|---|---|
| Name | The name you gave the key |
| Prefix | First few characters (e.g., sk_abc...) |
| Created | When the key was created |
| Last Used | Most recent API call |
| Status | Active or inactive |
Delete a Key
- Click the Delete button next to a key
- Confirm deletion
Warning
Deleting a key is immediate. Any applications using it will stop working instantly.
Security Best Practices
Do's ✓
- Use different keys for development and production
- Store keys in environment variables
- Rotate keys every 3-6 months
- Delete unused keys promptly
Don'ts ✗
- Never commit keys to version control
- Don't share keys via email or chat
- Don't embed keys in client-side code
Organization Keys
If you're part of an organization:
- Keys created in org context belong to the organization
- All org members with appropriate permissions can see org keys
- Org keys can access shared workspaces
When You Need an API Key
Dashboard users need an API key for:
- Zapier or Make.com integrations
- Custom automations
- Connecting third-party tools
Developers need an API key for:
- All programmatic API access
- Server-side integrations
- Building applications
What's Next?
- Usage — Monitor your API usage
- Developer Guide — Learn the API integration