The Perplexity Sonar API lets you integrate real-time search capabilities into your own applications, bots, or workflows. Instead of visiting the Perplexity website, you can send a question and receive a cited answer programmatically. This article explains what the Sonar API is, what you need to set it up, and how to make your first … Read more
Choosing the right Perplexity API model for your application can be confusing. The Sonar family includes three tiers: Sonar, Sonar Pro, and Sonar Reasoning. Each model offers different search depth, reasoning capability, and cost. This article explains the differences between these three models, their ideal use cases, and how to configure them in your API … Read more
To use Perplexity programmatically in your own applications, scripts, or third-party tools, you need an API key. This key acts as a unique token that authenticates your requests to the Perplexity API. Without it, you cannot access the search, chat, or completion endpoints. The process requires a paid Perplexity Pro subscription. Free accounts do not … Read more
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 … Read more
Managing API request volume is critical when integrating Perplexity into your applications. Without rate limits, your code can overwhelm the API server, trigger HTTP 429 Too Many Requests errors, or exceed your subscription quota unexpectedly. This article explains how to configure rate limits in Perplexity API requests using best practices for Python, JavaScript, and HTTP … Read more
You call the Perplexity API and get a 429 HTTP status code with the message “Rate Limit Exceeded.” This error stops your application or script from completing its request. The cause is simple: you sent more API requests than your current plan or key allows within a specific time window. This article explains why the … Read more
When you use the Perplexity API to generate search-backed answers, the response includes a citations field that lists the source URLs used. However, many developers find this field missing or empty in their API output. This usually happens because the request was sent without the required parameter that enables citation gathering. This article explains how … Read more
When you call the Perplexity API and the citations array comes back empty, your application cannot display the sources behind the answer. This breaks the core value of Perplexity’s search-grounded responses. The problem usually occurs because the return_citations parameter is not set to true in your API request. This article explains the exact cause and … Read more
Streaming Perplexity API responses using Server-Sent Events allows your application to display real-time answers as they are generated instead of waiting for the full response. SSE is a standard protocol that sends data from the server to the client over a single HTTP connection. This article explains how to configure your API request to enable … Read more
When you use the Perplexity API for streaming responses, the output may stop before the model finishes generating an answer. This early cutoff interrupts workflows that depend on complete replies, such as automated research summaries or customer-facing chatbots. The issue typically stems from client-side timeout settings, network interruptions, or misconfigured API parameters. This article explains … Read more