Authentication

All requests to the Aella for Merchants API must be authenticated using a secret key. We use Bearer Token authentication, which means you'll include your secret key in the Authorization header of every request. This ensures that only authorized applications can access your account and perform operations.

Authentication Overview

The Aella for Merchants API uses Bearer Token authentication to secure all endpoints. This is a standard HTTP authentication method where you include your secret key in the Authorization header. Your secret key acts as your API credentials and should be kept secure at all times.

Base URL

All API requests should be made to:

https://api.aellaapp.com

Authorization Header

Include your secret key in the Authorization header using the Bearer token format:

curl https://api.aellaapp.com/wallets \
  -H "Authorization: Bearer your_secret_key"

Environments

There are 2 environments available:

1. Sandbox - For development and testing
2. Live - For production use

The same URL (https://api.aellaapp.com) is used for both Sandbox and Live. The API key used is what determines the environment.

Sandbox Environment

• Purpose: The sandbox environment is for development and testing. It allows you to simulate API behavior without affecting real-world data.
• Characteristics:
  • No real transactions occur.
  • Predefined test scenarios are available (e.g., specific account numbers for testing failures).
  • API Key Format: ae_sk_test_****

Live Environment

• Purpose: The live environment processes actual data and performs real transactions.
• Characteristics:
  • Production-grade performance and security.
  • Real-world implications for every API call.
  • API Key Format: ae_sk_live_****