HTTP Status Code Lookup API

About the HTTP Status Code Lookup API

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).

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

Beta

GraphQL

Query language

New

MCP

For AI agents

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

Optional

1
2

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

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.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20

{
  "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.

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.

Errors

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

What a call costs — 1 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.

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.

Zero-code embed — one snippet, no backend

Drop an interactive HTTP Status Code Lookup form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.

Changelog — HTTP Status Code Lookup API

Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.

Currently v1