> 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/soap-webservice/status-queries.md).

# Status queries

### GetStateBasic

Use this method to query the status of a sent message.

To use it, send the original message with a `JobID`.

**Required:** `AccountName`, `AccountPassword`, `JobID`

**Optional:** `Address`

{% hint style="info" %}
For jobs sent to multiple recipients, specify `Address`. Use international format with leading zeros and no spaces, for example `0041791234567`.

If you omit `Address`, the response returns the last job within the `JobID`.
{% endhint %}

### Response structure

```
ServiceResponse
├── ResponseCode     Response code per response table (0 = OK)
└── ResponseText     Response text per response table

JobResponse          (only populated when ResponseCode = 0)
├── JobID            JobID of the sent message
├── Address          Recipient number
├── JobType          Job type
├── SendState        Send status
├── ErrorState       Error status for fax. For other types, use SendState.
├── PointsUsed       Number of credits consumed
└── FinishDate       Date and time when the job was completed
```

{% hint style="info" %}
If `ResponseCode` is not `0`, `JobResponse` is empty.
{% endhint %}

### Standard webservice response

All web methods return this structure:

| Parameter      | Description                                                              |
| -------------- | ------------------------------------------------------------------------ |
| `ResponseCode` | `0` means the job was accepted. Any other value means an error occurred. |
| `ResponseText` | Description of the response code                                         |

{% hint style="warning" %}
An accepted job is not the same as a delivered job. Use status queries, logs, or notifications to confirm delivery.
{% endhint %}

### HTTP headers

#### 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 send it, the service echoes the same value in the response.

#### Server request ID

Every response includes this header:

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

Provide this ID to support together with the request time, account name, and operation type.


---

# 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/soap-webservice/status-queries.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.