> For the complete documentation index, see [llms.txt](https://docs.oxapay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oxapay.com/legacy/api-reference/system-status.md).

# System Status

The endpoint allows users to check the current state of the OxaPay API. By making a request to this endpoint, users can verify if the API is functioning correctly.

<mark style="color:green;">`POST`</mark> `https://api.oxapay.com/monitor`

{% tabs %}
{% tab title="200: OK " %}

```json
OK
```

{% endtab %}
{% endtabs %}

### Usage

This endpoint is primarily used to perform a health check on the OxaPay API. It helps users determine if the API is operational and responsive. A successful response with "OK" indicates that the API is functioning as expected. If there are any issues with the API, the response message will provide relevant details about the encountered error.

Please note that this endpoint is useful for monitoring and diagnosing the overall health of the OxaPay API. It is commonly used by developers and administrators to ensure the stability and reliability of the payment gateway.

<br>


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.oxapay.com/legacy/api-reference/system-status.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.