Guidance on API Password Composition at


At, we are dedicated to ensuring a seamless interaction with our SMS API platform, which involves promoting effective practices for security without compromising on functionality. One common query we encounter pertains to the use of special characters in API passwords. Here’s our advice grounded on best practices:


  • Special Characters in API Passwords – Not a Preferred Choice:

While creating an API password, it's advisable to avoid the use of special characters. Despite being commonly employed for enhanced security, special characters could potentially interrupt message encoding processes within the API, thereby causing unforeseen issues.

  • Favorable Password Practices:

Opt for a strong password by incorporating a mix of uppercase letters, lowercase letters, and numerals. A robust password is your first line of defense against unauthorized access, ensuring the sanctity and security of your messaging operations.

  • Stability and Reliability:

Our recommendation against special characters is rooted in our endeavor to offer a stable and reliable messaging platform. By adhering to this guideline, you foster a conducive environment for hassle-free API interactions.

  • Support and Documentation:

Explore our comprehensive documentation to delve into our detailed SMS Developer section or to reach out our support team for assistance. Your successful engagement is our utmost priority.


At, we continually strive to simplify the complexities, offering you a streamlined, secure, and efficient platform for all your SMS messaging needs. Following our guidelines on password creation ensures you leverage the full potential of our platform while maintaining a secure and reliable communication channel.