API Key Management
API keys authenticate your AI tools with Prowlo's MCP server. Each key is tied to your organization and grants access to the full suite of Prowlo tools.
Creating an API Key
API keys can only be created by admins and owners of your organization. To generate a new key:
- Navigate to Settings > API Keys in your Prowlo dashboard
- Click the
Generate Keybutton - Give your key a descriptive name (e.g.,
Claude Desktop,Cursor) - The full API key is displayed once — copy it immediately and save it somewhere secure
- Keys follow the format
prowlo_followed by 32 characters
Security Best Practices
- Never share API keys in public repositories, chat messages, screenshots, or emails
- Create one key per tool or integration — easier to revoke if compromised
- Revoke unused keys promptly from your Settings page
- Treat API keys like passwords — they grant full access to your organization's data
- Store keys in secure environment variables, not in source code
Revoking an API Key
If a key is compromised or no longer needed, revoke it immediately:
- Go to Settings > API Keys
- Find the key you want to remove
- Click the trash icon to revoke it
- Revoked keys stop working immediately — any MCP sessions using that key will disconnect
Key Scopes
By default, API keys have access to all MCP tools in your organization. The full suite of available tools includes:
list_opportunities— Browse opportunities across your feedget_opportunity— Fetch detailed data on a specific opportunitysubmit_draft— Send engagement drafts to Prowlo for reviewget_product_profile— Retrieve your organization's product profileget_subreddit_intelligence— Access subreddit-specific engagement guidancekeyword_list— List all tracked keywords with match statisticskeyword_create— Add a new tracked keywordkeyword_update— Activate or pause a tracked keywordkeyword_delete— Remove a tracked keyword and its match history
Rate Limits
Each API key is rate-limited to 60 requests per minute. This applies to all MCP tool calls made with that key.
When you make API requests, the response includes rate limit headers:
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 45
X-RateLimit-Reset: 1712000400The X-RateLimit-Reset header shows the Unix timestamp when your quota resets. If you exceed the limit, you'll receive a 429 Too Many Requests response — simply wait for the reset window and retry.