Wallex Pay
Sign InSign Up
  • Welcome
  • Product Introduction
  • Get Started
  • Integration Guide
  • Account Creation
    • Individual/Freelance Account
    • Business Account
  • Verification Process
    • Need Assistance?
      • Starting Point
      • Common Rejection Causes
      • Proof of Address (POA)
      • Pending Verification
      • Session Expired?
  • Supported Coins
  • Merchant Tools
    • Payment Buttons
    • Custom APIs
      • API Basics
      • Informational Commands
      • Receiving Payments
      • Withdrawals/Transfers
    • Instant Payment Notification (IPN)
    • Invoice Builder
    • Point of Sale (POS)
    • Pre-Built Plugins
  • Mass Payouts
  • API Keys Management
  • Integration Testing & Testnet
  • Profile Management
    • Manage Personal Info
    • Wallet Statement
  • Access Issues
    • Why my Account is Blocked/Suspended?
  • Security
    • Account Security
    • Two-Factor Authentication (2FA)
    • Hacked Account
  • Fees & Limits
  • Legal & Regulatory
    • Restricted Jurisdictions
    • User Agreement
    • Privacy Policy
  • Contact our Experts
Powered by GitBook
On this page
  1. Merchant Tools
  2. Custom APIs

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

Field Name
Description
Required?

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

Get Authorized Token


For Wallex Pay users can get Authorized token by inserting public and private key in POST method.

Once user gets the Authorized bearer token it will be used for getting account info, user balances, receiving payments etc.

API POST Fields

Get Authorized Information

Field Name
Description
Required?

cmd

login

Yes

API Response

A successful call to the 'login' command will give you a result similar to this (JSON):

{
  "success": "true",
  "result": {
    "access_token": "Bearer <token>",
    "expires_at": "2020-08-16 13:28:32"
  },
  "message": "Login successfully!"
}
PreviousCustom APIsNextInformational Commands

Last updated 9 months ago

Method: POST URL: Requested Params: publickey, privatekey

http://wallexpay.io/api/login