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.

Quickei uses two authentication methods depending on the API you’re using.

​
Payment Gateway API — Bearer Token

The Payment Gateway API uses OAuth-style bearer tokens. First, exchange your credentials for a token, then include it in subsequent requests.
1

Get your credentials

Log in to your Merchant Dashboard and navigate to Developer API > API Keys. Copy your Client/Primary Key and Secret Key.
2

Request a token

Call the Access Token endpoint with your credentials.
curl -X POST https://quickei.io/pay/sandbox/api/v1/authentication/token \
  -H "Content-Type: application/json" \
  -d '{
    "client_id": "YOUR_CLIENT_ID",
    "secret_id": "YOUR_SECRET_ID"
  }'
3

Use the token

Include the token in the Authorization header for all subsequent requests.
Authorization: Bearer nyXPO8Re5SXP...
Tokens expire after 10 minutes (600 seconds). Implement token refresh logic in your integration to request a new token before expiry.

​
POS API — HTTP Basic Auth

The POS API uses HTTP Basic Authentication. Encode your client_id:client_secret as base64. 
# Format
Authorization: Basic base64(client_id:client_secret)

# Example
Authorization: Basic Y2xpZW50X2lkOmNsaWVudF9zZWNyZXQ=

​
Security Best Practices

Keep keys secret

Never expose API keys in client-side code, mobile apps, or public repositories.

Use environment variables

Store credentials in environment variables or a secrets manager — never hardcode them.

Rotate regularly

Regenerate your API keys periodically from the Merchant Dashboard.

Restrict access

Use IP allowlists and limit API key permissions to only what’s needed.