Difference between revisions of "API Configuration"

From Kolmisoft Wiki
Jump to navigationJump to search
m
Line 1: Line 1:
'''SETTINGS –> Setup –> Settings –> API'''
Go to '''SETTINGS –> Setup –> Settings –> API''' tab
 
 
[[File:Settings api.png]]
 


* '''Allow API''' - should we enable API?
* '''Allow API''' - should we enable API?
Line 6: Line 10:
* '''XML API Extension''' - send XML output with <HTML> tag - this is used for broken .Net support, keep it unchecked if everything works for you
* '''XML API Extension''' - send XML output with <HTML> tag - this is used for broken .Net support, keep it unchecked if everything works for you
* '''Allow API Login Redirect''' - if login is successful the customer will be redirected to MOR billing Main site.
* '''Allow API Login Redirect''' - if login is successful the customer will be redirected to MOR billing Main site.
* '''Uniquehash''' - admin's unique hash. Reseller can see it by going to '''SETTINGS''' -> '''Registration'''.





Revision as of 16:16, 2 July 2012

Go to SETTINGS –> Setup –> Settings –> API tab


Settings api.png


  • Allow API - should we enable API?
  • Allow GET API - should we allow GET method to be used for API? Good for testing - but do not use in production! It is unsafe.
  • API Secret Key - key to generate Hash
  • XML API Extension - send XML output with <HTML> tag - this is used for broken .Net support, keep it unchecked if everything works for you
  • Allow API Login Redirect - if login is successful the customer will be redirected to MOR billing Main site.
  • Uniquehash - admin's unique hash. Reseller can see it by going to SETTINGS -> Registration.


  • Please note that MOR does not allow you to enable Allow API if API Secret Key is not entered. In such case you will get a message Invalid API secret key. Enter API Secret Key in order to fix this.



See also