Hi @elisa.zoom this is a follow up to this previous thread.
I’ve got my server-to-server application running. It’s fairly simple. All the app does is takes incoming sms from zoom and posts certain messages to slack. I don’t need to send outgoing sms.
It is all working perfectly when I have the phone number I’m using for this attached to a user account. However, I’d prefer to have it attached on an account level rather than associated with a user, so that it’s obvious that it should not be reassigned or deleted.
I initially thought that the way to do this would be to attach the number on the admin menu under Phone System Management - Programmable APIs.
That “Programmable APIs” config page allows attaching the phone number, and provides a “Service endpoint ID”, although I still haven’t been able to find any documentation on what exactly that is or how to use it. (That was the question in my original post, although I realise I wasn’t clear that I was asking about that specifically and not the phone api’s in general.) That doesn’t work though - when the number is attached there, the webhook is not triggered.
I’ve also tried various other options such as attaching the number to an auto receptionist or call group - those also don’t seem to trigger the webhook.
So, my question is, what’s the right way to attach a number in order for sms messages to that number to trigger the webhook, without attaching it to an individual user? If one of the options I’ve already tried should work, are there specific scopes that have to be active for that to work?
Thanks for your help.