Skip to main content
Replace Perplexity Search API calls with Keenable’s POST /v1/search. This page maps each parameter and response field of Perplexity’s POST /search to Keenable, and shows the same request on both APIs. It doesn’t cover the Sonar chat completions API.

Migrate with your coding agent

Paste this prompt into your coding agent. Your agent reads this page as markdown and rewrites your calls. Your agent finishes by running one Keenable request and showing you the result. The prompt works with Claude Code, Cursor, Codex and any other agent that can read a URL.

What changes

Endpoint map

Parameter map

A parameter Keenable doesn’t list returns 400 with Unknown parameter(s), so remove Perplexity Search API parameters instead of sending them along. “Closest” means the Keenable parameter does a similar job with a different format or behavior, described in the notes.

Response map

Before and after

This search asks both APIs for 5 pages published in the past week. The Keenable request runs without a key.
The Keenable response has query, mode and up to 5 results. Each result has a title and a url, and usually a snippet, a published_at and an acquired_at.

No equivalent in Keenable

These Perplexity Search API features have no Keenable counterpart. Remove them from the request, or handle them in your own code as described.
  • last_updated_after_filter: Keenable has no last-updated filter. Use published_after for the publish date or acquired_after for when Keenable indexed the page.
  • search_type: people: Keenable has no people search. Search the web with a query that names the person.
  • country: Keenable has no country targeting.
  • search_language_filter: Keenable has no language filter.
Mapping checked on 2026-11-19 against docs.perplexity.ai/api-reference/search-post.

Use an SDK

This program sends the same search as the Keenable tab above with the official SDK. It runs without a key and prints the title, URL and publish date of each result.
You see up to 5 results, each published in the past week, with its publish date as an ISO 8601 timestamp. Install the SDK for your language from SDKs.

Verify the migration

Check each item before you remove the old client:
  1. Run the Keenable request from Before and after. The status is 200.
  2. results has at most as many entries as max_results. Each entry has a title and a url.
  3. Your code reads published_at as an ISO 8601 timestamp where it read date.
  4. Every date you send is YYYY-MM-DD or a relative delta such as 1w, not MM/DD/YYYY.
  5. Your requests send no parameter from a None row. A leftover one returns 400 with unknown_parameter.
  6. Change the path to /v1/search or /v1/fetch and send X-API-Key. The response gains a usage object. See API keys.

Common questions

Send the request to /v1/search/public or /v1/fetch/public with an X-Keenable-Title header and no key. Without a key, each endpoint allows 1,000 requests per hour and 10 per second per IP address. See Rate limits.
This page maps the Search API only. Keenable returns ranked pages with snippets, not a generated answer. To answer a question, pass the snippets to your own model.
Keenable filters by publish date with published_after and published_before, and by index date with acquired_after and acquired_before. It has no last-updated filter. See Date and time filters.
Each search mode and each kind of fetch is billed as its own SKU, and a call made with a key returns what it cost in usage. See Pricing and Balance and usage.