In this section
- API credentials overview – Understanding API security
- API credentials best practices – Security recommendations
- Manage API credentials – Create and manage credentials
The Wallet-as-a-Service (Palisade) API provides programmatic access to the Wallet-as-a-Service (Palisade) platform, enabling you to integrate digital asset custody and management into your applications.
The Wallet-as-a-Service (Palisade) API allows you to:
- Create and manage vaults and wallets
- Initiate and monitor transactions
- Configure policies and approval workflows
- Manage users and API credentials
- Set up webhooks for real-time notifications
| Environment | Base URL |
|---|---|
| Production | https://api.palisade.co |
| Sandbox | https://api.sandbox.palisade.co |
Before you begin, ensure you have:
- A Wallet-as-a-Service (Palisade) organization account
- API credentials with appropriate permissions
- A device configured for signing (if required)
- Navigate to the API Credentials section in the Wallet-as-a-Service (Palisade) console
- Click Create API credential
- Configure the credential name and permissions
- Securely store the generated API key and secret
For detailed instructions, see Manage API credentials.
All API requests must include authentication headers. Use Bearer token authentication:
curl -X GET "https://api.palisade.co/v1/vaults" \
-H "Authorization: Bearer YOUR_ACCESS_TOKEN" \
-H "Content-Type: application/json"For security best practices, see API credentials best practices.
Explore the complete API documentation:
- Wallet-as-a-Service (Palisade) API - Core platform operations
- Store API credentials securely and never expose them in client-side code
- Use the sandbox environment for testing before moving to production
- Implement proper error handling for all API calls
- Set up webhooks for real-time transaction status updates
For API support, contact support@palisade.co.