Welcome to Mercurius API

User Functions & Bank Virtual PBX & Call Center PIN - ServiceID = 2 (VoIP) or 20 (M2M) PIN - ServiceID = 2 (VoIP) or 20 (M2M) Mobile Telephony & Other Services
User Accounts
  1. User Login
  2. User Logout
  3. SessionID Refresh
  4. Validate SessionID Auth
  5. Get all available Users
  6. Add new user
  7. Delete existing user
  8. Change existing user
  9. Get User Info

Bank Account & Invoices

  1. Get Bank Balance
  2. Get Bank Statement
  3. Transfer Bank Balance
  4. Get SMS Bank Balance
  5. Get SMS Bank Statement
  6. Transfer SMS Bank Balance
  7. Log SMS Bank Activity
  8. Invoice CDR for Login

User Services

  1. Get all available Services
  2. Get all User services
  3. Get individual User Service
 Extensions
  1. Add Extension
  2. Change Extension
  3. Get Extension
  4. Change Seguali
  5. PBX Service Status

Conferences, IVR, Queues, Dialer

  1. Add Conference
  2. Change Conference
  3. Get Conference
  4. Add PBX
  5. Change PBX
  6. Get PBX
  7. Add Queue
  8. Add Dialer
  9. Send Phones to Dialer
  10. Search for audio recording
  11. Get Dialer Status from RECID

Public Number

  1. Get Country List
  2. Get DID Locations
  3. Get List of DIDs
  4. Add DID
  5. Change DID
  6. Get DID
 PIN (VoIP) Functions
  1. Add PIN
  2. Del PIN
  3. Get PIN Balance
  4. Get PIN Daily Balance
  5. Change PIN Balance
  6. Reset PIN Balance
  7. Change PIN Plans
  8. Change PIN Traffic
  9. Change PIN Credit Limit

PIN CallerID Functions

  1. Add CallerID to PIN
  2. Delete CallerID from PIN
  3. Get CallerIDs from PIN
  4. Find PIN from CallerID
  5. Find PIN from ICCID
  6. Check if CallerID exists

PIN CDR data

  1. Get PIN CDR
  2. Get PIN Bill
  3. Get PIN CDR (HTML)
  4. Get Login/Agent CDR
  5. Get Agent Stats
 PIN (VoIP & M2M) Carriers
  1. Get PIN/M2M Carriers

PIN (M2M) Functions

  1. Add PIN
  2. Del PIN
  3. Edit PIN Geo Location
  4. Transfer Service
  5. PINs Online
  6. M2M Last Carrier
  7. Set Jasper Status on
  8. PUSH API

Obs: The same functions available for PIN-VoIP are available for PIN-M2M. The main single difference is that, for M2M, the ServiceID tag must always be = 20, while for PIN VoIP, ServiceID = 2

 SMS & Voice Prepaid Mobile
  1. Send SMS
  2. Get SMS Status
  3. Get Mobile Carriers
  4. Get Mobile Recharges
  5. Recharge mobile phone
  6. Mobile number Portability look up

GPS

  1. Send GPS
  2. Get GPS
  3. Get Geocode of GSM CellID

UPC - Bar Code

  1. Send UPC
  2. Show UPC

Reference Links:

  1. ParlaBox User Guide
  2. ParlaBox customer login and sign-up
  3. Public demo of DID selection
  4. Error Codes - Descriptions

Important API guidelines:

  1. All APIs can be called by either using POST or GET methods
  2. The page samples are all using the POST method. Attention to the POST execution in all sample forms: <form action="//cgi-bin/parla" method="POST">. This is just like a simple HTML POST submission
  3. To use the GET method, i.e., call the API using URL-formatted parameters such as www.parlacom.net/cgi-bin/parla?function=getallusers&company=parla&output_type=html&login=clovis1234&sessionid=6173101117159668311613718971931311572197, just pass the required variables in the URL. The variables are exactly the same as those found in the HTML FORM sample pages.
  4. If sessionID is created and passed in the API calls, the admin and adminpwd fields are not required. If sessionID is not provided, the API call must be authenticated with mandatory fields admin and adminpwd
  5. If sessionID is created, it can be used in all subsequent API calls, given that the time lapse between these calls is not greated than the session timeout of the application. If a sessionid times out, the API call will error out, indicating that a new sessionid must be created
  6. The optional login field is either equal to the admin field, or it is the login of a user under the admin's hierarchy. Any user can be "admin" of himself or of all logins in his hierarchy
  7. Field output_type will indicate the format of the result that the API will return. =xml indicates XML data output. =html indicates a html-formatted output, exactly like the ones provided when browsing the web interface of the application at www.parlacom.net/login.html
  8. All XML results will return the tag "errorcode". For example: <errorcode>0</errorcode>. Only successfully executed API calls will return errorcode=0
  9. By browsing the web interface at www.parlacom.net/login.html , all URL's are API calls!  By doing so, developers can easily and quickly figure out how to build their own API calls and, as a result, build their own web interfaces. It's very easy and simple to "reverse engineer" the application for your own purpose