Difference between revisions of "MOR API phonebook edit"
From Kolmisoft Wiki
Jump to navigationJump to search
(Undo revision 12112 by Mindaugasm (Talk)) |
|||
Line 1: | Line 1: | ||
<!---This functionality is available from MOR 11---> | |||
[[MOR API]] Phonebook edit | |||
[[MOR API]] | |||
Phonebook edit | |||
<br><br> | <br><br> | ||
---- | ---- |
Revision as of 09:35, 20 February 2013
MOR API Phonebook edit
- Call: /api/phonebook_edit
- Methods: POST, GET(if allowed, not recomended)
- Params:
- phonebook_id - Phonebook ID in MOR database. Required.
- u - username to login. Required.
- p - password to login. Required.
- hash - SHA1 hash constructed using params and API_Secret_Key ( More described in Constructing hash). Required.
- number
- name
- speeddial
- Returns:
- Success
- <status>Phonebook saved</status>
- Errors:
- <error>Phonebook was not saved</error>
- <message>problem message</message>
- <error>Phonebook was not found</error> - Phonebook was not found using phonebook_id. Use correct phonebook id.
- <error>Incorrect hash</error> - Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string.
- <error>Dont be so smart</error> - User with UNIQUEHASH not found or params id not send. Enter correct id.
- <error>Phonebook was not saved</error>
- Success
- Example:
- We have phonebook_id = 123, API Secret Key = 456789
- Hash string to be converted: "123456789"
- We send:
- /api/phonebook_edit?u=admin&p=admin&phonebook_id=123&hash=f7c3bc1d808e04732adf679965ccc34ca7ae3441
* Note that username and password are not included in hash