Skip to main content
POST

Authorizations

Authorization
string
header
default:App
required

This is the most secure authorization type and the one with the most flexibility.

API keys can be generated by calling the dedicated API method. Furthermore, API keys can have a limited scope and cover only some API methods. Lastly, they can be revoked at any time. This range of possibilities makes API keys well suited for separating the API access rights across multiple applications or use cases. Finally, the loss of an API key is easily manageable.

You can manage your API keys from GUI, or programmatically with dedicated API.

API key Authorization header example:

Body

text
string
required

Content of the message being sent.

Minimum string length: 1
languageCode
string

Language code for the correct character set. AUTODETECT lets the platform select the character set based on message content only for supported languages.

Pattern: ^(TR|ES|PT|AUTODETECT)$
transliteration
string

The transliteration of your sent message from one script to another. Transliteration is used to replace characters which are not recognized as part of your defaulted alphabet. ALL means that the transliteration process will recognize all supported languages.

Pattern: ^(TURKISH|GREEK|CYRILLIC|SERBIAN_CYRILLIC|BULGARIAN_CYRILLIC|CENTRAL_EUROPEAN|BALTIC|PORTUGUESE|COLOMBIAN|NON_UNICODE|NONE|ALL)$

Response

successful response

originalText
string

Message content supplied in the request.

previews
Preview · object[]

Allows for previewing the original message content once additional language configuration has been applied to it.