Discussions

We have a production oauth API set up with webhooks and events being created when SMS are sent through Dialpad. We successfully set this up using the account with which the API key is registered.
We have since had someone with a separate Dialpad account use our process to register a webhook and event so that we can log SMS sent by their account.
When I log in using our Dialpad account and run a SMS Event list or a Webhook list API call, I only see my own events, no events that would have been created when the new user registered a new webhook/event. Should I be able to see all webhooks/events using that API, or just the ones using the account which I used to generate a token?
At this stage, it looks to me like a webhook and event were set up, but I have no way of verifying this.
Are you able to confirm that there is a webhook and event with the secret starting 83 and ending Cp using the API key starting ctWj and ending PQSy4.
The dialpad account that owns this api key is riacomp.

I was looking at the page below and it wasn't clear to me if the registered web hook will be called immediately once a call is connected?

What happens to event subscriptions (Call, SMS) when their associated webhook is deleted?

Tried C# and now PowerShell. Attempting to automate daily download of calls. Sending Invoke-WebRequest which returns request_id just fine (every time). Then use the request_id to get results...sometimes it only returns 200 "status": "processing" and other times it returns "download_url" as expected. When the "status": "processing" is returned, it of course bombs out the rest of the script which opens the download_url to save the file.

Is it possible to SMS from a Toll-free number?

Our account has numbers assigned to Call Centers, but individual users do not have numbers assigned.

I'm trying to add contacts through API, rather than thru the app to make it available for everyone in an office, but it doesn't accept commas. It will submit with only the number

Hi!

Hi team,

In the contacts (v2) API, there is a PUT (aka "Create or Update") call which requires a UID in the body. The doc for the call describes the UID as "The unique id to be included as part of the contact's generated id." This makes it sound like the UID is not the actual ID but somehow controls the ID calculation. But in fact doing two consecutive PUTs with the same UID in the body does not update the contact created by the first call; the second call returns a contact with a new ID entirely. And using the ID of a contact in the UID of a PUT does not cause that contact to be updated, instead a new contact is created with a different ID.