-
Notifications
You must be signed in to change notification settings - Fork 6
Expand file tree
/
Copy path.env.example
More file actions
26 lines (22 loc) · 998 Bytes
/
.env.example
File metadata and controls
26 lines (22 loc) · 998 Bytes
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
# ElevenLabs API Keys for E2E Testing
# Get your API keys from: https://elevenlabs.io/app/settings/api-keys
# ⚠️ CRITICAL: Use DEDICATED EMPTY TEST ACCOUNTS
#
# DO NOT use your production account or any account with deployed agents!
# E2E tests will create, modify, and DELETE agents during testing.
# Any existing agents in the workspace could be PERMANENTLY LOST.
#
# To set up test accounts:
# 1. Create TWO separate new ElevenLabs accounts at https://elevenlabs.io
# 2. Generate an API key for each account
# 3. Add the keys below
# 4. Keep these accounts empty - only for automated testing
# Primary test API key (required for all e2e tests)
ELEVENLABS_API_KEY=your_test_account_api_key_here
# For local development and testing:
# 1. Copy this file to .env (DO NOT COMMIT .env)
# cp .env.example .env
# 2. Add your TEST account API keys to .env
# 3. Verify both test accounts are empty
# 4. Run tests: npm run test:e2e
# Note: The .env file is gitignored and will not be committed