URL Encoder
Percent-encode text for safe use in URLs.
Look up any HTTP status code and learn what it means and when an API should return it.
Runs in your browser. Your input is never uploaded.
Search by code or keyword.
Filter by class (1xx–5xx).
Expand a code to read the details.
Input
429Output
Too Many RequestsPercent-encode text for safe use in URLs.
Format, beautify and minify JSON with custom indentation.
Convert Unix timestamps to dates and back, in UTC and local time.
401 means not authenticated; 403 means authenticated but not allowed.
301 is permanent, 302 temporary. Use 308 and 307 to preserve the HTTP method.
It is an April Fools’ joke from RFC 2324 but widely recognized.
The HTTP status codes you will meet most often, what they mean and which one to return from your API in common situations.
Understand REST APIs: resources, HTTP methods, status codes, JSON payloads, idempotency, pagination, versioning and authentication basics.
39 codes
The server received the request headers; the client should send the body.
When to use: Rarely handled manually; used with Expect: 100-continue for large uploads.
The server agrees to switch protocols as requested.
When to use: Returned when upgrading a connection to WebSocket.
Preliminary headers so the browser can start preloading resources.
When to use: Send Link headers early while the final response is still being generated.
The request succeeded.
When to use: Default success for GET, and for PUT/PATCH/POST that return a body.
The request created a new resource.
When to use: Return after POST creates something, with a Location header pointing to it.
The request was accepted for processing, but is not finished.
When to use: Use for asynchronous jobs; give the client a status URL.
Success with no response body.
When to use: Common for DELETE and for PUT/PATCH when nothing needs returning.
The server is delivering only part of the resource.
When to use: Used for range requests such as video streaming and resumable downloads.
The resource has a new permanent URL.
When to use: Use for permanent redirects; search engines transfer ranking. Method may change to GET.
The resource is temporarily at another URL.
When to use: Temporary redirect; prefer 303 or 307 when method semantics matter.
Fetch the result with a GET at another URL.
When to use: Redirect after a successful POST (Post/Redirect/Get).
The cached copy is still valid.
When to use: Reply to conditional requests (ETag / If-Modified-Since) with no body.
Temporary redirect that keeps the HTTP method and body.
When to use: Temporary move when POST must stay POST.
Permanent redirect that keeps the HTTP method and body.
When to use: Permanent move for APIs where the method must be preserved.
The server cannot process the request because of a client error.
When to use: Malformed syntax, invalid JSON, missing required parameters.
Authentication is required or has failed.
When to use: Missing/invalid credentials. Include a WWW-Authenticate header.
Reserved for future payment use.
When to use: Occasionally used by APIs for billing limits.
The server understood the request but refuses to authorize it.
When to use: Authenticated user lacks permission. Re-authenticating will not help.
The resource does not exist (or is hidden).
When to use: Unknown URL or ID. Also used to avoid revealing that a private resource exists.
The method is not supported for this resource.
When to use: Include an Allow header listing supported methods.
No representation matches the Accept headers.
When to use: Client asked for a format the server cannot produce.
The server timed out waiting for the request.
When to use: The client was too slow to send the full request.
The request conflicts with the current state of the resource.
When to use: Duplicate unique value, edit conflict, version mismatch.
The resource was permanently removed.
When to use: Stronger than 404: tells clients and crawlers it will not come back.
A conditional header (If-Match etc.) evaluated to false.
When to use: Optimistic concurrency checks on updates.
The request body exceeds server limits.
When to use: Upload bigger than allowed.
The request body format is not supported.
When to use: Wrong Content-Type, e.g. sending XML to a JSON-only endpoint.
Joke status from RFC 2324 (April Fools’ Day).
When to use: Easter egg; not for real APIs.
Syntax is valid but the content fails semantic validation.
When to use: Validation errors on well-formed JSON (e.g. invalid email field).
The server is unwilling to risk processing a replayable request.
When to use: TLS early-data replay protection.
The client has sent too many requests (rate limiting).
When to use: Include Retry-After. Applies to per-user or per-IP limits.
Headers are too large.
When to use: Oversized cookies or headers.
Access is denied for legal reasons.
When to use: Content blocked by law or court order.
An unexpected condition prevented the request from completing.
When to use: Generic server bug. Log details server-side; do not leak stack traces.
The server does not support the requested functionality.
When to use: Unknown method or unbuilt feature.
A gateway/proxy received an invalid response from upstream.
When to use: Common with reverse proxies when the app server crashed or returned garbage.
The server is temporarily unable to handle the request.
When to use: Maintenance or overload. Include Retry-After.
A gateway/proxy timed out waiting for upstream.
When to use: Upstream too slow; tune timeouts or optimize the backend.
The HTTP version is not supported.
When to use: Very rare.