PinnacleSMSplugin 1.0.1
dotnet add package PinnacleSMSplugin --version 1.0.1
NuGet\Install-Package PinnacleSMSplugin -Version 1.0.1
<PackageReference Include="PinnacleSMSplugin" Version="1.0.1" />
<PackageVersion Include="PinnacleSMSplugin" Version="1.0.1" />
<PackageReference Include="PinnacleSMSplugin" />
paket add PinnacleSMSplugin --version 1.0.1
#r "nuget: PinnacleSMSplugin, 1.0.1"
#addin nuget:?package=PinnacleSMSplugin&version=1.0.1
#tool nuget:?package=PinnacleSMSplugin&version=1.0.1
Pinnacle SMS Plugin
Pinnacle sms plugin official library is useful to helps you in sending sms.
Every function contains common parameters for authentication i.e. apikey You can provide apikey via request parameter to send SMS.
For API Key You will have to create an account with Pinnacle Teleservices PVT LTD. (https://console.pinnacle.in/) Once you create an account with Pinnacle you can obtain the api key from the email with all the credentials . The same can be used for your specific app or if you are testing with the sandbox application.
SEND SMS
Parameter Name | Parameter Description |
---|---|
apikey | It will be generated by admin and send to members as per requirement via email |
Payload | It is a json payload |
Parameters
Parameter Name | Parameter Description |
---|---|
sender | Sender name must be 6 alpha characters and should be pre-approved by Pinnacle. |
umbers | Comma-delimited list of mobile numbers in international format (i.e. 918123456789). Maximum of 10,000 numbers are allowed. |
message | The message content. This parameter should be no longer than 2000 characters. The message also must be URL Encoded to support symbols like &. |
messagetype | Message Type should be defined as per the type for example: TXT, UNI, USSD and etc |
scheduledate | This parameter can be used to specify a schedule date/time for your message, which should be provided in Unix timestamp format(YYYY-MM-DD HH:MM:SS). Times should be provided in GMT. |
extrares | This parameter can be used to store extra parameters for your message, which should be provided as alphanumeric. |
clientuid | This parameter can be used to store unique id sent by client. |
dltentityid | This parameter can be used to store a DLT EntityID for your message. |
dltheaderid | This parameter can be used to store a DLT HeaderID for your message. |
dlttempid | This parameter can be used to store a DLT TemplateID for your message |
dlttagid | This parameter can be used to store a DLT Consent ID for your message |
tmid | This parameter is DLT Telemarketer ID for your message |
1) Single number request
{
"sender": "<SENDER>",
"message": [
{
"number": "<91xxxxxxxxxx>",
"text": "<Your Message>"
}
],
"messagetype": "TXT",
"dlttempid": "<DLT Template ID>"
}
OR
{
"sender": "<SENDER>",
"message": [
{
"number": "<91xxxxxxxxxx>",
"text": "<Your Message>"
}
],
"messagetype": "TXT",
"dltentityid": "<DLT EntityID>",
"dlttempid": "<DLT Template ID>",
"dltheaderid": "<DLT Header ID>",
"dlttagid": "<DLT Tag ID>",
"tmid": "<Telemarketer ID>"
}
2) Multiple number request
{
"sender": "<SENDER>",
"message": [
{
"number": "<91xxxxxxxxx1>,<91xxxxxxxxx2>,<91xxxxxxxxx3>,......,<91xxxxxxxxxx>",
"text": "<Your Message>"
}
],
"messagetype": "TXT",
"dlttempid": "<DLT Template ID>"
}
3) Multiple number request with single template id
{
"sender": "<SENDER>",
"message": [
{
"number": "<91xxxxxxxxx1>",
"text": "<Your Message 1>"
},
{
"number": "<91xxxxxxxxx2>",
"text": "<Your Message 2>"
},
{
"number": "<91xxxxxxxxx3>",
"text": "<Your Message 3>"
}
],
"messagetype": "TXT",
"dlttempid": "<DLT Template ID>"
}
4) Multiple number request with multiple template id
{
"sender": "<SENDER>",
"message": [
{
"number": "<91xxxxxxxxx1>",
"text": "<Your Message 1>",
"dlttempid": "<DLT Template ID 1>"
},
{
"number": "<91xxxxxxxxx2>",
"text": "<Your Message 2>",
"dlttempid": "<DLT Template ID 2>"
},
{
"number": "<91xxxxxxxxx3>",
"text": "<Your Message 3>",
"dlttempid": "<DLT Template ID 3>"
}
],
"messagetype": "TXT"
}
5) For regional language
For regional language we have to write "messagetype":"UNI".
{
"sender": "<SENDER>",
"message": [
{
"number": "<91xxxxxxxxxx>",
"text": "<Your Message>"
}
],
"messagetype": "UNI",
"dltentityid": "<DLT EntityID>",
"dlttempid": "<DLT Template ID>",
"dltheaderid": "<DLT Header ID>",
"dlttagid": "<DLT Tag ID>",
"tmid": "<Telemarketer ID>"
}
Common Function for calling the Plugin for Sending Message:
using WrapperSMS;
using Newtonsoft.Json;
Pinnacle_SMS_Wrapper Pinobj = new Pinnacle_SMS_Wrapper();
string json = <JSON payload or JSON file path> ;
string jsonResult = JsonConvert.SerializeObject(json);
string apikey ="<API Key>";
string finalResult="";
string apikey ="<API Key>";
finalResult = Pinobj.send_sms(apikey, jsonResult );
Pinnacle Support
Call +91 83088 00004, +91 83088 00005 or email at support@pinnacle.in
Product | Versions Compatible and additional computed target framework versions. |
---|---|
.NET | net5.0 was computed. net5.0-windows was computed. net6.0 was computed. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
.NET Core | netcoreapp2.0 was computed. netcoreapp2.1 was computed. netcoreapp2.2 was computed. netcoreapp3.0 was computed. netcoreapp3.1 was computed. |
.NET Standard | netstandard2.0 is compatible. netstandard2.1 was computed. |
.NET Framework | net461 was computed. net462 was computed. net463 was computed. net47 was computed. net471 was computed. net472 was computed. net48 was computed. net481 was computed. |
MonoAndroid | monoandroid was computed. |
MonoMac | monomac was computed. |
MonoTouch | monotouch was computed. |
Tizen | tizen40 was computed. tizen60 was computed. |
Xamarin.iOS | xamarinios was computed. |
Xamarin.Mac | xamarinmac was computed. |
Xamarin.TVOS | xamarintvos was computed. |
Xamarin.WatchOS | xamarinwatchos was computed. |
-
.NETStandard 2.0
- No dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.