> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/data-management/archived-data/success-and-failure-code-responses-to-your-http-post-requests.md).
# Success and failure code responses to your HTTP POST requests
The following table provides the various success and failure code responses to your HTTP POST requests, which can help you troubleshoot any problems with your HTTP collector configuration.
| Success/failure response code | Description | Output code displayed (if applicable) |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| 200 | Success code that indicates there are no errors and the request was successful. The `last_used` field timestamp is updated accordingly. | `{ "ok": "true"}` |
| 400 | Error code that indicates that there is a problem with any of the following:
- The partition date value (
x-cortex-partition) is missing or empty in the HTTP request. - The partition date value in the HTTP request (
x-cortex-partition) isn't in the correct format of YYYY-MM-DD. - Dataset name value (x-cortex-source-dataset) is missing or empty in the HTTP request.
| Partition date value missing or empty in HTTP request:
{ "error": "partition value is missing or empty"}
Partition date value isn't in the correct format of YYYY-MM-DD:
{ "error": "partition value must be in the format YYYY-MM-DD"}
Dataset name value is missing or empty in the HTTP request:
{ "error": "sourceDataset value is missing or empty"}
|
| 401 | Unauthorized error code that indicates an incorrect authorization key for the HTTP collector is being used. | `{ "error": "Failed to validate authentication detail"}` |
| 403 | Error code that indicates one of the following:
- Wrong header key for the HTTP collector is in the HTTP request and cannot be used.
- Partition date value (x-cortex-partition) in the HTTP request is not within the license retention period for hot and cold storage.
| Wrong header key in HTTP request:
The Bulk Load configuration has been deleted and cannot be used
Partition date value not within the license retention period for hot and cold storage:
partition is less than license start date
|
| 413 | Error code indicating the request entity is too large as the request size is more than the 25 MB limit. | `Request entity too large as the size is more than 25 MB limit` |
| 429 | Error code indicating too many requests as the ingestion limits are reached for one of the following reasons:
- Daily ingestion limit of \ files is exceeded.
- Daily file size ingestion limit of \ GB is exceeded.
| Daily ingestion file limit exceeded:
exceeds daily limit of \ files
Daily ingestion file size limit exceeded:
Daily file size limit of \ GB for HTTP requests sent is exceeded
|
| 500 | Error code indicating an unexpected internal error while processing the bulk load HTTP request. | `Unexpected error while processing bulk load request` |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsiam/configure-cortex-xsiam/data-management/archived-data/success-and-failure-code-responses-to-your-http-post-requests.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.