Status codes
Overview
DocuBot uses standard HTTP status codes to communicate the result of your requests and system operations. These codes help you identify whether a task succeeded or why it failed. Codes are grouped into three main categories: success, client errors, and server errors.
Success codes (2xx)
These codes indicate that your request was successfully received, understood, and accepted.
| Code | Name | Meaning |
|---|---|---|
| 200 | OK | The request succeeded. This is the standard response for successful data retrieval. |
| 201 | Created | The request succeeded and a new resource was created, such as a new repository configuration. |
| 204 | No Content | The request succeeded, but there is no representation to return. This usually follows a successful deletion. |
Client error codes (4xx)
These codes indicate that there is an issue with the request you sent. You typically need to modify your input or permissions to resolve these.
| Code | Name | Meaning |
|---|---|---|
| 400 | Bad Request | The server cannot process the request due to invalid parameters, such as an incorrectly formatted URL slug. |
| 401 | Unauthorized | Authentication is missing or invalid. Ensure you are signed in with your Google account. |
| 403 | Forbidden | You do not have permission to access the resource. This may occur if you attempt to access a private repository without GitHub authorization. |
| 404 | Not Found | The requested resource could not be found. Verify the repository ID or documentation path. |
| 429 | Too Many Requests | You reached the rate limit. This often occurs if you exceed the daily manual sync limit. |
Server error codes (5xx)
These codes indicate that the server failed to fulfill a valid request. These issues are usually temporary or related to system maintenance.
| Code | Name | Meaning |
|---|---|---|
| 500 | Internal Server Error | The system encountered an unexpected condition. This may happen during complex AI generation tasks. |
| 503 | Service Unavailable | The server is currently unable to handle the request, often due to temporary maintenance or high load. |
Common causes and fixes
Use this table to quickly resolve frequent issues encountered during repository management and synchronization.
| Symptom | Likely cause | Resolution |
|---|---|---|
| 401 Unauthorized | Expired session | Sign out and sign back in using your Google account. |
| 403 Forbidden | Private repo access | Connect your GitHub account in the settings panel to grant DocuBot access. |
| 429 Rate Limit | Manual sync limit | Wait for the daily limit to reset or rely on your scheduled daily sync. |
| 400 Validation Error | Invalid slug | Ensure your slug contains only lowercase letters, numbers, and dashes. |
Support and escalation
If you encounter a status code that is not documented here or if a server error persists, please reach out for technical assistance.
- Email support: support@ademero.com
- Technical portal: https://www.ademero.com
When contacting support, please include the specific status code you received and the action you were performing.