SDK overview
The SDKs are language-specific client libraries that let you call the Communication API reliably from your application code.
SDK
Java
Java 17+
bizgo-sdk-comm-java
SDK
Node.js
Node.js / TypeScript
bizgo-sdk-comm-js
SDK
Python
Python 3.6+
infobank-omni-sdk-python
Supported languages and runtimes
| Language | Repository | Runtime baseline | Notes |
|---|---|---|---|
| Java | bizgo-sdk-comm-java | Java 17 or higher | Latest example version 1.1.1 per the README |
| Node.js | bizgo-sdk-comm-js | Node.js / TypeScript | 1.0.1 per the repository package.json |
| Python | infobank-omni-sdk-python | Python 3.6 or higher | Legacy structure, 1.0.2 per setup.py |
Common integration baseline
- Base URL:
https://mars.ibapi.kr. - Authentication: API KEY.
- Unified send path: centered on
/api/omni. - Core features: broadcast send, failover chain, asynchronous report handling.
Which SDK should you choose
- Java: a good fit when you need a stable server integration in a backend service, including Spring Boot.
- Node.js: a good fit when you need fast development and deployment on a JavaScript/TypeScript server.
- Python: a good fit when you have an existing Python operating environment or need to maintain a legacy integration.
Reference links
- GitHub Organization: https://github.com/icomm-api.
- Java README: bizgo-sdk-comm-java/README.md.
- Node.js README: bizgo-sdk-comm-js/README.md.
- Python README: infobank-omni-sdk-python/README.md.