Replies: 2 comments
-
The click send API works as advertised when using cURL. I've now created my own ClickSend Transport with an extended Notification class to call it from. All working well with Messenger. If you end up here then I suggest don't use the Symfony Click Send Notifier as it's not in any way correctly configured for their API. Presumably the API has changed at some point and this repository is now out of date or I could have missed some part of the setup of course. |
Beta Was this translation helpful? Give feedback.
-
I have the same issue, the structure sent is not correct. Symfony is sending something like {\n
"source": "php",\n
"from": "xxxx",\n
"body": "Hello World",\n
"to": "+41xxxxxxx",\n
} but it should be {\n
"messages": [\n
{\n
"source": "php",\n
"from": "xxxx",\n
"body": "Hello World",\n
"to": "+41xxxxxxx",\n
}\n
]\n
} I'll send a patch |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I am trying to get the Click-send notifier/texter to work and it seems as if what is being submitted to the API is the wrong format and hence I get a 400 response.
Basic test controller:
composer.json
notifier.yaml
On the symfony profiler the https request that is sent by texter is shown as:
Which I don't think matches the Click-Send API format which expects an array of 'messages' which then contain the one or more message details.
The response back is:
Any ideas on what else needs setting up to get this to work?
Next I will be trying it with cURL but would really prefer to have this working as integrated with other channels under notifier.
Thanks
Mark
Beta Was this translation helpful? Give feedback.
All reactions