HTTP Status Code Lookup API GET

HTTP Status Code Lookup is a tool for looking up HTTP status code information. It provides descriptions, categories, and common causes for all standard HTTP status codes from 1xx to 5xx.

Try it — live request, no key required

Request

GETapi.apiverve.com/v1/httpstatuslookup

Verification

Format

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

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // HTTP Status Code Lookup response payload
  }
}

About the HTTP Status Code Lookup API

HTTP Status Code Lookup works by querying a comprehensive database of HTTP status codes defined in various RFCs. Returns detailed information including the status code name, description, category, and boolean flags for quick identification.

What people use it for

API Development: Quickly reference HTTP status codes while developing and debugging APIs
Error Handling: Understand status codes when implementing error handling and response logic
Documentation: Generate status code documentation and error message templates for APIs
Troubleshooting: Diagnose HTTP errors and understand response codes during debugging

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 HTTP Status Code Lookup

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 Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.on VerveContext

Questions.

Common questions about the HTTP Status Code Lookup API.

Read the docs →

What does the HTTP Status Code Lookup API do?

HTTP Status Code Lookup is a tool for looking up HTTP status code information. It provides descriptions, categories, and common causes for all standard HTTP status codes from 1xx to 5xx.

How do I authenticate HTTP Status Code Lookup API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the HTTP Status Code Lookup API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the HTTP Status Code Lookup API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the HTTP Status Code Lookup API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the HTTP Status Code Lookup API use?

GET over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — GET /v1/httpstatuslookup

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
`code`Required	integer	`404`	HTTP status code to lookup range 100-599

Example request

1
2

curl "https://api.apiverve.com/v1/httpstatuslookup?code=404" \
  -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/httpstatuslookup

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": {
    "code": 404,
    "name": "Not Found",
    "description": "The requested resource could not be found",
    "category": "Client Error",
    "is_error": true,
    "is_success": false,
    "is_redirect": false,
    "is_informational": false
  }
}

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
`code`	number	`404`	HTTP status code number
`name`	string	`"Not Found"`	Standard name of the status code
`description`	string	`"The requested resource could not be found"`	Detailed description of the status code
`category`Premium	string	`"Client Error"`	Category (1xx, 2xx, 3xx, 4xx, 5xx)
`is_error`Premium	boolean	`true`	Whether this is an error status code
`is_success`	boolean	`false`
`is_redirect`	boolean	`false`
`is_informational`	boolean	`false`

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 — 2 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	HTTP Status Code Lookup calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

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/httpstatuslookup

No SDK to install — this is a plain HTTPS call to /v1/httpstatuslookup 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/httpstatuslookup" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/httpstatuslookup-apiSource, issues and the examples this page is built from.ReferenceHTTP Status Code Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/httpstatuslookupnpm APIVerve.API.HTTPStatusCodeLookupNuGet

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/httpstatuslookup

Install the Node.js SDK, then call the HTTP Status Code Lookup 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/httpstatuslookup

Node.js

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

Resources

npm@apiverve/httpstatuslookupThe published Node.js client, versioned and signed.GitHubapiverve/httpstatuslookup-apiSource, issues and the examples this page is built from.ReferenceHTTP Status Code Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.HTTPStatusCodeLookupNuGet

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

Call it from Python — GET /v1/httpstatuslookup

No SDK to install — this is a plain HTTPS call to /v1/httpstatuslookup 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/httpstatuslookup",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/httpstatuslookupnpm APIVerve.API.HTTPStatusCodeLookupNuGet

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/httpstatuslookup

Install the C# / .NET SDK, then call the HTTP Status Code Lookup 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.HTTPStatusCodeLookup

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/httpstatuslookup");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.HTTPStatusCodeLookupThe published C# / .NET client, versioned and signed.GitHubapiverve/httpstatuslookup-apiSource, issues and the examples this page is built from.ReferenceHTTP Status Code Lookup API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/httpstatuslookupnpm

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

Call it from Go — GET /v1/httpstatuslookup

No SDK to install — this is a plain HTTPS call to /v1/httpstatuslookup 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/httpstatuslookup", 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/httpstatuslookupnpm APIVerve.API.HTTPStatusCodeLookupNuGet

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

Call it from PHP — GET /v1/httpstatuslookup

No SDK to install — this is a plain HTTPS call to /v1/httpstatuslookup 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/httpstatuslookup");
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/httpstatuslookupnpm APIVerve.API.HTTPStatusCodeLookupNuGet

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

Call it from Ruby — GET /v1/httpstatuslookup

No SDK to install — this is a plain HTTPS call to /v1/httpstatuslookup 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/httpstatuslookup")
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/httpstatuslookupnpm APIVerve.API.HTTPStatusCodeLookupNuGet

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

All articles →

API Rate Limiting Done Right: A Complete GuideLearn how to design rate limits that protect your API while maintaining good developer experience.Read

Add Daily Horoscopes to Your App in 5 MinutesBuild a horoscope feature your users will actually check daily. Working code included.Read

Extract Clean Content from Any WebpageTurn messy web pages into clean Markdown. Perfect for content migration, archiving, AI training data, and building read-later tools.Read

HTTP Status Code Lookup API GET

Try it — live request, no key required

About the HTTP Status Code Lookup API

What people use it for

Ways to call it

Other ways to use HTTP Status Code Lookup

Questions.

Request parameters — GET /v1/httpstatuslookup

Required

Authentication

Response — GET /v1/httpstatuslookup

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — GET /v1/httpstatuslookup

Resources

Also published for

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

Resources

Also published for

Call it from Python — GET /v1/httpstatuslookup

Resources

Also published for

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

Resources

Also published for

Call it from Go — GET /v1/httpstatuslookup

Resources

Also published for

Call it from PHP — GET /v1/httpstatuslookup

Resources

Also published for

Call it from Ruby — GET /v1/httpstatuslookup

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — HTTP Status Code Lookup API

Reference Data

Related articles

Ready to build with HTTP Status Code Lookup? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog