HTTP Status Lookup

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 Lookup Source →

Formula

One function covers the whole catalog: the first argument names the source, the next are its inputs, and the field after them says which single value lands in the cell. Formulas covers the grammar that applies to all of them.

=VERVE("httpstatuslookup", A2, "name")

A2 holds the code you are looking up. Drag the formula down and each row resolves on its own.

With literal values

Nothing has to come from a cell — typed values work the same way.

=VERVE("httpstatuslookup", 404, "name")

Inputs

Required inputs are positional, in the order below, followed by the field. Everything else is passed as a "name", value pair after that — the same shape as SUMIFS. Premium inputs are accepted on every plan but only take effect on plans that include them.

Input	Type	Where it goes	Description
`code`Required	integer	argument 2 (A2)	HTTP status code to lookup range 100–599
`details`Optional	boolean	"details", value	Also return the registry name, defining RFC section and link, retry and default-caching flags, and related headers

Passing an option

=VERVE("httpstatuslookup", A2, "name", "details", "true")

What lands in your sheet

The field — the argument after the inputs — is what makes the formula resolve to one cell. Its value is a dot-path from the table below, so swapping it is how you pull a different value — one formula per column.

Seeing everything at once

Leave the field out and the formula returns the whole response instead: two columns, field name on the left and value on the right, spilling from the cell you typed in.

=VERVE("httpstatuslookup", A2)

Good for exploring, not for filling down

The second row's table would land on top of the first's, and every cell after the first reads #REF! (#SPILL! in Excel). Keep one per sheet, or name a field, and leave the cells below and to the right empty.

Response fields

Paths are relative to data. Each one is exactly what the field argument accepts, so swapping it is how you pull a different value into a cell. On a plan without a Premium field the cell reads #PREMIUM(field) rather than a value, so a locked field never looks like a real answer.

Use as the field	Type	Example cell value	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`	The classification of the status code by its leading digit: Informational, Success, Redirection, Client Error, or Server Error
`is_error`Premium	boolean	`true`	Whether the status code represents a client or server error (4xx or 5xx)
`is_success`	boolean	`false`	Whether the status code represents a successful response (2xx)
`is_redirect`	boolean	`false`	Whether the status code represents a redirection (3xx)
`is_informational`	boolean	`false`	Whether the status code represents an informational response (1xx)
`registry_name`Premium	string	`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
`spec`Premium	string	`RFC 9110, Section 15.5.5`	The RFC, and section where the registry gives one, that defines the code. Returned with details=true
`spec_url`	string	`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_retryable`Premium	boolean	`false`	Whether 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_default`Premium	boolean	`true`	Whether RFC 9110 Section 15.1 lets a cache store this response without explicit freshness information. Returned with details=true
`related_headers`Premium	array	`[]`	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

Filling a whole column

Both platforms make one batched call for a column rather than one request per cell, and both cost the same — 1 credit per row looked up. How you write it differs, because the two runtimes batch at different points.

Rows 2–100 in one call

=VERVE("httpstatuslookup", A2:A100, "name")

In Google Sheets, give the arguments ranges and the answers spill down from the cell you typed in. Custom functions there run synchronously and in isolation, so dragged cells cannot be coalesced — the range form is how a column becomes one call. The field is required here: a per-row two-column table has nowhere to spill. Use a full column per input (A2:A100, not A2) — a single-cell reference is read as row 1 only and the rest of the column comes back blank.

In Excel, type the formula once and fill down — no range form and none needed, because its runtime is asynchronous and the add-in coalesces the calls a fill produces into a single batched request. Do not hand VERVE.CALL a range: Excel flattens it into positional arguments, so A2:A100 arrives as a hundred separate arguments and the cell reads #ERR rather than filling.

Either way, column A holds your code values and the answers land beside them, one row each, blank rows skipped.

When a cell doesn't fill

A failed lookup returns readable text starting with #ERR rather than a spreadsheet error, because Excel cannot show a custom message on a real error — you would get a bare #VALUE! with no reason. The trade-off is that IFERROR() will not catch it; test with LEFT(cell, 4) = "#ERR" instead. Error handling covers the rest.

Cell reads	What happened
`#ERR Not connected`	No API key saved. Open the side panel and connect your account.
`#ERR Replace <name> with a cell or value`	A preview formula was copied as-is. Swap the placeholder for a cell reference.
`#ERR No "x" in httpstatuslookup`	An option name this source does not take. The message lists the ones it does.
`#ERR No data point "…"`	The field path is not in the response. Check it against the table above.
`#PREMIUM(field)`	The field exists but your plan does not include it.
`#ERR Out of credits`	The cycle's credits are spent. Usage resets on your billing date.

Before the formula works

The add-in reads the API key you saved once in the side panel — the key never goes in the formula, so a shared sheet does not leak it and a collaborator without access simply sees the last calculated values.

Install the add-in for Google Sheets or Excel.
Open the side panel and sign in, or paste a key from your dashboard.
Type the formula above into any cell.

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 Lookup

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

Call it as a REST APIOne HTTPS endpoint and an x-api-key header, with SDKs for Node, Python and .NET.APIVerve →Reference →

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.VerveKit →Reference →

Ground an agent on itA cited, machine-checkable fact your model can't produce on its own.VerveContext →Reference →