SIP Account Management API

This API can be used from third party applications running in and end-point that wish to interact with the SIP account data stored on the server. Data can be read or modified by calling various functions.

Directory Services

SIP2SIP uses LDAP for directory services:

Server address


Search base

ou=addressbook, dc=sip2sip, dc=info

Server Address

To access the API, a client must connect using HTTP protocol to the following address:

The return is encoded using json.


To login you must append & to the query string, then in the HTTP digest authentication form enter the username part without and the password.

API Functions

The following actions are supported:


Returns identity information:

SIP aliases

Return the SIP aliases:

Add an alias to our own account

ENUM numbers

Return the ENUM numbers:

Call history

Returns call history:

Registered devices

Return the list of registered devices


Return the prepaid balance and active calls:

Return the history of prepaid balance:

Return the curent monthly usage:

Call forwarding

Return the call forwarding settings:

Set call forwarding

FUNC = Forward unconditional all calls
FBUS = Forward on Busy
FNOL = Forward on Not Online
FNOA = Forward on No Answer
FUNV = Forward when Not Available based on Accept rules

Pre-defined keywords for diversion targets:


Call filtering

Return the list of accept rules:

Return the list of reject rules:

Voicemail settings

Return the voicemail settings:

Do not disturb

Enabled Do Not Disturb

Disable Do Not Disturb

Enable Do Not Disturb for 60 minutes


Enabled privacy (hide Caller Id for outgoing calls)

Disable privacy

Data replication

These function can be used by multiple client instances to replicate arbitrary data among themselves. An example of such application is bidirectional replication of chat messages between multiple clients configured for the same account.

Get journal entries

UUID is the GRUU identifier of the SIP client. ID must be replaced with the last replicated journal_id received from a previous get_journal_entries call. The return contains an array with 'data' entities that were put using the 'put_journal_entries' call. Optionally after_timestamp can be used to retrieve entries recent than the given timestamp.

Put journal entries

The request must be done using POST method by passing two variables uuid=UUID and data=DATA.

UUID is the GRUU identifier of the SIP client.

DATA must be a json encoded associative array containing the 'id' and 'data' keys. 'id' value must be client own identifier corresponding to the replicated data.

'data' value can be anything the client understands when reading it back using a get_journal_entries call. Is recommended that 'data' values are encrypted using a key known only by the client.

The response from the server contains a json encoded array with mappings between client id and server journal id that can be saved by the client for further reference that can be used for 'get_journal_entries' calls.