Difference between revisions of "MOR API user calls get"

From Kolmisoft Wiki
Jump to navigationJump to search
m
Line 7: Line 7:


<br><br>
<br><br>
'''Admin''' - can get every user calls
'''Reseller''' - can get his and his users calls
'''User''' - can get his own calls
----
----
<br><br>
<br><br>

Revision as of 10:13, 31 May 2011

This functionality is available from MOR 8


MOR API

Retrieves list of calls in selected time period for some user/device



Admin - can get every user calls

Reseller - can get his and his users calls

User - can get his own calls





  • Call: /api/user_calls
  • Methods: POST, GET(if allowed, not recomended)
  • Params:
    • user_id - Users ID in MOR database. Required.
    • period_start - Unix timestamp of calls period starting date. (Default: Today at 00:00).
    • period_end - Unix timestamp of calls period end date. (Default: Today at 23:59).
    • direction - Call direction. Possible values [outgoing, incoming]. (Default: outgoing)
    • calltype - Call type. Possible values [all, answered, busy, no_answer, failed, missed, missed_inc, missed_inc_all, missed_not_processed_inc]. (Default: all)
    • device - Device ID in MOR database. Possible values [all, numeric value of device_id]. (Default: all)
    • hash - SHA1 hash constructed using params and API_Secret_Key ( More described in Constructing hash). Required.
    • u - Users username. Required.
    • p - Users password. Required.
  • Returns:
    • Errors:
      • <error>User was not found</error> - User was not found using user_id. Use correct user_id.
      • <error>Incorrect hash</error> - Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string.