Step-by-Step Guide

Follow these steps to integrate your SMSAPI account:

 

Configure Callback URL

1. Sign in to your SMSAPI account.
2. Navigate to Settings → Callback URLs.
3. Add the following SMS DLR Callback URL:

   https://api.aretonet.com/api/smsApi/update  
   

Generate API Token

1. In SMSAPI, go to Settings → API Tokens.
2. Generate a new API token.
3. In your CRM account, go to Settings → SMS Settings.
4. Add the SMSAPI token to complete the integration.

The following limitations are based on SMSAPI documentation:

• A single SMS can contain up to 160 characters when using standard characters.
• If at least one special character is used (e.g., Polish letters), the limit reduces to 70 characters per SMS.
• SMSAPI supports concatenated messages of up to:
  • 918 characters (standard characters).
  • 402 characters (if special characters are included).
• Messages exceeding 160 characters will be split and billed accordingly.

For more details on special characters and encoding, refer to Chapter 9 of the SMSAPI documentation.

 

Configuring a Custom Sender Identifier

A custom sender identifier ensures that customers recognize messages from your brand instead of receiving messages from a random phone number.

Example

• Default Sender: +17111111111
• Custom Sender: ARETO NET

Steps to Set Up a Custom Sender Name

1. Sign in to your SMSAPI portal account.
2. Navigate to SMS Messages (left menu) → Sender Names.
3. Add a custom sender name (maximum 11 characters, avoid spaces).
4. Wait for SMSAPI approval.
5. Once approved, configure the custom sender name in:
   • CRM Global Settings (Settings → SMS)
   • Campaign Preferences (allows different sender names per campaign)

Important Note:

• Custom sender identifiers may not be supported in all countries, including USA and Canada.
• For further information, contact SMSAPI support.

While the CRM account is in test mode during integration, messages will be:

• Sent in test mode (if supported by SMSAPI).
• Not delivered to mobile devices.

This ensures safe testing before live deployment.