Sinch Community

Artificially Inflated Traffic (AIT) is a type of SMS fraud that happens when fraudsters generate high volumes of fake traffic via mobile applications or websites.    A common AIT scenario looks something like this:   A fraudster designs a bot to create fake accounts.   The bot triggers a one-time passcode (OTP) SMS to mobile numbers.  The fraudster partners with a rogue party to intercept the inflated traffic without actually delivering messages to the end user.  Together, they claim the revenue, share the profits...  … and repeat the process to inflate revenues further or tamper with conversion statistics.  To learn more about AIT and what can be done about it - read the full blog post on sinch.com.   Take a look at the Sinch SMS Product page to learn more about our SMS products, or click here to sign up to our self-service portal and get started today. ... View more

In order to port your toll-free number (TFN) to Sinch, complete the attached Sinch Letter of Authorization and send to your Sinch Account Manager, or contact Sinch if you have any questions. ... View more

For developers integrating Numbers functionality into their app, Sinch SDKs provide a convenient alternative to the Numbers REST API.   Sinch SDKs offer a consistent standardized framework for functionality to address problems like pagination, error code response and language familiarity regardless of the underlying API setup. For example, two common approaches to pagination are page-based and token. Depending on the API, there are pros and cons to each approach. However, in our SDKs, we provide a single iterator object you can use to parse through your results.   Our client is centralized around a single authentication model, ensuring support for all actively supported language versions, and reducing reliance on third-party libraries.   The Numbers SDK allows you to quickly start interacting with the Sinch Numbers API using your favorite programming languages. Currently we support the following languages: Node.js Python Java .NET For more information about our SDKs visit the Sinch SDK Overview page. ... View more

Note: This article provides information related to the standalone SMS API and corresponding SDK. New customers will access SMS functionality through Sinch's Conversation API. To learn more about Conversation API and the corresponding SDK, visit the SDK section of the Sinch Developer Documentation.   For developers integrating SMS functionality into their app, Sinch SDKs provide a convenient alternative to the SMS REST API. Sinch SDKs offer a consistent standardized framework for functionality to address problems like pagination, error code response and language familiarity regardless of the underlying API setup. For example, two common approaches to pagination are page-based and token. Depending on the API, there are pros and cons to each approach. However, in our SDKs, we provide a single iterator object you can use to parse through your results. Our client is centralized around a single authentication model, ensuring support for all actively supported language versions, and reducing reliance on third-party libraries. The SMS SDK allows you to quickly start interacting with the Sinch SMS API using your favorite programming languages. Currently we support the following languages: Node.js Python Java .NET *If you'd like to get started using the legacy Java SDK, click here. For more information about our SDKs visit the Sinch SDK Overview page. ... View more