# PUBLISH Status
**REQUEST**
```
|
* \*op\*\* string required
Operation code: `status`
|
```
|
|---|
</th>
</tr>
|
| * \*id\*\* integer Request ID, an arbitrary integer to link requests with responses. Eg. `1` |
Example
```json
{
"id": 1,
"op": "status"
}
```
**RESPONSE**
```
|
data.**account** string required
Account's Ethereum address.. Eg. `0xE9b3a48d15BE316A8e34FAd53fFDFDddf0C3D24b`
|
|
data.**subscriptions** array of strings required
Array of available channels to subscribe to. Eg. `orderbook:ETH-27JAN23-1050-P`
|
```
|
|---|
</th>
</tr>
|
| * \*id\*\* integer Response ID, an arbitrary integer to link requests with responses. Eg. `1` |
Example
```json
{
"id": 1,
"data": {
"account": "0xE9b3a48d15BE316A8e34FAd53fFDFDddf0C3D24b",
"subscriptions": ["orderbook:ETH-27JAN23-1050-P"]
}
}
```
---
# 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://docs.aevo.xyz/api-reference/websocket-api/private-operations/get-status.md?ask=
```
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.