Docs/APIs/HTTP Status Code Lookup

HTTP Status Code Lookup

Look up HTTP status code information

OperationalCredits 1 per callp50 207msReference DataStar

Overview

HTTP Status Code Lookup works by querying the HTTP status codes registered with IANA and defined across RFCs 9110, 6585, 4918 and others. Returns the status code name, description, category and boolean flags; with details=true it also returns a link to the defining RFC section, and on paid plans the current registry name, the RFC section itself, whether the code is safe to retry, whether RFC 9110 lets caches store it by default, and the headers the spec pairs with it (Location, Retry-After, WWW-Authenticate, Allow and so on).

Live Test HTTP Status Code Lookup API →

Endpoint

One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.

GEThttps://api.apiverve.com/v1/httpstatuslookup
curl "https://api.apiverve.com/v1/httpstatuslookup?code=404&details=true" \
  -H "x-api-key: your_api_key_here"

Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.

Authentication

Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.

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.

Parameters

Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.

ParameterTypeDescription
codeRequiredintegerHTTP status code to lookup
range 100–599
detailsOptionalbooleanAlso return the registry name, defining RFC section and link, retry and default-caching flags, and related headers

Response

Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.

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,
    "registry_name": "Not Found",
    "spec": "RFC 9110, Section 15.5.5",
    "spec_url": "https://www.rfc-editor.org/rfc/rfc9110#section-15.5.5",
    "is_retryable": false,
    "is_cacheable_by_default": true,
    "related_headers": []
  }
}

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.

FieldTypeExampleDescription
codenumber404HTTP status code number
namestring"Not Found"Standard name of the status code
descriptionstring"The requested resource could not be found"Detailed description of the status code
categoryPremiumstring"Client Error"The classification of the status code by its leading digit: Informational, Success, Redirection, Client Error, or Server Error
is_errorPremiumbooleantrueWhether the status code represents a client or server error (4xx or 5xx)
is_successbooleanfalseWhether the status code represents a successful response (2xx)
is_redirectbooleanfalseWhether the status code represents a redirection (3xx)
is_informationalbooleanfalseWhether the status code represents an informational response (1xx)
registry_namePremiumstring"Not Found"Current name in the IANA HTTP status code registry, which can differ from the common name (413 is now Content Too Large). Returned with details=true
specPremiumstring"RFC 9110, Section 15.5.5"The RFC, and section where the registry gives one, that defines the code. Returned with details=true
spec_urlstring"https://www.rfc-editor.org/rfc/rfc9110#section-15.5.5"Link to the defining RFC section on rfc-editor.org. Returned with details=true
is_retryablePremiumbooleanfalseWhether the code signals a transient condition, so the same request may succeed later (408, 425, 429, 500, 502, 503, 504). Returned with details=true
is_cacheable_by_defaultPremiumbooleantrueWhether RFC 9110 Section 15.1 lets a cache store this response without explicit freshness information. Returned with details=true
related_headersPremiumarray[]Headers the defining spec pairs with this code, such as Location for redirects or Retry-After for 429 and 503. Empty when there are none. Returned with details=true

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.

StatusMeaningWhat to do
400Input was rejectedRead error; it names the parameter.
401Key missing or invalidCheck the header name and the key value.
403Key valid, but not permittedA key restriction or IP allow-list; see key scoping.
429Rate limited, or out of creditsRead error to tell them apart; see rate limits.

Use cases

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

Other ways to use HTTP Status Code Lookup

Set up HTTP Status Code Lookup on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →
Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.VerveSheets →Reference →
Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →

More in Reference Data:

Was this page helpful?