Ecosystem
The integration map is the API list, drawn
Glossary, mind map, sister technologies, the integration list, teaching bridges, and hooks that stay blank.
Ecosystem ยท practice ยท 12 min full read
An integration map for this chapter is the API list turned sideways: CTI, Configuration, Reporting, Statistics, Web2Campaign, CRM SDK, and Web Connectors, plus the prebuilt CRM names and the UC names. REST is the access sentence for agents, administrators, supervisors, and reporting users.
- Draw the API list
- Do not draw payloads
Web Connectors and the CRM SDK are both on that list and they are not the same row. A connector that opens a page and an SDK you build against are different objects. The map labels both. It does not invent payloads.
Labels only.
Draw the map
Seven API labels and no fields.
- CTI
- SDK
- Web Connectors
A reader can see they are different boxes.
- Reporting versus Statistics? Two names.
- SDK versus connector? Two names.
- Payloads? Not drawn.
- Who does the REST sentence name? Agents, administrators, supervisors, reporting users.
- APIs and SDKs. vendor. last checked 2026-10.
Glossary. G.711: The default codec in the technical requirements, described as uncompressed. Technical requirements PDF
Sister technologies. Dynamics 365, Zendesk, Oracle, NetSuite, Epic. Each is a named Plus adapter. This lab does not copy a package number for them. Technical requirements PDF
Config. Seven API labels and no fields.
Troubleshooting. The page printed two names. Split them.
Cross-platform bridge. A mapping to another PBX or contact center is a teaching bridge. It is not an import button.
Future hook. The guide's cloud endpoint stays unset. Confirm before relying on a dated catalog or a case-study number.