Zoom Phone

Zoom Phone Emergency Service Locations API

The Emergency Service Locations API from Zoom Phone — 3 operation(s) for emergency service locations.

GitHub OpenAPI
Business capability
Emergency Services Management BC-2700.40

Operations 6

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

POST /phone/batch_locations Add emergency service locations in bulk · Batch add emergency service locations #
Ask an LLM
“Can I upload many emergency service locations in one request?”
“How do I bulk-load a site's emergency locations?”
Tell an agent
Batch add emergency locations {locations}.
Bulk add emergency service locations {locations} to site {site_id}.
GET /phone/locations List emergency service locations · List emergency service locations #
Ask an LLM
“Which emergency service locations are defined on our account?”
“Do I need a site ID to list emergency locations when multiple sites are on?”
Tell an agent
List all emergency service locations.
List emergency locations for site {site_id}.
POST /phone/locations Add an emergency service location · Add an emergency service location #
Ask an LLM
“How do I add a single emergency location tied to a network?”
“Can an emergency location match on BSSID or IP address?”
Tell an agent
Add emergency location {name} at emergency address {emergency_address_id}.
Add location {name} for address {emergency_address_id} matched by BSSID {bssid}.
GET /phone/locations/{locationId} Get an emergency service location · Get emergency service location details #
Ask an LLM
“What network details does one emergency location use?”
“Where can I check a single emergency service location?”
Tell an agent
Show emergency location {locationId}.
Get the network match details of location {locationId}.
DELETE /phone/locations/{locationId} Delete an emergency service location · Delete an emergency location #
Ask an LLM
“Can I remove an emergency location we no longer use?”
“What deletes one emergency service location?”
Tell an agent destructive · confirm first
Delete emergency location {locationId}.
Remove emergency service location {locationId}.
PATCH /phone/locations/{locationId} Update an emergency service location · Update emergency service location #
Ask an LLM
“How do I change the IP range or BSSID of an emergency location?”
“Can I point an emergency location at a different address?”
Tell an agent
Rename emergency location {locationId} to {name}.
Set emergency location {locationId}'s public IP to {public_ip}.

Documentation

📖
Documentation
https://developers.zoom.us/docs/api/phone/
📖
APIReference
https://developers.zoom.us/docs/api/phone/
📖
Documentation
https://developers.zoom.us/docs/integrations/oauth/
📖
Documentation
https://developers.zoom.us/docs/api/phone/events/
📖
APIReference
https://developers.zoom.us/docs/api/phone/events/
📖
Documentation
https://developers.zoom.us/docs/api/number-management/
📖
APIReference
https://developers.zoom.us/docs/api/number-management/

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/zoom-phone/refs/heads/main/openapi/zoom-phone-emergency-service-locations-api-openapi.yml

Other Resources

🔗
PostmanCollection
https://www.postman.com/zoom-developer/zoom-public-workspace/documentation/uba96fr/phone

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/zoom-phone:zoom-phone-emergency-service-locations-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

zoom-phone-emergency-service-locations-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Phone Emergency Service Locations API
  description: 'You can access information from Zoom with Zoom Phone APIs to build private services or public applications on the Zoom App Marketplace.


    To learn how to get your credentials and create private or public applications, see Zoom APIs use OAuth 2.0 authorization.


    All endpoints are available through `https` at `api.zoom.us/v2/`. For instance, `https://api.zoom.us/v2/users/` returns all users on an account. You''ll receive a `403` error message if you have not set up Zoom Phone.'
  termsOfService: https://zoom.us/docs/en-us/zoom_api_license_and_tou.html
  contact:
    name: Zoom Developers
    url: https://developer.zoom.us/
  version: '2'
servers:
- url: https://api.zoom.us/v2
tags:


# --- truncated at 32 KB (77 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/zoom-phone/refs/heads/main/openapi/zoom-phone-emergency-service-locations-api-openapi.yml