Authentication

The Wallet-as-a-Service (Palisade) API uses API keys for authentication. This guide explains how to authenticate your API requests.

Overview

All API requests to Wallet-as-a-Service (Palisade) must be authenticated using API credentials. These credentials consist of:

• API Key ID - A unique identifier for your API credential
• API Secret - A secret key used to sign requests

Generating API credentials

1. Log in to the Wallet-as-a-Service (Palisade) console
2. Navigate to API Credentials
3. Click Create API credential
4. Configure the credential name and permissions
5. Copy and securely store the API key and secret

Authentication methods

Bearer token authentication

For most API endpoints, use Bearer token authentication:

curl -X GET "https://api.palisade.co/v1/vaults" \
  -H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json"

Request signing

For sensitive operations, requests may require cryptographic signing. The signing process involves:

1. Creating a canonical request string
2. Signing the string with your API secret
3. Including the signature in the request headers

Token management

• Access tokens have a limited lifetime
• Refresh tokens before they expire to maintain session continuity
• Revoke compromised credentials immediately from the console

Best practices

• Rotate credentials regularly - Update API credentials periodically
• Use least privilege - Only grant permissions that are necessary
• Secure storage - Never store credentials in source code or version control
• Monitor usage - Review API credential activity for unauthorized access

Error responses

For more information on API credentials, see API credentials best practices.