SARoadrunners
Occasional Contributor
since ‎04-20-2024
‎05-02-2024

User Statistics

  • 6 Posts
  • 0 Solutions
  • 1 Kudos given
  • 3 Kudos received

Re: Unexpected JSON received by SMS delivery report hook and no client_reference when send had one.

by in Developer Forum
‎05-01-2024 11:55 AM
1 Kudo
‎05-01-2024 11:55 AM
1 Kudo
FWIW I also now have the client_reference working.  In the process of integrating code our Database admin changed the data type of the value I was putting into the client_reference from string to binary.  The binary value evaluated to 1 or true.  Once I adapted to the data change, your handing of client_reference worked as expected.  My team's mistake again. ... View more

Re: Unexpected JSON received by SMS delivery report hook and no client_reference when send had one.

by in Developer Forum
‎04-30-2024 07:48 AM
2 Kudos
‎04-30-2024 07:48 AM
2 Kudos
That helps alot!  I am using per_recipient_final in my send request.   When I moved my code from a simple stand alone app into my much larger production code, I must have inadvertently change the delivery_report.  My mistake.  Thanks for your help.   ... View more

Re: Unexpected JSON received by SMS delivery report hook and no client_reference when send had one.

by in Developer Forum
‎04-30-2024 06:51 AM
‎04-30-2024 06:51 AM
The main part of my question was that the JSON format and content of the delivery report webhook for "recipient_delivery_report_sms" suddenly didnt match the documents.    What JSON format should I expect going forward for the delivery report webhook - the format I received recently and posted above -or- the one documented that contains a statuses array??? I have already refactored my code to validate the client_reference field to be sure it's what I expect and not to rely on it so that is not an issue for me.  The JSON to expect in the delivery report hook is an issue. ... View more

Unexpected JSON received by SMS delivery report hook and no client_reference when send had one.

by in Developer Forum
‎04-29-2024 06:30 AM
‎04-29-2024 06:30 AM
New JSON format received by delivery report hook and didnt have client_reference which my code depended on.  Client reference was sent.  JSON format didnt match docs so broke my code.  How many more variations are there? {"at":"2024-04-28T22:56:13.840Z","batch_id":"01HWKERMJ8MZKH0YYJPZ6A5ZNZ","client_reference":"true","code":0,"operator_status_at":"2024-04-28T22:56:00Z","recipient":"12103173758","status":"Delivered","type":"recipient_delivery_report_sms"}   Previously, even if batch had only 1 number in it, the delivery hook JSON would contain a statuses array which contained a recipients array containing just one number as currently documented. FWIW I'm using PHP. so... 1. Are there any other JSON variations I should code for? 2. Why was client_reference set to true?  A 32 char hex string was set as client_reference when the SMS was sent.  I'll need to restructure my code if client_reference isn't going to work any more. ... View more
Labels:

Re: Block SMS replies

by in Discussion Forum
‎04-22-2024 09:32 AM
‎04-22-2024 09:32 AM
When I click on the 1-way numbers for SMS link, I get a page saying I'm not authorized.  Can you tell me how I can learn more about 1 way SMS numbers? ... View more

Block SMS replies

by in Discussion Forum
‎04-20-2024 01:27 PM
‎04-20-2024 01:27 PM
For my use case, I am sending 1x a race discount code via text to someone who has earned it and requested it.  No subscription.  1X.  So, I'm not interested in monitoring replies.  No 'stop' handling needed.  Is there a way to block users from sending messages to my Sinch number?  Dont want to be charged for replies or for replying to replies. In essence I'd like an outgoing number only.  Does that exist?  Can Sinch supply? ... View more
Labels:

User Activity

Unexpected JSON received by SMS delivery report hook and no client_reference when send had one.

04-29-2024
New JSON format received by delivery report hook and didnt have client_reference which my code depended on. Client reference was sent. JSON format didnt match docs so broke my code. How many more variations are there? {"at":"2024-04-28T22:56:13.840Z"...

Block SMS replies

04-20-2024
For my use case, I am sending 1x a race discount code via text to someone who has earned it and requested it. No subscription. 1X. So, I'm not interested in monitoring replies. No 'stop' handling needed. Is there a way to block users from sending mes...
Kudos given to