Need help understanding an error when updating emergency service location

API Endpoint(s) and/or Zoom API Event(s)
phone/locations

Description
I am attempting to troubleshoot an error that happens when attempting to update an existing emergency service location via the zoom API. I am calling

PATCH https://api.zoom.us/v2/phone/locations/:locationId

with body json

{
“bssid”:“D0:D3:E0:B0:23:C3”,“emergency_address_id”:“6Z27P_V_SI2tTe3G-ywlvw”,“name”:“7th St Café”,“private_ip”:“111.29.0.0/32”,“public_ip”:“111.82.0.0/32”,“minimum_match_criteria”:false,“network_switches”:[{“mac_address”:“q4:bd:9e:ff:21:00”,“port”:null,“port_prefix”:null,“port_range_from”:null,“port_range_to”:null}],“sip_group_id”:null,“elin_phone_number_id”:null
}

The only field that is actually changing is the emergency_address_id. If I run the request in postman I get an error saying that “Only the company address can be used for the company location.“ . I have verified that the value being passed for emergency_address_id points to an existing emergency address. All the required fields appear to be present in the body. What am I doing wrong?

Error?
{
“code”: 400,
“message”: “Only the company address can be used for the company location.”
}

Hi @ptb014 , when you call get emergency service location details can you verify you get the same exact details (aside from the new emergency_address_id) that you’re passing through to the update request?

Is the new emergency_address_id compatible with this update change? How is it generated? If you’re taking it from another location id, make sure you’re grabbing this value:

Looking at the data again, the bssid is also being updated. All of the other fields remain the same. However, even if I remove the bssid field from the incoming data, I still get the same error.

Hi @ptb014 please answer these questions.

I’m not quite sure what you mean by “compatible with this update change“. I have confirmed that the new emergency_address_id value corresponds with an id value for an existing emergency_address.

Thank you for confirming how you’re sourcing the emergency_address_id value @ptb014 . Can you please open a support ticket with the following:

  • client id
  • zm-tracking-id from response header
  • link to this post
  • description of the issue

Support will be able to look at your account to view account-specific details to better determine the address information resulting in the error with the API. If you run into the issues with getting help with support, please let me know. Please also let us know the resolution on this thread to help the broader developer community :slight_smile:

1 Like

With the help of tech support, I understand what is happening now. Note in the images above, the emergency_address we are trying to associate with the location contains an ‘owner’ object. Because it contains this data, Zoom treats the emergency address as an individual rather than a ‘company’ address.

I’m not sure where (if anywhere) this requirement is documented. I really wish there was documentation somewhere that listed all the validation rules for each API endpoint and their associated error messages.

Ah okay thanks @ptb014 !

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.