Difference between revisions of "MOR API phonebooks get"
From Kolmisoft Wiki
Jump to navigationJump to search
m |
|||
| Line 24: | Line 24: | ||
** Errors: | ** Errors: | ||
*** <error>No Phonebooks</error> - User | *** <error>No Phonebooks</error> - User don't have phonebooks. | ||
*** <error>User was not found</error> - User was not found using user_id. Use correct user id. | *** <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. | *** <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 | *** <error>Dont be so smart</error> - User with UNIQUEHASH not found or params id not sent. Enter correct id. | ||
Revision as of 07:55, 14 November 2011
This functionality is available from MOR 11
Phonebooks list
- Call: /api/phonebooks
- Methods: POST, GET(if allowed, not recomended)
- Params:
- user_id - User ID in MOR database, whose phonebooks we want to see. Required.
- u - username to login. Required.
- p - password to login. Required.
- hash - 632667547e7cd3e0466547863e1207a8c0c0c549
- Returns:
- Success
- <phonebooks> <phonebook> ..... </phonebook> </phonebooks>
- Success
- Errors:
- <error>No Phonebooks</error> - User don't have phonebooks.
- <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.
- <error>Dont be so smart</error> - User with UNIQUEHASH not found or params id not sent. Enter correct id.
- Errors:
