> For the complete documentation index, see [llms.txt](https://developer.ecall-messaging.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.ecall-messaging.com/api-references/https-interface/response-codes-and-headers.md).

# Response codes and headers

### Response types

The interface returns two response types:

* Send methods return HTTP status codes and eCall result codes.
* Cache operations return eCall result codes in the response body.

### HTTP status codes

| Status Code | Status Text         | Description                                 |
| ----------- | ------------------- | ------------------------------------------- |
| `200`       | OK                  | Job was accepted successfully               |
| `400`       | BadRequest          | Request failed. Check the eCall result code |
| `401`       | Unauthorized        | Credentials are missing or invalid          |
| `403`       | Forbidden           | The account has insufficient credits        |
| `500`       | InternalServerError | General processing error                    |

{% hint style="info" %}
Cache queries return HTTP `200 OK`. Check the XML body for the actual result code.
{% endhint %}

### eCall result codes

| Code    | ResponseText                           | Description                                    |
| ------- | -------------------------------------- | ---------------------------------------------- |
| `0`     | OK                                     | Message submitted successfully                 |
| `11000` | SyntaxError                            | Syntax error                                   |
| `11001` | PermissionDenied                       | Access denied                                  |
| `11100` | AdrAdCInvalid                          | Invalid recipient address                      |
| `11101` | AdrNAdInvalid                          | Invalid notification address                   |
| `11102` | AdrAdCMissing                          | Missing recipient address                      |
| `11103` | AdrNAdMissing                          | Missing notification address                   |
| `11104` | AdrAdCTooMany                          | Too many recipient addresses                   |
| `11105` | AdrAdCNotAllowed                       | Recipient address is outside the allowed range |
| `11200` | MsgNoCharacters                        | Missing message content                        |
| `11201` | MsgInvalidCharacters                   | Invalid characters in the message              |
| `11202` | MsgSendTimeInvalid                     | Invalid send time                              |
| `11203` | MsgSendTimeNotAllowed                  | Send time is outside the allowed time window   |
| `11204` | MsgTooLong                             | SMS or pager message is too long               |
| `11300` | AccNoUser                              | Unknown user                                   |
| `11301` | AccNoUnits                             | Insufficient credits                           |
| `11303` | AccNoFreeUnits                         | Insufficient free credits                      |
| `11400` | CallSystemInvalid                      | Invalid alerting system                        |
| `11401` | CallSystemInvalidForUser               | Invalid alerting system for this user          |
| `11402` | CallSystemNotSupported                 | Alerting system is not supported               |
| `11403` | CallSystemConfused                     | Alerting system is temporarily unavailable     |
| `11500` | IDMissing                              | Missing ID                                     |
| `11501` | IDInvalid                              | ID could not be found                          |
| `11502` | IDDoesNotExist                         | ID does not exist                              |
| `11600` | StateAlreadyTransmitted                | Message was already sent                       |
| `11700` | DataReadError                          | Data content could not be read                 |
| `11800` | CBMsgError                             | Callback contains a forbidden number or text   |
| `11810` | AnswerInvalid                          | Answer contains an invalid address             |
| `11904` | Too many attachments                   | More than 10 attachments were sent             |
| `11905` | Attachment(s) too large                | At least one attachment exceeds 5 MB           |
| `11906` | File type not supported                | Unsupported file type                          |
| `11907` | Error while processing the attachments | Unexpected attachment processing error         |
| `11908` | Error while saving the attachments     | Unexpected attachment save error               |
| `11910` | Job not found in Log                   | Job could not be found in the log              |
| `11911` | JobID required                         | A `JobID` is required for status queries       |
| `11912` | Job is scheduled                       | Job is scheduled for a future time             |
| `11913` | Job in progress                        | Job is still being processed                   |
| `11914` | Attachment name exceedes char limit    | Attachment name exceeds the character limit    |
| `11999` | Unknown error                          | Unknown error                                  |

### Client request ID

Set this request header to correlate responses with your own request IDs:

```
x-f24-client-request-id
```

Maximum length: 100 characters.

If you set it, the service echoes the same value in the response.

### Server request ID

Every response includes this header:

```
x-f24-request-id
```

Provide this value to support together with:

* The request time
* The eCall account name or interface username
* The operation type

### Source IP addresses

Use these source IPs to allow inbound traffic from eCall to your service:

* `193.93.208.200`
* `193.93.208.149`
* `193.93.208.153`

Source ports are dynamic and can use the full range `0–65535`.


---

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

```
GET https://developer.ecall-messaging.com/api-references/https-interface/response-codes-and-headers.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.