> ## Documentation Index
> Fetch the complete documentation index at: https://docs.go.gbgplc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Response Codes

> General response and error codes

GBG GO APIs use conventional HTTP response codes to indicate the success or failure of an API request.

| Code    | Description           | Notes                                                                   |
| ------- | --------------------- | ----------------------------------------------------------------------- |
| **200** | Ok                    | Request successful                                                      |
| **201** | Created               | New resource created successfully                                       |
| **400** | Bad request           | Request invalid or missing required parameters                          |
| **401** | Unauthorized          | No valid authentication token or token expired                          |
| **403** | Forbidden             | No permission to access the requested resource                          |
| **404** | Not found             | Requested resource or endpoint does not exist                           |
| **405** | Method not allowed    | HTTP method used, for example, `GET` or `POST`, is not supported        |
| **500** | Internal server error | A problem with the API, which may not be related to your request server |
| **503** | Service unavailable   | API service is temporarily down                                         |

For more details on API response codes and troubleshooting, refer to [Error handling](/docs/go-v1/developer-integration/error-handling).