Missed the Community Update Webinar? Learn what's coming in the next release & catch up 🤞
Watch recording 🟢
All categories
System
Access management
AI
Appflows - Technical
Billing
Billing and policy
Built-in apps
Business cases addon
Business Intelligence
Business Operations and ERPs
Calendar addon
Commerce
Communication
Community apps
Contacts module
Contracts addon
CRM and Sales tools
Customer Support
Database
Education
Features
File and Document Management
Forms Addon (Legacy)
Getting started with Boost.space
HR management
Internet of Things
Invoices module
IT and Development
language-tools
Lifestyle
Marketing
Marketplace - Overview
Marketplaces
Modules and Addons
News monitor addon (legacy)
Notes addon
Offers addon
Orders module
Other
Pages addon
Policy
Process Management
Productivity
Products module
Projects addon
Records
Spaces
Surveys and Forms
System Settings (for Admins)
Tasks module
Travel
Users and teams
Wall addon
Warehouses addon
Website Building
Work hours addon
Integrations
Apps
Connections
Errors
Functions
Getting started with Boost.space Integrator
Integrator Modules
Mapping
Scenarios
Tools
Tutorials
List of applications
Table of Contents

Understanding Common HTTP Error Codes

When browsing the web or working with APIs, you may encounter various HTTP error codes. These status codes help identify the cause of an issue and guide troubleshooting. Below, we’ll explain some of the most common client and server errors.

Client Errors

400 Bad Request

A 400 Bad Request error occurs when the server cannot process the request due to invalid syntax. This may be caused by malformed request headers, incorrect query parameters, or invalid data formats.

401 Unauthorized

A 401 Unauthorized error means authentication is required, but the request lacks valid credentials. This often happens when an API key, token, or login credentials are missing or incorrect.

403 Forbidden

A 403 Forbidden error occurs when the server understands the request but refuses to authorize it. This usually happens when the user does not have sufficient permissions to access the requested resource.

404 Not Found

A 404 Not Found error means the requested resource does not exist on the server. This may be due to an incorrect URL, a deleted resource, or a broken link.

Server Errors

500 Internal Server Error

A 500 Internal Server Error is a general error message indicating something went wrong on the server’s end. The exact cause can vary from configuration issues to software bugs.

502 Bad Gateway

A 502 Bad Gateway error occurs when a server acting as a gateway or proxy receives an invalid response from an upstream server. This is common in distributed systems.

503 Service Unavailable

A 503 Service Unavailable error means the server is temporarily unable to handle the request, often due to maintenance or high traffic.

504 Gateway Timeout

A 504 Gateway Timeout error occurs when a server acting as a gateway does not receive a timely response from an upstream server.

Conclusion

HTTP error codes can be frustrating, but understanding what they mean can make troubleshooting much easier. Whether you’re dealing with client-side mistakes or server issues, checking the details of each error and following best practices can help you resolve problems quickly. If you’re working with APIs, always refer to the documentation to ensure your requests are structured correctly. Over time, getting familiar with these status codes will save you time and effort when debugging issues.