# Getting started with the Wallet-as-a-Service (Palisade) API

In this section
- [API credentials overview](/products/wallet/user-interface/api/what-are-credentials-in-palisade) – Understanding API security
- [API credentials best practices](/products/wallet/user-interface/api/api-credentials-best-practices) – Security recommendations
- [Manage API credentials](/products/wallet/user-interface/api/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.

## Overview

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


## Base URLs

| Environment | Base URL |
|  --- | --- |
| Production | `https://api.palisade.co` |
| Sandbox | `https://api.sandbox.palisade.co` |


## Prerequisites

Before you begin, ensure you have:

1. A Wallet-as-a-Service (Palisade) organization account
2. API credentials with appropriate permissions
3. A device configured for signing (if required)


## Quick start

### 1. Generate API credentials

1. Navigate to the **API Credentials** section in the Wallet-as-a-Service (Palisade) console
2. Click **Create API credential**
3. Configure the credential name and permissions
4. Securely store the generated API key and secret


For detailed instructions, see [Manage API credentials](/products/wallet/user-interface/api/manage-api-credentials).

### 2. Authenticate your requests

All API requests must include authentication headers. Use Bearer token authentication:


```bash
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](/products/wallet/user-interface/api/api-credentials-best-practices).

## API reference

Explore the complete API documentation:

- [Wallet-as-a-Service (Palisade) API](/products/wallet/api-docs/palisade-api/palisade-api) - Core platform operations


## Best practices

- 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


## Support

For API support, contact [support@palisade.co](mailto:support@palisade.co).