Skip to content

Add API key security guidance to documentation#261

Open
warengonzaga wants to merge 1 commit intorelayprotocol:mainfrom
warengonzaga:waren/docs-improve-api-key-security-guidance
Open

Add API key security guidance to documentation#261
warengonzaga wants to merge 1 commit intorelayprotocol:mainfrom
warengonzaga:waren/docs-improve-api-key-security-guidance

Conversation

@warengonzaga
Copy link
Member

Summary

  • Adds a "Keeping Your API Key Secure" section to the API keys documentation
  • Covers leak risks, best practices (server-side only, env vars, gitignore), and what to do if compromised
  • Motivated by recurring integrator questions about API key sensitivity (e.g., Pylon #3652)

Test plan

  • Verify the new section renders correctly in Mintlify
  • Confirm the internal anchor link to #proxy-api resolves properly
  • Review content accuracy with the team

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants