Difference between revisions of "MOR API card group get"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 23: Line 23:
<cardgroup>
<cardgroup>
   <name>....</name>
   <name>....</name>
   <iamge_link>/cards/example.jpg</iamge_link>
   <iamge_link>/billing/cards/example.jpg</iamge_link>
   <description>...</description>
   <description>...</description>
   <price>...</price>
   <price>...</price>

Revision as of 13:09, 31 January 2012

'This functionality is available from MOR 12


MOR API

Show Calling Card Group






  • Call: /api/show_calling_card_group
  • Methods: POST, GET(if allowed, not recomended)
  • Params:
    • id - Calling Card Group ID in MOR database. Required.
    • u - username to login. Required.
    • p - password to login. Required.
    • hash - SHA1 hash constructed using id and API_Secret_Key ( More described in Constructing hash). Required.
  • Returns:
    • Success

<cardgroup>

 <name>....</name>
 <iamge_link>/billing/cards/example.jpg</iamge_link>
 <description>...</description>
 <price>...</price>
 <price_with_tax>...</price_with_tax>
 <currency>...</currency>
 <free_cards_size>...</free_cards_size>
 <pin_length>....</pin_length>
 <number_length>....</number_length>

</cardgroup>


    • Errors:
      • <error>Bad login</error> - User supplied bad login or password.
      • <error>Incorrect hash</error> - Hash was not correct. Check API_Secret_Key and order or params while concatenating hash_string.
      • <error>Cardgroup was not found</error> - Use correct Calling Card Group ID .




  • Example:
    • We have id = 6, API Secret Key = 456789
    • Hash string to be converted: "6456789"
    • We might send:
      • /api/show_calling_card_group?id=6&hash=67df827dec80a7241fb3fc4de22a90e62c5e8d93&u=admin&p=admin

* Note that username and password are not included in hash