Phone Com
Phone.com is a cloud business phone and unified communications provider for small and mid-sized businesses, offering VoIP calling, SMS/MMS, video conferencing, fax, and virtual phone numbers. Its developer platform is the JSON REST v4 API (codenamed "Phoenix") at api.phone.com, which gives programmatic control over accounts, extensions, devices, phone numbers, call routing (routes, menus, queues, schedules), media, messaging, and an event callback/listener webhook system. Authentication is OAuth 2.0. First-party SDKs are published for Go, Python, PHP, Android, and JavaScript. Surfaced as a portfolio company of Lightspeed Venture Partners and enriched into the API Evangelist network.
Phone Com publishes 68 API contracts indexed on the APIs.io network, including 10 DLC API, Access Tokens API, Account Contacts API, and 65 more. Tagged areas include Company, VoIP, Telephony, Business Phone, and SMS.
The Phone Com catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 1 Spectral governance ruleset.
Phone Com’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 34 more developer resources.
2 published contracts
Business capabilities this provider's published APIs can perform, derived from its own
contracts. Browse all capabilities →
Individual APIs this provider publishes, each with its own machine-readable definition.
10 DLC registration is required for SMS messaging
Allows you to manage access tokens issued for your account.
Contact which can be used for different needs, such as ordering devices
This page gives an overview of how to interact with your accounts.
Information about API usage statics.
We save API errors related to your account so you can analyze issues if for some reason you don't log error responses in your application
Phone.com created the async-call-logs API endpoint to allow customers to download large amounts of call logs without encountering the normal Phone.com API Rate Limits. This serv...
This service lists phone numbers that are available for purchase through Phone.com.
The Blocked Calls API allows users block incoming calls from specific phone numbers. If only a part of a telephone number is provided, calls with callers ID matching the pattern...
The Call Logs API returns a list of call detail records for the account. The result includes the id, start time, creation time, caller ID, called number, direction of call, and ...
Aggregated calls statistics
API users with Extension scope access token does not have access to the Phone Number API. This API helps user to retrieve available account phone numbers to be used as caller id...
This API places a call to the caller phone number (or caller extension ID). If that number (or extension) answers within the timeout period, then the callee DID (or extension) w...
Phone.com API supports OAuth 2.0 Authorization Framework, which enables a third-party application (client) to obtain limited access to HTTP API requests. This page describes how...
Represents overview of your messaging history in messenger-like format.
Extension on your Phone.com account may have SIP devices associated with them. The Device API provides information about those SIP devices, such as the SIP credentials required.
Callbacks represent URLs on your side which will be called by our system when event occurs. Read more: https://github.com/phonedotcom/events-integration-doc
Callback invocations statistics
Combined representation of listeners, callbacks, profiles and subscriptions. Read more: https://github.com/phonedotcom/events-integration-doc
Listener is an entity that associates subscriptions with callbacks. Read more: https://github.com/phonedotcom/events-integration-doc
Filters functionality. If no filters defined, than all events will be processed. If filters defined, events should match all of them.
Defines what kind of events should generate a callback. Read more: https://github.com/phonedotcom/events-integration-doc
A Profile allows to specify a notifications email for a callback. Notifications are emitted when there is a need to notify the callback owner of some issues like timeouts, or de...
An Express Service Code is required when a customer calls Phone.com for support. With the following services, customer may retrieve the Express Service Code associated with his/...
The entries in an extension's address book can be divided into any number of groups. This page gives an overview.
Each extension at Phone.com can have an address book with any number of contacts.
Your Phone.com account will have one or more extensions.
Phone.com customers can fax outbound documents via the Control Panel or API; They can also receive incoming fax into one of the Extension mailbox. The Fax API service allows use...
Invoices also knows as billing statements. "billing-api" scope is required for the token
[DEPRECATED; use Events Listeners] At the heart of every telephony system is the Events Engine. At Phone.com, our customers (and their call traffic) emit millions of events per ...
With Live Receptionist and Phone.com, your business can now have its very own live answering service, adding versatility, flexibility, and availability to your company no matter...
Usage of live answer script by other Phone.com resources.
Information about available Live Answer vendors
Live Answer Vendor Tokens are required for some integrations
Your Phone.com account has two kinds of media that can be used in various ways: Hold Music and Greetings. Hold Music can be used in routes, queues, and anywhere the caller might...
Usage of media file by other Phone.com resources.
We've all been on the consuming side of a phone menu before. You call a company and hear, 'Press '1' for Sales. Press '2' for Support. Press '0' for the operator.' With Phone.co...
Phone.com’s standard phone service lets you send and receive SMS/MMS messages using your Phone.com numbers. The Phone.com API extends this functionality, letting you send SMS/MM...
The OAuth 2.0 Authorization Framework enables a third-party application to obtain limited access to HTTP API requests which require an access token. This page describes how to u...
History of the orders of physical devices
Phone.com accepts credit card payment, and the Account Payment Methods API allows users to add, list, get, update and delete a credit card payment method. "billing-api" scope is...
Allows to manage phone numbers reservations.
Your Phone.com account has one or more phone numbers registered to it.
[DEPRECATED] This interface allows you to try to obtain basic information about any phone number (CNAME, line type, etc)
Queues are used when you want to direct calls to a pool of phone numbers and/or extensions. A common utilization of queues is for Customer Service call centers. When a queue is ...
Queues are used when you want to direct calls to a pool of phone numbers and/or extensions. A common utilization of queues is for Customer Service call centers. When a queue is ...
The Account OAuth Clients API supports redirect-uri. Since an OAuth Client is created by a Phone.com admin who does not know what redirect uris should be assigned, API users may...
Routes, a.k.a. 'Call Handling Rules' or 'Presets', are used to tell Phone.com how to handle incoming phone calls. They can be used to connect your Phone.com phone number to an e...
API for managing postponed (scheduled) API requests. "scheduled-requests" scope is required for the token.
Schedules are used at various places in your Phone.com account. A schedule can specify a recurring weekly pattern such as 'Monday through Friday' or a single time period such as...
[DEPRECATED; use Messages] Phone.com’s standard phone service lets you send and receive SMS messages using your Phone.com numbers. The Phone.com API extends this functionality, ...
This page gives an overview of how to interact with your subaccounts. Subaccounts are the same as master accounts in terms of the functionality Phone.com supports. The main diff...
You can submit support request via API, it will be delivered to our API team
The System endpoints API from Phone Com — 2 operation(s) for system endpoints.
Transactions (charges, taxes, payments, etc.). "billing-api" scope is required for the token.
SIP Trunks are used to connect your Phone.com account to your PBX. NOTE: SIP Trunking Customers Only -- Your Phone.com account must have SIP Trunking enabled in order to use any...
Endpoints for managing scheduled video conferences
The Phone.com Video API allows an integrator to automate provisioning a complete cloud-based video conferencing system for a Phone.com account.
Token for integration with Video Conference service
Video-users are associated with Phone.com extensions. A video user is a collection of a domain name for the bridge id, a business name, and a plan which affects the bridge capab...
Phone.com’s standard phone service allows callers to leave a voicemail if the incoming call was not answered. The /voicemail services show a history of voicemail and allow users...
AsyncAPI definitions for this provider's event-driven and streaming APIs.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral governance rulesets for linting and validating these APIs.
Standalone JSON Schema definitions for this provider's data models.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
OAuth scopes governing access to this provider's APIs.
Recommended x-agentic-access execution contracts for AI agents.
aid: phone-com
name: Phone Com
description: Phone.com is a cloud business phone and unified communications provider for small and mid-sized businesses, offering
VoIP calling, SMS/MMS, video conferencing, fax, and virtual phone numbers. Its developer platform is the JSON REST v4 API
(codenamed "Phoenix") at api.phone.com, which gives programmatic control over accounts, extensions, devices, phone numbers,
call routing (routes, menus, queues, schedules), media, messaging, and an event callback/listener webhook system. Authentication
is OAuth 2.0. First-party SDKs are published for Go, Python, PHP, Android, and JavaScript. Surfaced as a portfolio company
of Lightspeed Venture Partners and enriched into the API Evangelist network.
url: https://raw.githubusercontent.com/api-evangelist/phone-com/refs/heads/main/apis.yml
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: self-serve
trial: false
try_now: false
public: false
label: Self-serve signup
confidence: medium
source:
- authentication
generated: '2026-07-22'
method: derived
image: https://github.com/phonedotcom.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- lightspeed-venture-partners
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-10-06'
x-docs-platform: readme
x-docs-platform-confidence: high
x-docs-platform-checked: 2026-10-04
tags:
- Company
- VoIP
- Telephony
- Business Phone
- SMS
- Video Conferencing
- Communications
tags_raw:
- Company
- VoIP
- Telephony
- Business Phone
- SMS
- Video Conferencing
- Communications
- API
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: CapabilityMap
url: capabilities/phone-com-capability-edges.yml
name: Phone Com Business Capability Map
- type: AgenticAccess
url: agentic-access/phone-com-agentic-access.yml
- type: Spectral
url: rules/phone-com-rules.yml
- type: JSONLD
url: json-ld/phone-com-context.jsonld
- type: Vocabulary
url: vocabulary/phone-com-vocabulary.yml
- type: ErrorCatalog
url: errors/phone-com-problem-types.yml
- type: Hosts
url: hosts/phone-com-hosts.yml
- type: IntegrationEdges
url: integrations/phone-com-integration-edges.yml
- type: Vendors
url: vendors/phone-com-vendors.yml
- type: Leadership
url: https://www.phone.com/leadership/
- url: https://www.phone.com/feed/
type: BlogRSS
- type: Website
url: https://phone.com
- type: DeveloperPortal
url: https://apidocs.phone.com/
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: Support
url: https://support.phone.com/
- type: Blog
url: https://www.phone.com/blog/
- type: GitHubOrganization
url: https://github.com/phonedotcom
- type: Pricing
url: https://www.phone.com/pricing/
- type: SignUp
url: https://www.phone.com/pricing/
- type: Login
url: https://my.phone.com
- type: TermsOfService
url: https://www.phone.com/general-terms/
- type: PrivacyPolicy
url: https://www.phone.com/privacy-statement/
- type: Packages
url: packages/phone-com-packages.yml
- type: SDKs
url: packages/phone-com-packages.yml
- type: LLMsTxt
url: llms/phone-com-llms.txt
- type: Authentication
url: authentication/phone-com-authentication.yml
- type: OAuthScopes
url: scopes/phone-com-scopes.yml
- type: Conventions
url: conventions/phone-com-conventions.yml
- type: Lifecycle
url: lifecycle/phone-com-lifecycle.yml
- type: StatusPage
url: lifecycle/phone-com-lifecycle.yml
- type: DomainSecurity
url: security/phone-com-domain-security.yml
- type: TrustCenter
url: security/phone-com-trust-center.yml
- type: Compliance
url: security/phone-com-trust-center.yml
- type: WellKnown
url: well-known/phone-com-well-known.yml
- type: Conformance
url: conformance/phone-com-conformance.yml
- type: X-MCPServerCandidate
url: mcp/phone-com-mcp.yml
note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: Webhooks
url: asyncapi/phone-com-events-webhooks.yml
- type: DataModel
url: data-model/phone-com-data-model.yml
- type: AgentSkill
url: skills/_index.yml
apis:
- aid: phone-com:phone-com-10-dlc-api
name: Phone Com 10 DLC API
description: 10 DLC registration is required for SMS messaging
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- 10 DLC
properties:
- type: OpenAPI
url: openapi/phone-com-10-dlc-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-access-tokens-api
name: Phone Com Access Tokens API
description: Allows you to manage access tokens issued for your account.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Access Tokens
properties:
- type: OpenAPI
url: openapi/phone-com-access-tokens-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-account-contacts-api
name: Phone Com Account Contacts API
description: Contact which can be used for different needs, such as ordering devices
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Account Contacts
properties:
- type: OpenAPI
url: openapi/phone-com-account-contacts-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-accounts-api
name: Phone Com Accounts API
description: This page gives an overview of how to interact with your accounts.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Account
tags_raw:
- Accounts
properties:
- type: OpenAPI
url: openapi/phone-com-accounts-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-api-endpoint-statistics-api
name: Phone Com API Endpoint Statistics API
description: Information about API usage statics.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- API Endpoint Statistics
properties:
- type: OpenAPI
url: openapi/phone-com-api-endpoint-statistics-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-api-errors-api
name: Phone Com API Errors API
description: We save API errors related to your account so you can analyze issues if for some reason you don't log error
responses in your application
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- API Errors
properties:
- type: OpenAPI
url: openapi/phone-com-api-errors-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-asynchronous-call-logs-api
name: Phone Com Asynchronous Call Logs API
description: "Phone.com created the async-call-logs API endpoint to allow customers to download large amounts of call logs\
\ without encountering the normal Phone.com API Rate Limits. \nThis service needs to be activated on a per-customer basis\
\ and collect the call log data in the requested customer's format. (please call our support to activate and better define\
\ the format if needed) \nWhen the async-call-logs endpoint is invoked, the endpoint will return a list of 47 to 48 files,\
\ each representing the calls entered into the logs during a full hour of the last two days. The file names contain the\
\ time period of call logs each file encapsulates. \nThe Items returned are ordered by modification (i.e., creation) date;\
\ the most recent item is the first item. The files should be download using the provided URL(s) in the item JSON array\
\ returned by the endpoint. \nPhone.com creates the files at the 15 minutes mark, every hour for the previous hour. Files\
\ lifespan is 2 days, which means that each file will disappear after 48 hours."
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Asynchronous Call Logs
properties:
- type: OpenAPI
url: openapi/phone-com-asynchronous-call-logs-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-available-phone-numbers-api
name: Phone Com Available Phone Numbers API
description: This service lists phone numbers that are available for purchase through Phone.com.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Available Phone Numbers
properties:
- type: OpenAPI
url: openapi/phone-com-available-phone-numbers-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-blocked-calls-api
name: Phone Com Blocked Calls API
description: The Blocked Calls API allows users block incoming calls from specific phone numbers. If only a part of a telephone
number is provided, calls with callers ID matching the pattern will be blocked. For example, pattern '+1212' will block
all calls from NY 212 area code.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Blocked Calls
properties:
- type: OpenAPI
url: openapi/phone-com-blocked-calls-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-call-logs-api
name: Phone Com Call Logs API
description: The Call Logs API returns a list of call detail records for the account. The result includes the id, start
time, creation time, caller ID, called number, direction of call, and duration in seconds. If applicable, the result may
also include final action, final action duration, listen URL, and/or transcription. Since the call logs usually contains
many calls, API users may use filters such as start_time, created_at and direction to limit the result set to calls interested.
Users may also use the sorting parameters such as start_time and created_at to list result in ascending or descending
order.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Call Logs
properties:
- type: OpenAPI
url: openapi/phone-com-call-logs-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-call-reports-api
name: Phone Com Call Reports API
description: Aggregated calls statistics
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Call Reports
properties:
- type: OpenAPI
url: openapi/phone-com-call-reports-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-caller-ids-api
name: Phone Com Caller IDs API
description: API users with Extension scope access token does not have access to the Phone Number API. This API helps user
to retrieve available account phone numbers to be used as caller id via the /Calls API.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Caller IDs
properties:
- type: OpenAPI
url: openapi/phone-com-caller-ids-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-calls-api
name: Phone Com Calls API
description: This API places a call to the caller phone number (or caller extension ID). If that number (or extension) answers
within the timeout period, then the callee DID (or extension) will be connected to the call.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Calls
properties:
- type: OpenAPI
url: openapi/phone-com-calls-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-clients-api
name: Phone Com Clients API
description: Phone.com API supports OAuth 2.0 Authorization Framework, which enables a third-party application (client)
to obtain limited access to HTTP API requests. This page describes how to use the /oauth/clients API to list, get and
delete client.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Clients
properties:
- type: OpenAPI
url: openapi/phone-com-clients-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-conversations-api
name: Phone Com Conversations API
description: Represents overview of your messaging history in messenger-like format.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Conversations
properties:
- type: OpenAPI
url: openapi/phone-com-conversations-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-devices-api
name: Phone Com Devices API
description: "Extension on your Phone.com account may have SIP devices associated with them. \n\nThe Device API provides\
\ information about those SIP devices, such as the SIP credentials required."
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Devices
properties:
- type: OpenAPI
url: openapi/phone-com-devices-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-events-callbacks-api
name: Phone Com Events Callbacks API
description: 'Callbacks represent URLs on your side which will be called by our system when event occurs. Read more: https://github.com/phonedotcom/events-integration-doc'
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Events Callbacks
properties:
- type: OpenAPI
url: openapi/phone-com-events-callbacks-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-events-callbacks-health-status-api
name: Phone Com Events Callbacks Health Status API
description: Callback invocations statistics
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Events Callbacks Health Status
properties:
- type: OpenAPI
url: openapi/phone-com-events-callbacks-health-status-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-events-integrations-overview-api
name: Phone Com Events Integrations Overview API
description: 'Combined representation of listeners, callbacks, profiles and subscriptions. Read more: https://github.com/phonedotcom/events-integration-doc'
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Events Integrations Overview
properties:
- type: OpenAPI
url: openapi/phone-com-events-integrations-overview-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-events-listeners-api
name: Phone Com Events Listeners API
description: 'Listener is an entity that associates subscriptions with callbacks. Read more: https://github.com/phonedotcom/events-integration-doc'
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Events Listeners
properties:
- type: OpenAPI
url: openapi/phone-com-events-listeners-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-events-listeners-filters-api
name: Phone Com Events Listeners Filters API
description: Filters functionality. If no filters defined, than all events will be processed. If filters defined, events
should match all of them.
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Events Listeners Filters
properties:
- type: OpenAPI
url: openapi/phone-com-events-listeners-filters-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-events-listeners-subscriptions-api
name: Phone Com Events Listeners Subscriptions API
description: 'Defines what kind of events should generate a callback. Read more: https://github.com/phonedotcom/events-integration-doc'
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Events Listeners Subscriptions
properties:
- type: OpenAPI
url: openapi/phone-com-events-listeners-subscriptions-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-events-profiles-api
name: Phone Com Events Profiles API
description: 'A Profile allows to specify a notifications email for a callback. Notifications are emitted when there is
a need to notify the callback owner of some issues like timeouts, or de-registration of the callback. Read more: https://github.com/phonedotcom/events-integration-doc'
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Events Profiles
properties:
- type: OpenAPI
url: openapi/phone-com-events-profiles-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
- aid: phone-com:phone-com-express-service-codes-api
name: Phone Com Express Service Codes API
description: An Express Service Code is required when a customer calls Phone.com for support. With the following services,
customer may retrieve the Express Service Code associated with his/her account
humanURL: https://www.phone.com/api/
baseURL: https://api.phone.com/v4
tags:
- Express Service Codes
properties:
- type: OpenAPI
url: openapi/phone-com-express-service-codes-api-openapi.yml
- type: Documentation
url: https://docs.phone.com/
- type: APIReference
url: https://apidocs.phone.com/reference
- type: GettingStarted
url: https://docs.phone.com/aboutdevenv/aboutdevenvhome.html
- type: JSONSchema
url: json-schema/phone-com-live-answer-schema.json
- type: JSONSchema
url: json-schema/phone-com-route-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-schema.json
- type: JSONSchema
url: json-schema/phone-com-events-overview-schema.json
- type: JSONSchema
url: json-schema/phone-com-account-schema.json
- type: JSONSchema
url: json-schema/phone-com-extension-contact-schema.json
# --- truncated at 32 KB (81 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/phone-com/refs/heads/main/apis.yml
Every provider here is available over the APIs.io API and to AI agents over MCP.
Kin Score
How this is scored →