For the complete documentation index, see llms.txt. This page is also available as Markdown.

Sending FLASHCALL

Sending FLASHCALL messages

POST https://direct.revicom.ltd/api/v1/message

The method allows for sending an array of single messages (1 to 1,000)

Headers

Name
Type
Description

Authorization*

string

Basic {TOKEN_1}

Content-Type*

string

application/json

Request Body

Name
Type
Description

channelType*

string

Sending channel (FLASHCALL)

senderName*

string

Sender name. Any string is allowed. The call will come from a number, the last digits being the sent code.

destination*

string

Subscriber number

content*

string

Numerical code, 4 symbols

tags

array

Message tags (array of strings). Each tag must match the expression ^\w+$ (any case letters, numbers and underscore "_" are allowed)

callbackUrl

string

Address to send callback

callbackEvents

array

Events to send callback (an array of strings). If there is callbackUrl and no callbackEvents in the request, a callback will be sent on the event delivered.

If the request is successful, a response is returned that lists the message IDs and result codes. With errors = false, all submitted messages are guaranteed to have been successfully generated.

{
  "errors": false,
  "items": [
    {
      "messageUuid": "063474ec-a34f-4558-90c5-984395000004",
      "code": 201
    },
    {
      "messageUuid": "063564ec-a34f-4558-90c5-984395000005",
      "code": 201
    }
  ]
}

Invalid token used.

{
    "error": {
        "code": 4012,
        "msg": "Bad credentials"
    }
}
{
    "error": {
        "code": 4010,
        "msg": "Not Authenticated"
    }
}

Token of wrong type used.

The request body contains invalid parameters; below are some response examples.

If you need to use codes consisting of more than four digits, please contact customer support.

Enumerations:

Parameter
Allowed values

callbackEvents

Request example

Sending FLASHCALL conversion

POST https://direct.i-dgtl.ru/api/v1/flashcall-conversion

The method is used to report the correctness of the user-entered code sent in a FLASHCALL message

Headers

Name
Type
Description

Authorization*

string

Bearer {TOKEN_1}

Content-Type*

string

application/json

Request Body

Name
Type
Description

messageUuid*

string

FLASHCALL message uuid

result*

string

Code entry result Code approved: NUMBER_VERIFIERD Invalid code: WRONG_CODE

code

string

Code

Enumerations:

Parameter
Allowed values

result

FLASHCALL conversion result

Sending the conversion assists in improvement of the quality of sending FLASHCALL-messages

Request example

Last updated