Microsip Api Documentation Jun 2026

Use the command_line integration to control MicroSIP via batch scripts, enabling voice calls from automations.

import subprocess def dial_number(phone_number): # Paths may vary based on installation (e.g., Program Files) microsip_path = r"C:\Program Files\MicroSIP\microsip.exe" subprocess.run([microsip_path, phone_number]) # Usage dial_number("123456789") Use code with caution. 3. Windows Messages API (Single Instance Control)

MicroSIP does not feature a traditional HTTP REST API or a web-based JSON endpoint. Instead, it relies on Windows-native inter-process communication (IPC) and command-line arguments. microsip api documentation

When a user clicks these links, Windows passes the phone number directly to the running MicroSip instance to initiate dialing immediately. 4. Code Examples C# Example: Initiating a Call via CLI

To start MicroSip or send it directly to the system tray without stealing user focus, use the -m switch. microsip.exe -m Use code with caution. 2. Windows Messaging API (Advanced Integration) Use the command_line integration to control MicroSIP via

Developers can interact with MicroSIP using three primary methods:

The CLI is the primary "API" for integration. The available commands allow you to initiate calls, answer incoming calls, and manage active sessions. Windows Messages API (Single Instance Control) MicroSIP does

microsip.exe /hangupall (terminates all active sessions) Application State

This is the more powerful interface. Any Windows application can send a WM_COPYDATA message to MicroSIP’s main window (class "MicroSIP" ). The dwData field identifies the command, and lpData contains a UTF-8 string with parameters.

import subprocess def make_call(phone_number): microsip_path = r"C:\Program Files\MicroSIP\microsip.exe" subprocess.run([microsip_path, phone_number]) make_call("15550199") Use code with caution. 3. Deep Integration via Windows Messages ( WM_COPYDATA )