API Keys

Overview

API keys authenticate your server-side applications with the AgentWallex API. Each key starts with the awx_ prefix and is tied to your account.

Creating API Keys

Create API keys through the dashboard or the REST API (requires JWT authentication):

Via Dashboard

Log in to the AgentWallex Dashboard.
Navigate to Settings > API Keys.
Click Create API Key.
Give the key a descriptive name (e.g., production-backend, staging-ci).
Copy and securely store the key — it is only shown once.

Via API

curl -X POST https://api.agentwallex.com/api/v1/api-keys \
  -H "Authorization: Bearer eyJhbGciOi..." \
  -H "Content-Type: application/json" \
  -d '{"name": "production-backend"}'

The full API key is only returned once at creation time. Store it immediately in a secure secrets manager.

Listing API Keys

curl -X GET https://api.agentwallex.com/api/v1/api-keys \
  -H "Authorization: Bearer eyJhbGciOi..."

The response includes key metadata but never the full key value:

{
  "data": [
    {
      "id": "key_abc123",
      "name": "production-backend",
      "prefix": "awx_...x4f2",
      "created_at": "2025-06-01T10:00:00Z",
      "last_used_at": "2025-06-15T14:30:00Z"
    }
  ]
}

Rotating API Keys

Create a new key

Create a new API key via the dashboard or API.

Update your application

Deploy the new key to your application’s environment variables.

Verify the new key works

Confirm that API calls succeed with the new key.

Delete the old key

Remove the old key to prevent unauthorized access:

curl -X DELETE https://api.agentwallex.com/api/v1/api-keys/key_abc123 \
  -H "Authorization: Bearer eyJhbGciOi..."

Rotate API keys at least every 90 days. Set a calendar reminder or automate rotation with your CI/CD pipeline.

Rate Limits

API rate limits depend on your plan tier:

Plan	Requests/min	Requests/day	Concurrent connections
Starter	60	10,000	5
Growth	300	100,000	25
Enterprise	Custom	Custom	Custom

When you exceed the rate limit, the API returns a 429 Too Many Requests response with a Retry-After header:

{
  "code": "rate_limit_exceeded",
  "type": "rate_limit_error",
  "message": "Rate limit exceeded. Retry after 30 seconds."
}

Rate limits are applied per API key. If you need higher limits, contact the AgentWallex team or upgrade your plan.

Best Practices

One key per environment — Use separate keys for development, staging, and production.
Name keys descriptively — Include the environment and service name (e.g., prod-payment-service).
Monitor usage — Check last_used_at to identify unused keys that should be deleted.
Never share keys — Each team member or service should have its own key.
Use a secrets manager — Store keys in AWS Secrets Manager, HashiCorp Vault, or similar tools rather than in .env files on disk.

Getting Started

Platform

Core Features

Guides

Overview

Creating API Keys

Via Dashboard

Via API

Listing API Keys

Rotating API Keys

Rate Limits

Best Practices

​Overview

​Creating API Keys

​Via Dashboard

​Via API

​Listing API Keys

​Rotating API Keys

​Rate Limits

​Best Practices

Overview

Creating API Keys

Via Dashboard

Via API

Listing API Keys

Rotating API Keys

Rate Limits

Best Practices