Authentication

​

Overview

​

API Key Types

​

Public Keys (Publishable Keys)

• Use case: Client-side integrations and Monieswitch Checkout
• Security: Safe to expose in frontend code and mobile applications
• Prefix: pk_live_ (production) or pk_test_ (sandbox)
• Capabilities: Limited to creating payment sessions and retrieving public data

​

Secret Keys (Private Keys)

• Use case: Server-side integrations and full API access
• Security: Must be kept confidential and stored securely
• Prefix: sk_live_ (production) or sk_test_ (sandbox)
• Capabilities: Full API access including sensitive operations

​

Getting Your API Keys

1. Log in to your Monieswitch Dashboard
2. Navigate to Settings → API Keys
3. Generate new keys or copy existing ones
4. Store them securely in your application’s environment variables

​

Making Authenticated Requests

​

Authentication Method

Authorization: Bearer sk_live_your_secret_key_here

​

Example Request

curl -X GET "https://nini.monieswitch.com/payments" \
  -H "Authorization: Bearer sk_live_your_secret_key_here" \
  -H "Content-Type: application/json"

​

Code Examples

const headers = {
  Authorization: `Bearer ${process.env.MONIESWITCH_SECRET_KEY}`,
  "Content-Type": "application/json",
};

const response = await fetch("https://nini.monieswitch.com/payments", {
  method: "GET",
  headers: headers,
});

import os
import requests

headers = {
    'Authorization': f'Bearer {os.environ.get("MONIESWITCH_SECRET_KEY")}',
    'Content-Type': 'application/json'
}

response = requests.get('https://nini.monieswitch.com/payments', headers=headers)

$headers = [
    'Authorization: Bearer ' . getenv('MONIESWITCH_SECRET_KEY'),
    'Content-Type: application/json'
];

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, 'https://nini.monieswitch.com/payments');
curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);

​

Base URL

https://nini.monieswitch.com

​

Environment Variables Setup

​

Sandbox Environment

# Sandbox keys for testing
MONIESWITCH_PUBLIC_KEY=pk_test_your_public_key_here
MONIESWITCH_SECRET_KEY=sk_test_your_secret_key_here

​

Live Environment

# Production keys
MONIESWITCH_PUBLIC_KEY=pk_live_your_public_key_here
MONIESWITCH_SECRET_KEY=sk_live_your_secret_key_here

​

Key Management Best Practices

​

Key Rotation

• Rotate API keys periodically (recommended: every 90 days)
• Generate new keys before revoking old ones to prevent service interruption
• Update all applications and services with new keys before revocation

​

Access Control

• Use different keys for different services or applications
• Implement key-specific scoping when available
• Monitor key usage through your dashboard

​

Incident Response

1. Immediately revoke the compromised key from your dashboard
2. Generate a new key pair
3. Update all affected applications
4. Monitor for any unauthorized usage

​

Troubleshooting

​

Common Authentication Issues

​

Getting Help

• Check our Error Handling Guide for detailed error codes
• Contact support at [email protected]