When you query the Perplexity API, the default search behavior returns results from any time period. This can include outdated information that is not useful for tasks requiring the latest news, recent events, or time-sensitive data. The search recency filter lets you restrict results to a specific time range, such as the past day, week, … Read more
When you set a recency filter in the Perplexity API to limit results to the last week or month, the API may still return older sources. This defeats the purpose of the filter and can make your application appear stale. The problem is caused by how the API handles the recency parameter in combination with … Read more
If you use the Perplexity API for search, research, or question answering, you need to monitor your usage and cost. Without tracking, you may exceed your budget or hit rate limits unexpectedly. This article explains how to view your API usage dashboard, check remaining credits, and set spending alerts. You will learn the exact steps … Read more
Developers using the Perplexity API often receive unexpected charges because they do not understand how tokens are counted. The Perplexity API charges based on the total number of tokens sent in a request and received in a response. Token counting includes the prompt, the system instructions, any context, and the generated answer. This article explains … Read more
Perplexity API users often need to receive real-time updates when a search or analysis completes, rather than polling the API manually. Webhook notifications let Perplexity push results directly to your server when a task finishes, saving bandwidth and reducing latency. This article explains how to configure a webhook endpoint, register it with Perplexity, and handle … Read more
You set up a webhook in the Perplexity API to receive real-time data, but the endpoint never receives a POST request. This usually happens because of a misconfiguration in the webhook URL, an incorrect event selection, or a network-level block. This article explains why the webhook fails to trigger and provides step-by-step fixes to get … Read more
You need to collect large amounts of information from multiple sources without manually typing each query into a browser. The Perplexity API lets you send multiple search requests programmatically and retrieve structured answers. This article explains how to set up the API, write batch scripts, and handle large volumes of research data efficiently. Key Takeaways: … Read more
If you are building an application that sends multiple requests to the Perplexity API at the same time, you need to know the concurrency limit. Sending too many parallel requests can return HTTP 429 Too Many Requests errors and interrupt your service. The concurrency limit controls how many API calls your account can make simultaneously. … Read more
When your application calls the Perplexity API, a network request may hang or fail to complete within an acceptable time. This leaves your code waiting indefinitely, blocking user interactions or other critical processes. API timeouts happen when the server does not respond before your client gives up waiting. This article explains how to set request … Read more
When you send a request to the Perplexity API, the connection may stop waiting for a response before the answer is fully generated. This is called a timeout. The default timeout value is often too short for complex queries that require deep research or large context windows. This article explains why timeouts happen and how … Read more