Did You Mean API

GET

Catch misspelled search terms and suggest the right words.

Did You Mean suggests spelling corrections for misspelled search queries and phrases. Pass any text string to receive the original query along with a list of alternate spelling suggestions.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/didyoumean?query=what%20weather%20today%20is

Query parameters

querystring

Verification

Format

No key required to try it. Get a key to use it in your app.

Example

{
  "status": "ok",
  "error": null,
  "data": {
    "query": "what weather today is",
    "didYouMean": [
      "what is the weather today",
      "what's the weather like today",
      "what will be the weather today"
    ]
  }
}

About the Did You Mean API

Did You Mean works by analyzing the text provided and checking for spelling mistakes and suggestions powered by AI. This is similar to Google's did you mean. Suggestions are returned based on your input query

What people use it for

E-Commerce Search Suggestions: When shoppers mistype product names in a store search bar, display alternate spelling recommendations so they still find inventory.
Help Desk Query Fallback: To prevent dead ends in customer support portals, offer corrected search terms whenever a knowledge base query returns zero articles.
User Form Normalization: Clean user-submitted tags and profile fields during registration by matching misspellings against recommended corrections before saving entries to the database.
Chatbot Typo Recovery: Chatbots can parse incoming user messages with spelling mistakes and prompt users with suggested corrections before triggering fallback handlers.

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Other ways to use Did You Mean

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets

Questions.

Common questions about the Did You Mean API.

Read the docs →

Can it check full search phrases, or only single words?

You can send entire search queries and multi-word phrases to the endpoint. The AI-backed engine evaluates the full text string to identify typos and find appropriate spelling suggestions.

What would 5,000 search corrections a month cost me?

5,000 requests use 100,000 credits, which fits well within the Starter plan allowance of 200,000 credits at $29.99 per month. That works out to about $0.003 per check, or $3.00 per 1,000 calls. The Free plan provides 10 checks each month for testing.

What does the response return if the query has no spelling mistakes?

When a query is already spelled correctly, the didYouMean array will return without alternative corrections. Your original input text is always preserved and returned in the query field so you can confirm what was evaluated.

Can I receive multiple spelling suggestions for a single input?

Yes. The Did You Mean API returns suggestions inside a JSON array rather than a single string, allowing your application to present multiple alternative spellings to the user or pick the first suggestion automatically.

Does it automatically overwrite the text or just provide suggestions?

It provides suggestions separately from your input rather than modifying the text silently. The response returns your original query alongside an array of suggested corrections so your product can choose between automatic replacement and prompting the user.

Request parameters — GET /v1/didyoumean

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`query`Required	string	`what weather today is`	The text you want to check for spelling mistakes

Example request

1
2

curl "https://api.apiverve.com/v1/didyoumean?query=what%20weather%20today%20is" \
  -H "x-api-key: YOUR_API_KEY"

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — GET /v1/didyoumean

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "query": "what weather today is",
    "didYouMean": [
      "what is the weather today",
      "what's the weather like today",
      "what will be the weather today"
    ]
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`query`	string	`"what weather today is"`	Original input query text provided by user
`didYouMean`	array	`[what is the weather today, ...]`	Array of spelling suggestions and corrections

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 20 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Did You Mean calls	Per 1,000 calls
Free	Free	200	10	Free
Starter	$29.99	200,000	10,000	$3.00
Pro	$99.99	1,000,000	50,000	$2.00
Mega	$299.99	4,000,000	200,000	$1.50

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — GET /v1/didyoumean

No SDK to install — this is a plain HTTPS call to /v1/didyoumean with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/didyoumean" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/didyoumean-apiSource, issues and the examples this page is built from.ReferenceDid You Mean API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/didyoumeannpm APIVerve.API.DidYouMeanNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — GET /v1/didyoumean

Install the Node.js SDK, then call the Did You Mean API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/didyoumean

Node.js

const res = await fetch("https://api.apiverve.com/v1/didyoumean", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/didyoumeanThe published Node.js client, versioned and signed.GitHubapiverve/didyoumean-apiSource, issues and the examples this page is built from.ReferenceDid You Mean API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.DidYouMeanNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — GET /v1/didyoumean

No SDK to install — this is a plain HTTPS call to /v1/didyoumean with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/didyoumean",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/didyoumeannpm APIVerve.API.DidYouMeanNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — GET /v1/didyoumean

Install the C# / .NET SDK, then call the Did You Mean API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.DidYouMean

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/didyoumean");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.DidYouMeanThe published C# / .NET client, versioned and signed.GitHubapiverve/didyoumean-apiSource, issues and the examples this page is built from.ReferenceDid You Mean API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/didyoumeannpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — GET /v1/didyoumean

No SDK to install — this is a plain HTTPS call to /v1/didyoumean with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/didyoumean", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/didyoumeannpm APIVerve.API.DidYouMeanNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — GET /v1/didyoumean

No SDK to install — this is a plain HTTPS call to /v1/didyoumean with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/didyoumean");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/didyoumeannpm APIVerve.API.DidYouMeanNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — GET /v1/didyoumean

No SDK to install — this is a plain HTTPS call to /v1/didyoumean with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/didyoumean")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/didyoumeannpm APIVerve.API.DidYouMeanNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Text Processing

View all 45 →

All articles →

Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read

Summarize Text with AI: A Practical GuideUse AI to summarize articles, documents, and user content. Tutorial with code for content platforms, research tools, and dashboards.Read

7 Content Moderation Mistakes That Sink AppsYour app allows user content. Here are the moderation mistakes that get apps pulled from stores.Read

Did You Mean API

Try it — live request, no key required

About the Did You Mean API

What people use it for

Ways to call it

Other ways to use Did You Mean

Questions.

Request parameters — GET /v1/didyoumean

Required

Authentication

Response — GET /v1/didyoumean

Response fields

Response headers

Errors

What a call costs — 20 credits per call

Call it from cURL — GET /v1/didyoumean

Resources

Also published for

Call it from Node.js — GET /v1/didyoumean

Resources

Also published for

Call it from Python — GET /v1/didyoumean

Resources

Also published for

Call it from C# / .NET — GET /v1/didyoumean

Resources

Also published for

Call it from Go — GET /v1/didyoumean

Resources

Also published for

Call it from PHP — GET /v1/didyoumean

Resources

Also published for

Call it from Ruby — GET /v1/didyoumean

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Did You Mean API

Text Processing

Related articles

Ready to build with Did You Mean? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog