Coming from our legacy RingRing's Portal application (https://portal.ringring.be) ?
You are on the right page. We will guide you through the differences between the old products and the new version.

Account Management & Users

Users Management Key Differences

Naxai platform provides advanced features for user security and management.

Key differences

Feature	Legacy Portal	New Naxai
User identity	username	email
MFA	❌ No	✅ Yes
SSO	❌ No	✅ Yes
Brute Force detection	❌ No	✅ Yes
Impossible Travel Detection	❌ No	✅ Yes
Password History and Strength Checker	❌ No	✅ Yes

FAQ

Can I share an email with different users ?

Yes, technically it's possible, even with MFA, by using a product like 1Password , which allows users to use a shared user identity.
We don't recommend this approach for your security; how do you know which person did what?
Which MFA Factors are supported on Naxai?

SMS notifications, Email notifications, One-time passwords, Recovery Code
How do you activate SSO for Naxai?

SSO can be requested via your Sales Account. More info on SSO can be found here.
How can I have multiple users on the same account?

You can use the '+' (plus addressing) trick in your email address; for example, the email address [email protected] is an alias of [email protected]. It means you can use [email protected] to create a new user account.
The emails sent to [email protected] will be delivered to [email protected]

SMS Mailer

The legacy SMS Mailer is now accessible via 3 different products on Naxai, based on your usage.

If you used SMS Mailer to send only 1 or 2 SMS messages at a time, we recommend using Quick SMS.
Quick SMS is easy to use and faster.

If you used SMS Mailer with automated FTP ingestion, we created the FTP-to-SMS on Naxai.
The FTP to SMS on Naxai added several security and configuration features.

When using SMS Mailer with uploaded files or contacts, we recommend using SMS Broadcasts.
SMS Broadcasts can use a flexible file format for uploaded files and dynamic segments, whereas SMS Mailer was limited to a fixed set of contacts.

Here is a summary of the main differences.

Legacy SMS Mailer	Differences
User Experience	Naxai comes with a lot of new features and is faster, more responsive and more secure than the legacy SMS Mailer.
Send one or two SMS	Focused on sending one message at a time.
Limited to 10 custom fields	You can create up to 50 custom attributes on top of the existing standard attributes
XLS and CSV support	Naxai supports only CSV files with commas or semicolons as separators. From Excel (Mac OS), go to "File" -> "Save As" -> and select the file format "CSV UTF-8 (Comma-delimited) (.csv) From Excel (Windows), go to "File" -> "Save As" -> Select CSV From Google Sheet, go to "File" -> "Download" -> Select CSV
Limited to the replacement of values	Legacy SMS Mailer was limited to replacing the values of custom fields. Naxai uses Liquid Syntax, which lets you not only replace values but also manipulate and transform them.
No Preview of messages	Naxai provides a live preview of messages as you compose.
Not possible to test a mailing	Before sending your messages with SMS Broadcasts, you can send a test message to your phone number to check the layout and ensure the formatting is correct.
Limit usage of uploaded file columns	With SMS Broadcasts, you have more flexibility when using an uploaded file. You can compose your message based on multiple columns. With the previous, you can see the message content in real time.
SMS Mailer has no spread of the message	SMS Broadcasts and FTP-to-SMS can be used to deliver your messages over time. It's useful to include a phone number in your message so people don't call you back at the same time.
Security Delay	Naxai has no security delay before sending the messages. With Naxai, you have a full preview of your messages and can send a test message to your phone; that's the reason we believe a security delay is not required. If you still do not want to send the message directly, you can always schedule your broadcast.
Time Window	Time Window is replaced by Calendars. Calendars can be shared across all Naxai products and offer additional features: you can add exclusion dates (public holidays) and set up 2 time windows per day... In legacy SMS Mailer, messages sent outside of the Time Window would have been rejected; in Naxai, they will be sent at the next opening window.
Allow long messages	On the legacy SMS Mailer, the option "Allow long messages" is replaced by the option "Number of SMS parts" on Naxai, allowing you to control the number of SMS parts; you can limit it to 1, but also to 2, 3, or 4, depending on your use case.
Group of Contacts	Naxai is using Segments to replace groups of contacts. On SMS Mailer, you need to define your groups by manually adding people to them. You can continue to do that with Segments by creating a Manual Segment, but you can also create Dynamic Segments. Dynamic segments use conditions to determine whether a contact must be in the group. Suppose you have contacts with the attributes language and country; you can create a dynamic segment based on those conditions. Each time a contact is added, updated, or deleted, it will be evaluated against the segment and will automatically enter or leave it. If you use Groups in SMS Mailer, we recommend that you visit the Segmentssection.
Not possible to pause	SMS Broadcasts can be paused if you are using a spread of messages. In all other cases, SMS are sent as fast as possible.
Incoming replies	The legacy SMS Mailer allows you to send a manual response to incoming replies. SMS Broadcasts can be used with SMS Automations , allowing you to handle incoming responses automatically, send them by email, SMS, or HTTP request, update your contacts, or reply to incoming SMS. To continue manually replying to incoming messages, Quick SMS will be used.
Webhooks	You can receive in real-time the SMS delivery status report and incoming messages using the Webhooks Manager, even if the messages are not sent via the API.

SMS API

The Naxai SMS API has some subtle changes compared to the legacy Message API of Portal https://portal.ringring.be

You can compare the legacy format with the new API in detail.

Here are the main differences and how to adapt to the new format.

Legacy API	Differences
API Keys & Security	Naxai doesn't use a single API Key for security. By default, the API uses OAuth2 as a security schema. If you are unable to use OAuth2, you can pass credentials in the headers. On Naxai, you can create up to 10 API Credentials. Compared to the legacy platform, the API Credentials can be used for all services. When you had to call the Message API and Voice API on the legacy platform, you had to use distinct API keys. On Naxai, you can use the same set of credentials for all API calls. Check the authentication section of our
Webhook Limitations	In the Legacy API, only one Webhook configuration was allowed. Naxai allows you to create up to 10 webhook configurations, each with options to select which events you want to receive. Webhooks Subscription can also be created programmatically. See Webhooks for more details.
XML Support	Bye Bye XML; XML is no longer supported on Naxai
GET Request	Naxai no longer supports the GET method with query string parameters; you must use the POST method.
To	The legacy API uses a comma-separated list for destination phones. Naxai will use a JSON array.
From	On legacy API, you setup a from number that you need to know, you still have the possibility to use a From number on Naxai but we have added the possibility to use a Sender Service. A Sender Service acts as a router that will use the best From number based on the destination. It's very useful when you need to send messages to different destination's countries.
Idempotency Key	On Naxai, we have introduced the concept of an idempotency Key (optional). It will protect the system against sending duplicate messages. If you send a message with idempotencyKey = "1111" and you try to send another message with the idempotencyKey = "1111" in the next 24 hours, then your message will be rejected. It protects your system from sending duplicate messages when you don't get a response from our API endpoint. We recommend that you use a unique identifier, such as a UUID, ULID, KSID, or NanoID.
Calendars	You can use a Calendar to restrict the time window when messages can be sent. Please note that Calendar does not block messages; it reschedules them to the next available window.
Length of messages	On Naxai, you can control message length by setting a limit on SMS parts and deciding whether to truncate the message. If your message exceeds maxParts and truncate is set to false, it will not be sent. If truncate is set to true, your message will be sent, but it will be truncated into maxParts SMS parts. It allows you to control your budget and avoid sending too long messages.
Scheduling of messages	On Naxai, we have limited message scheduling to 7 days when using the API. Let us know your use case if you need an extended period. Note that messages scheduled within 5 minutes are sent immediately.
Rate Limiter	Naxai comes with a new Rate Limiting service with different values (see Rate Limits)
HTTP Response	On Naxai, you will receive a 202 Accepted response. Our new API is faster than the legacy API and can process many more messages simultaneously.
Response Body	The New Naxai API will return only an array of message identifiers, along with the number of messages processed. You will get details about the messages, including their status, via Webhooks.
Documentation	The documentation for the new Naxai Developers API Reference lets you test it directly from the docs and provides the necessary source code in more than 20 programming languages.

Comparing API Requests

Legacy RingRing SMS API

API endpoint: https://api.ringring.be/sms/v1/message
The API Key was sent in the body payload.

{
"apiKey": "YOUR_API_KEY",
"to": "32485123456",
"message": "Hello World!"
}

{
"MessageCount": 1,
"Messages": [
{
"MessageId": "UNIQUE-MESSAGE-ID",
"To": 32485123456,
"ResultCode": 0,
"ResultDescription": "Success"
}
],
"ResultCode": 0,
"ResultDescription": "Success",
"NumberOfParts": 1,
"NumberOfChars": 36,
"MessageEncoding": "TEXT"
}

Naxai API

API Endpoint: https://api.naxai.com/sms/send

You need to use the token retrieved with the OAuth2 endpoint or send the credentials in the headers.

{
  "to": [
    "32485123456"
  ],
  "body": "Hello World!"
}

{
  "count": 1,
  "messages": [
    {
      "messageId": "30a561b6-a558-4599-95d0-6a73872c6f37",
      "to": "32485123456"
    }
  ]
}