Skip to main content

Documentation Index

Fetch the complete documentation index at: https://developer.quickei.io/llms.txt

Use this file to discover all available pages before exploring further.

The Partner Payout API uses Bearer Token authentication. Include your API key in every request.

​
Base URLs

The API has separate URLs for sandbox and production:
EnvironmentBase URL
Sandboxhttps://quickei.io/api/partner/sandbox/v1
Productionhttps://quickei.io/api/partner/v1
Use the sandbox URL with sandbox credentials for testing. Use the production URL with production credentials for real transactions.A sandbox token will be rejected on the production URL, and vice versa.

​
Getting Your Credentials

1

Log in to the Merchant Dashboard

Go to quickei.io/merchant/login and sign in.
2

Create API Keys

Go to Developer API > API Keys and generate your keys. You will get separate keys for Sandbox and Production.
3

Go to Payout API

Navigate to Payout API in the sidebar. You’ll see your credentials for both environments with a toggle to switch between them.

​
Request Headers

Include the following headers in every request: 
Authorization: Bearer YOUR_API_KEY
Content-Type: application/json
Accept: application/json

​
Example Requests

Sandbox: 
curl -X GET https://quickei.io/api/partner/sandbox/v1/balance \
  -H "Authorization: Bearer YOUR_SANDBOX_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json"
Production: 
curl -X GET https://quickei.io/api/partner/v1/balance \
  -H "Authorization: Bearer YOUR_PRODUCTION_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json"

​
Sandbox vs Production

SandboxProduction
Base URL/api/partner/sandbox/v1/api/partner/v1
CredentialsSandbox API keyProduction API key
Real fundsNo — simulated transactionsYes — real money
Wallet debitedSandbox walletReal merchant wallet
User wallet creditedNoYes
Sandbox transactions appear in the Sandbox Wallets section of your merchant dashboard, separate from production transactions.
Never expose your API key in client-side code, mobile apps, or public repositories. All Partner API calls must be made server-to-server.

​
Error Responses

If authentication fails, the API returns: 
{
  "message": {
    "error": ["Invalid sandbox API credentials."]
  }
}
StatusCause
401 UnauthorizedMissing, invalid, or wrong-environment API key
403 ForbiddenAPI key is valid but Partner Payout API is not enabled for your account