-
Notifications
You must be signed in to change notification settings - Fork 96
HSM Start: Invalid JSON #129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I also got the "Got an invalid JSON response from the server" error. I'm trying to replace an old solution we have in place in the company, which is still running on the old legacy API (on PHP 5.6.40), with a new version of the solution based on the REST API but so far I'm hitting this blocker... The new version I'm trying to set up is running on a Windows 2012 R2 x64 server with IIS 8.5 with PHP 7.4.10 on it. Because of the company network I need to define the proxy to channel the traffic directly outside, just like with the old legacy API. My code to check the credit balance, to see if the REST API is working fine, is the following:
The full dump of \Exception $e is:
Line 16: Like you I'm stuck at the moment as I also don't see other hints in the PHP logs on the server. P.S. If these 2 topics are unrelated then I'm happy to create a new topic for it. |
Maybe is a little late, but could help someone. Check the parameters |
Closing this as a part of issue cleanup. |
Hello.
We've tried using the SDK to send a WhatsApp HSL message. To do this we've used the
create-hsm
example from the example folder. However, it will throw an exceptionJSON is not a valid format
. Then I got looking and found out that this issue is already known for the conversation API. We're using start and not create (Which was the possible fix in the other issue) #95When we use create instead of start the error gets even funnier.
Got an invalid JSON response from the server
. I have a feeling that the SDK is not running things correctly, but it can be our stupidity too. I've attached the code.The text was updated successfully, but these errors were encountered: