HTTP Status Codes & API Error Mapping Markdown Table Template
Standardized API error responses, error payload codes, HTTP status mapping, retryability, and troubleshooting steps.
Interactive Template Customizer
Edit cells, add rows, or sort — changes update the markdown liveColumn Architecture & Alignment Specification
Carefully chosen column alignments ensure optimal visual scannability across desktop and mobile screens:
| Column Header | Alignment | Delimiter Syntax | Design Rationale |
|---|---|---|---|
| HTTP Status | right | ---: | Aligns numeric scale, defaults, or magnitudes |
| Error Code | left | :--- | Standard left-aligned readable text & descriptions |
| Retryable | center | :---: | Centers compact status symbols, flags, or tags |
| Cause / Meaning | left | :--- | Standard left-aligned readable text & descriptions |
| Client Action | left | :--- | Standard left-aligned readable text & descriptions |
Pro Tips for HTTP Status Codes & API Error Mapping
- Right-align the numeric HTTP status code.
- Center-align the Retryable indicator (`Yes` / `No`).
- Document RFC-7807 Problem Details `type` URIs if applicable.
How to Deploy This Table Across Platforms
Paste raw Markdown into README.md. Leave one blank newline above and below for GFM compliance.
Paste directly into Live Preview mode. Use wikilinks ([[Note]]) inside cells for bidirectional linking.
Press Enter to make a fresh empty line block, then paste. Notion auto-transforms it into a native Simple Table block.
Standard GFM tables work out of the box in modern MDX engines. You can style them via custom CSS selectors.
Raw GFM Code
| HTTP Status | Error Code | Retryable | Cause / Meaning | Client Action |
| ------------------------: | :------------------ | :-------: | :--------------------------------------------- | :---------------------- |
| `200 OK` | `SUCCESS` | No | Request completed successfully | Process payload |
| `400 Bad Request` | `INVALID_PAYLOAD` | No | Malformed JSON syntax or missing schema fields | Validate request body |
| `401 Unauthorized` | `AUTH_EXPIRED` | No | Bearer token missing, malformed, or expired | Refresh access token |
| `403 Forbidden` | `ROLE_INSUFFICIENT` | No | User lacks RBAC permission for resource | Request admin privilege |
| `404 Not Found` | `ENTITY_NOT_FOUND` | No | Target UUID does not exist in database | Check resource ID |
| `429 Too Many Requests` | `RATE_LIMITED` | Yes | Exceeded 1,000 requests per minute quota | Backoff with jitter |
| `503 Service Unavailable` | `GATEWAY_TIMEOUT` | Yes | Upstream microservice unresponsive | Retry after 5 seconds |Standard padded style with boundary pipes matching GitHub GFM parser specifications.
Platform Support
Syntax Formatting Rules
- Pipe Escaping: Use
\|for text with pipe symbols. - Multi-line Cells: Use
<br>for line breaks. - Monospace Text: Wrap variables or code in backticks (
`key`). - Empty Values: Use
—instead of leaving cells empty.
More Developer Markdown Templates
Browse all 50 templatesREST & GraphQL API Parameters
Document REST endpoints, GraphQL query fields, request payload types, requirements, and default fallback values.
Environment Variables (.env) Matrix
Document required and optional environment keys, secret classifications, types, and staging vs production defaults.
CLI Options & Arguments Reference
Reference table for command-line tool options, shorthand aliases, data types, environment overrides, and descriptions.
Frequently Asked Questions About HTTP Status Codes & API Error Mapping
How should I format parameters, flags, or keys in this HTTP Status Codes & API Error Mapping table?
Wrap variable names in the "HTTP Status" column in backticks (e.g., `200 OK`). This enforces monospace rendering, prevents underscores from italicizing surrounding text, and improves readability across GitHub and developer documentation sites.
Where in my repository or project documentation should I place this HTTP Status Codes & API Error Mapping table?
This template is specifically designed for developer portals, public api documentation, mobile sdk integration specifications. Place it inside your project's README.md, technical wiki, or developer portal. Always leave at least one blank newline before and after the table to ensure the GFM parser detects it properly.
Why is the "HTTP Status" column styled with right alignment?
The "HTTP Status" column functions as the primary key of this table. Setting it to right alignment establishes an anchor along the left reading margin, making it effortless for developers to scan down the list.
How do I add line breaks inside a single cell of this HTTP Status Codes & API Error Mapping table?
Standard Markdown table rows cannot contain literal carriage returns. To create a multi-line list inside a cell, insert HTML <br> tags (e.g. "Item 1<br>Item 2<br>Item 3"). This keeps the entire entry in a single clean row without breaking column alignments.
How do I handle optional or missing values in HTTP Status Codes & API Error Mapping?
Never leave table cells completely empty, as some strict Markdown parsers may collapse empty pipes. Instead, insert an em-dash ("—"), "N/A", or "None" to explicitly indicate that a value is not applicable.
Can I export this HTTP Status Codes & API Error Mapping table into CSV, Excel, or HTML?
Yes. In the interactive toolkit above, you can edit your data and use our integrated export tools to convert this table directly into CSV, JSON, HTML <table>, or LaTeX with a single click.