API Basics
Unlocking the fundamentals of APIs for Wallex Pay integration.
Introduction
The WallexPay API will provide access to our services and information to our sellers. If you would like to see a particular function added, please click the Contact menu item above. API calls are implemented as standard HTTP POST (application/x-www-form-urlencoded) calls to http://wallexpay.io/api . Publickey and Privatekey need to get the bearer authentication token . Remaining all API response will get once possible to pass in header bearer token.
API Setup
The only setup needed is to go to the API Keys page and generate an API key. You will be given a private and public key used to authenticate your API calls. Make sure you don't share your private key with any 3rd parties. User can able to create a maximum of 10 API Keys.
Note: You must click "Edit Permissions" to enable most commands.
API Response
The API will return an array with 1 or 2 elements: 'error' and 'result'. The result will always have an 'error' field. If its value is 'ok' (case-sensitive) the API call was a success, otherwise it will contain an error message. If there is data to return to you, it will be stored as an array in the 'result' element.
API POST Fields
API calls are made as basic HTTP POST requests using the following variables: (note: The POST data is regular application/x-www-form-urlencoded style data, not JSON or XML).
Main Fields: These fields will be here for all calls
version
1
Yes
key
Your API public key
Yes
cmd
The API you are calling
Yes
nonce
Optional nonce (an integer that is always higher than in your previous API call) to prevent replay attacks. This is optional, however once used with a particular key it must always be used with that key from then on. Note: API nonce processing is non-atomic so you always want to wait for an API call to return before making another.
No
format
The format of response to return, json or xml. (default: json)
No
Last updated