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

API Keys Management

Easily generate, view, and manage your API keys.

PreviousMass PayoutsNextIntegration Testing & Testnet

Last updated 8 months ago

Setting up Merchant ID & IPN Secret


Merchant ID: To locate your Merchant ID, simply log in to your account and select "Account Settings" from the Side Menu.

Then locate the [Merchant Settings] button and click on it.

Merchant Settings

  • IPN Secret: In the "Merchant Settings" section, you should insert a IPN Secret (This is used to verify that an IPN is from us, use a good random string nobody can guess).

Important: Keep your IPN Secret confidential and do not share it with anyone. Sharing this key could compromise the security of your transactions.

  • IPN URL: HTTPS URL recommended (self-signed certs OK).

  • Callback Deposit IPN Coin/Currency: Select which coins you want to accept as payment by selecting the dropdown box in front of each coin.

  • Status/Log Email: If set payment status emails and positive feedback notifications will be sent to this email address. Otherwise they will be sent to your primary email address.

  • When To Receive Emails:

    • When a user submits a new payment to you.

    • When funds have been received by us for a payment to you.

    • When funds for a payment have been sent to you.

    • When a deposit is received on one of your deposit addresses.

Note: Once you have filled out all the fields and selected your preferences, do not forget to click the [Update Settings] button to save your changes.

Creating & Managing API Keys


Creating API Keys

API keys are essential for authenticating and interacting with our services. Follow these steps to generate and secure your API keys:

  • Navigate to "API Keys" from the Side Menu.

  • Click on the [Generate new key] button.

  • Your API Public Key and API Private Key will be displayed (Ensure to store them securely).

Note: You can have a maximum of 10 API keys.


Show Keys

  • Navigate to "API Keys" from the Side Menu.

  • Click the [Show Keys] button located on the right-hand side of the screen.


Edit Keys

  • You can modify and manage your API keys by clicking the blue "Edit" pencil icon.

  • By default, the API key is named "Unnamed API Key". However, for better API key management and to avoid any confusion, we highly recommend renaming your keys with descriptive and meaningful names. This will help ensure clarity and organization in your API usage.

  • You can also manage API key permissions using the options available on the right side of the screen.

Be sure to save your changes by clicking the [Update Permissions] button.


Delete Selected Keys

  • You can also Delete any API key that you no longer need.

Important: Once you delete an API key, the integration will be disrupted and the action cannot be reversed.

Create a new user

POST /users

<Description of the endpoint>

Headers

Name
Value

Content-Type

application/json

Authorization

Bearer <token>

Body

Name
Type
Description

name

string

Name of the user

age

number

Age of the user

Response

{
  "id": 1,
  "name": "John",
  "age": 30
}
{
  "error": "Invalid request"
}