Perplexity API Key Revoked Without Notice: Cause and Recovery

You are using the Perplexity API in your application or script, and suddenly requests fail with a 401 or 403 error. The API key that worked minutes ago now returns an authentication failure. This often happens without any warning email or dashboard notification from Perplexity. This article explains the technical causes behind silent API key revocation and provides step-by-step recovery steps to restore your access quickly.

Why Perplexity Revokes API Keys Without Notice

Perplexity does not always send an email when an API key is revoked. The revocation happens at the server level, and the next API call returns an error. The most common root causes are:

Rate Limit or Quota Exceeded

Perplexity imposes per-minute rate limits and monthly token quotas on API keys. If your application sends requests faster than the limit or uses all tokens before the billing cycle ends, the key is temporarily or permanently revoked. The API returns a 429 Too Many Requests error before revocation, but if the spike is extreme, the system may skip the warning and revoke the key directly.

Payment Failure or Billing Issue

If you use a pay-as-you-go plan and your credit card expires, is declined, or your account balance goes negative, Perplexity revokes all active API keys. This is a security measure to prevent unpaid usage. The system does not always send a notification; the key simply stops working.

Security Policy Violation

Perplexity monitors API usage patterns for abuse. If your key is used from multiple IP addresses in rapid succession, or if the requests contain prohibited content (e.g., hate speech, illegal activity), the key is revoked without prior notice. This protects the platform from misuse.

Account Suspension or Deletion

If your Perplexity account itself is suspended due to ToS violations or if you accidentally delete the account, all associated API keys are revoked. Account deletion is irreversible, but suspension can sometimes be appealed.

Steps to Diagnose and Recover a Revoked API Key

Follow these steps in order. Do not skip any step — each one rules out a different cause.

Step 1: Check the API Key Status in the Dashboard

1. Log in to Perplexity API Dashboard
   Go to perplexity.ai/settings/api. Sign in with the account that owns the revoked key.
2. Navigate to API Keys section
   On the left menu, click API Keys. A table lists all keys with a status column. A revoked key shows a red badge with the text Revoked.
3. Click the revoked key to view details
   The detail page shows the revocation reason if Perplexity recorded one. Common reasons include Rate limit exceeded, Billing issue, or Security violation.

Step 2: Review Usage and Quota

1. Go to Usage & Limits
   In the dashboard, click Usage & Limits on the left menu.
2. Check the current billing period
   Look at the Tokens Used bar. If it is at 100% or above your plan limit, you have exceeded your quota. The key may have been revoked to prevent overage charges.
3. Check rate limit graph
   Below the quota bar, a graph shows requests per minute. If you see a spike above your plan limit, that explains the revocation.

Step 3: Verify Billing Status

1. Go to Billing
   Click Billing on the left menu.
2. Check payment method
   Under Payment Method, verify the card on file is not expired. If it expired, click Update Payment Method and enter a new card.
3. Check outstanding balance
   If the Current Balance shows a negative number, you owe money. Pay the balance by clicking Add Funds or Pay Now.

Step 4: Create a New API Key

1. Return to API Keys
   Click API Keys on the left menu.
2. Click Create New Key
   A button at the top of the table. A dialog appears asking for a key name and permissions.
3. Set key permissions
   Select the models and endpoints this key can access. For most use cases, leave all boxes checked.
4. Copy the key immediately
   After creation, a popup shows the key value once. Copy it and store it securely. If you close the popup, the key is hidden forever — you must delete and recreate it.
5. Update your application
   Replace the old revoked key with the new key in your code, environment variables, or configuration file. Restart your application.

Step 5: Contact Support If the Key Was Revoked Due to a Security Violation

1. Open a support ticket
   Go to perplexity.ai/support. Click Contact Support.
2. Explain the situation
   State that your API key was revoked without notice. Include the key name (not the full key value) and the timestamp when it stopped working. Do not mention any prohibited content — if you suspect a violation, ask for clarification.
3. Wait for a response
   Perplexity support typically replies within 24-48 hours. If the revocation was a mistake, they will reactivate the key or instruct you to create a new one.

If the Key Is Still Revoked After Following These Steps

Key Shows Active but API Returns 401

The key may be active but the request is missing the Authorization header or uses the wrong format. Ensure your HTTP header is exactly: Authorization: Bearer YOUR_API_KEY. Do not add quotes or extra spaces. If you are using an SDK, update it to the latest version.

Key Was Revoked and Recreated but Old Key Still in Code

You may have updated the key in the dashboard but forgot to update the environment variable or configuration file. Check all locations where the key is stored: .env files, CI/CD secrets, cloud provider secret managers, and hardcoded strings in source code.

Account Was Deleted

If you cannot log in to the Perplexity API Dashboard, your account may have been deleted. This is irreversible. You must create a new account and a new API key. To prevent this, enable two-factor authentication and avoid sharing your login credentials.

Perplexity API Key Revocation: Free vs Pro vs Enterprise Plans

Item	Free Plan	Pro Plan	Enterprise Plan
API access included	No	Yes, with token quota	Yes, with custom quota
Monthly token limit	N/A (no API)	5 million tokens	Custom (negotiated)
Rate limit (requests/min)	N/A	60 RPM	Custom (higher)
Revocation notification	N/A	Email only for billing issues	Email and dashboard alert
Support response time	N/A	24-48 hours	2-4 hours

If you are on the Free plan, you cannot use the API at all. Upgrade to Pro or Enterprise to get API access. Enterprise plans include priority support and proactive alerts before quota exhaustion, reducing the chance of silent revocation.

You now know the four main causes of silent API key revocation and the exact steps to diagnose and recover each one. Start by checking the API key status in the dashboard, then verify your usage and billing. Creating a new key is the fastest recovery method when the cause is quota or billing. For security violations, contact support with the key name and timestamp. To minimize future revocations, set up usage alerts in the dashboard and monitor your token consumption weekly.