# HTTP-Status Codes

The web-service uses five different responses with a dedicated meaning (see also [Response Schema](/mspro.services/general-information/response-schema.md)).

### 200 - Ok: Success with data

The endpoint returned the expected data.

### 204 - NoContent: Success no data

The endpoint's expectations have been meet (success) but there is not data returned.

### 400 - Bad Request 

The endpoint could not provide the requested results because of the request parameters. If you would change the request parameters the endpoint would eventually respond the expected data. 

{% hint style="info" %}
This status-code is used with *query parameters* or *request bodies*, only. A *path-segment* which is used as a resource-id, for example, is not considered to be request data. It is a URL

See [#using-query-parameters](#using-query-parameters "mention")
{% endhint %}

### 404 - Not Found

The not-found status code is used only when a URL path is invalid. 

It is not used to respond that a resource was not found. Finding a resource is a business use-case while 404 is a technical representation of a "URL endpoint not found".

HTTP 404 (Not Found) is a standard response code indicating that the requested resource could not be found on the server.

### 500 - Internal Server Error

Something went wrong on the server (Exception). See response details for more information.


---

# Agent Instructions: 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:

```
GET https://services.markusschmidt.pro/mspro.services/general-information/http-status-codes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.