Automate Your Secrets: Introducing Developer API Keys
The GUI is great for humans. But your build servers, cron jobs, and Slack bots don't have hands. Users have been asking for a way to integrate EnvShareApp into their automated workflows.
Today, we're launching **Developer API Keys**. A secure, standard way to create ephemeral secrets programmatically.
The Power of `Authorization: Bearer`
We've adopted the industry-standard Bearer token authentication. Once you generate a key from your dashboard, you can carry it in the header of your HTTP requests.
curl -X POST https://envshare.app/api/v1/secrets \
-H "Authorization: Bearer env_live_sk_..." \
-d '{
"secret": "DATABASE_URL=postgres://...",
"ttl": 3600,
"reads": 5
}'Result: A JSON response containing your secure link.
Use Cases
CI/CD Pipelines
Send build artifacts or temporary passwords to developers via Slack automatically after a deployment fails.
Internal CLI Tools
Wrap our API in your internal `acme-cli` tool.
`acme share .env` -> returns an EnvShareApp link.
Bypassing CAPTCHAs
One of the biggest pain points for automation is the "I am not a robot" check. Our public API relies on Cloudflare Turnstile to prevent abuse.
API Keys bypass Turnstile completely. Because your requests are authenticated and rate-limited against your account, we treat you as a trusted actor. No puzzles to solve.
Managing Keys
Head over to your Team Dashboard. You can issue multiple keys (e.g., one for "Production CI", one for "Staging Bot") and revoke them individually if they leak.
Start Building
API Keys are available on all accounts directly from the dashboard.
Generate Your First Key