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

# HTTP response codes

> Learn about the HTTP status codes returned by the NeetoEngage API.

## Success codes

<ResponseField name="200 OK">
  The request was successful and the server returned the requested data.
</ResponseField>

<ResponseField name="201 Created">
  The request was successful and a new resource was created. Returned when you create a feature request or a comment.
</ResponseField>

## Error codes

<ResponseField name="401 Unauthorized">
  The request needs to be authenticated. This typically means:

  * Missing API key.
  * Invalid API key.
  * Expired API key.
  * The key still has the placeholder value `your-api-key`.
</ResponseField>

<ResponseField name="404 Not Found">
  The requested resource was not found. This could indicate:

  * The feature request, track or changelog does not exist in your workspace.
  * Workspace subdomain is incorrect.
</ResponseField>

<ResponseField name="406 Not Acceptable">
  The `Accept` header does not allow JSON. The API only returns `application/json`.
</ResponseField>

<ResponseField name="422 Unprocessable Entity">
  The request could not be processed. This could indicate:

  * A required parameter is missing.
  * A value is invalid, for example a blank title or a website URL that is not valid.
</ResponseField>

<ResponseField name="429 Too Many Requests">
  Rate limit exceeded. Try again after some time.
</ResponseField>

## Server error codes

<ResponseField name="500 Internal Server Error">
  An unexpected error occurred on the server. If this persists, please contact
  support.
</ResponseField>

<ResponseField name="503 Service Unavailable">
  Returned by [Search feature requests](/api/feature-requests/search) with the error `search_unavailable` when the search service is down. Try again after some time.
</ResponseField>

## Error response format

When an error occurs, the API returns a JSON response with error details:

```json 401 Unauthorized theme={"system"}
{
  "error": "Could not authenticate, invalid API Key"
}
```

```json 404 Not Found theme={"system"}
{
  "error": "FeatureRequest does not exist."
}
```

<ResponseField name="error" type="string">
  A human-readable error message.
</ResponseField>

<Tip>
  When debugging API issues, the HTTP status code often provides the first clue
  about what went wrong. Start by checking the status code before diving into
  the response body.
</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.