Continuing the discussion from Is it possible to include '\n' in SMS-ovef-IP using the Embedded API?:
How do you create a newline char when using the (deprecated but not dead) “SMS-over-IP” embedded endpoint?
Solution provided by Reuben:
Ok so the docs apparently never reflected reality here. We’ve always taken a single newline on the SMS endpoint to end the connection.
We’re going to leave that in place, but now you can send the characters
\n (not an actual newline) to create a newline in the message.
Let us know if that gives you any trouble.
We’ll update the docs with this information soon.
In my testing, this same solution seems to apply to sending newlines using the “Send a Message to the Hologram Cloud” embedded endpoint. Is that expected/known? I’m hoping that this embedded endpoint is a very highly-used part of the Hologram system… is that true? I have probably tried your patience over the months asking about the longevity of the deprecated but not dead “SMS-over-IP” embedded endpoint, so with significant effort I have switched to using this endpoint + Twilio for sending SMSs. I’m hoping that this will ensure that my hardware product will have a long lifespan.
I’m hoping you can calm my fear that the “Send a Message to the Hologram Cloud” embedded endpoint will be deprecated or go the same way as the SMS-over-IP embedded endpoint… Thanks!