URL¶
POST https://security.webmoney.com/V1/GetMessages.ashx
Headers¶
Request body (JSON)¶
{
"reqn": 123456,
"msgid": 0,
"maxid": 0,
"datestart": "2025-09-01T00:00:00",
"datefinish": "2025-10-02T23:59:59"
}
| *. Field |
*. Type |
Description |
| reqn |
long |
Request number (idempotency/tracing). |
| msgid |
long |
Message id (0 — not applied). |
| maxid |
long |
Upper message id boundary (0 — not applied). |
| datestart |
DateTime |
Period start (ISO 8601: YYYY-MM-DDThh:mm:ss). |
| datefinish |
DateTime |
Period end (ISO 8601: YYYY-MM-DDThh:mm:ss). |
Example of a successful response¶
The response is streamed: first the meta and the messages array, then the final retval/retdesc fields.
{
"reqn": 123456,
"messages": [
{
"id": 1010246826,
"corrwmid": "111122223333",
"subj": "wmk:link-button=More details",
"msg": "Task proposal ...",
"dir": 2,
"sentdate": "2025-09-02T12:00:43"
}
],
"retval": 0,
"retdesc": "OK"
}
Example of an error (partial data already returned)¶
If an error occurs after the messages array has started, the response ends with an error flag.
{
"reqn": 123456,
"messages": [
{ "id": 1, "corrwmid": "123", "subj": null, "msg": "..." }
],
"retval": -2,
"retdesc": "Partial data followed by error: <description>"
}
Example of an error (before any data, HTTP 400)¶
{
"reqn": 123456,
"retval": -3,
"retdesc": "Request processing error: <description>"
}
Example of an authorization error (HTTP 401)¶
{
"retval": 401,
"retdesc": "Authorization error: <description>"
}
Possible return codes¶
| *. Code |
*. Description |
| 0 |
OK |
| 401 |
Authorization error (invalid/missing JWT) |
| 405 |
Method not allowed (only POST is supported) |
| -2 |
Data partially returned, then error occurred |
| -3 |
Request processing error before any data output |
Notes¶
- Clients must rely on
retval/retdesc to determine operation success,
even if the HTTP status is 200.