Sorry, you need to enable JavaScript to visit this website.

You are here

.NET SDK

2 posts / 0 new
Last post

Kieran's picture
by Kieran

.NET SDK
Hi, I have a number of observations about the Message API and .NET SDK
  1.  The ScheduledDelivery has to be > 0, which means not that useful for two factor auth as minimum wait time for a message is 1 minute  
  2. If the ScheduledDelivery is greater than the Validity, the message will never be sent/received (sometimes even when they have the same value it won't be sent/received). I thought the Validity time would start from when it's Scheduled to be sent, not when the API call is made, if this is how intended that's ok but it doesn't seem not that intuitive to me.  
  3. GetSMSStatus and GetSMSStatusAsync always return a cast error. For example: TelstraMessagingAPI.Standard.Exceptions.APIException : Failed to parse the response: Unable to cast value PEND to enum type Nullable`1 TelstraMessagingAPI.Standard.Exceptions.APIException : Failed to parse the response: Unable to cast value EXPIRED to enum type Nullable`1
 

DeveloperSteve's picture
by DeveloperSteve

Hi Ko, 

Hi Ko

Thanks for the feedback, ill pass that onto the messaging team and get it added in for some of our next lot of releases. 

Re the SDK error, ill raise a bug and investigate further. There is new versions of the SDKs that will likely push in the next few days. 

Log in or register to post comments