bootstrap-api-keys

API key authentication in a Phoenix LiveView app is added by generating an ApiKey schema, context functions for create and revoke, a management LiveView UI, and a Bearer token auth plug. This provides end-to-end CRUD with secure token handling at /api-keys.

Secure API key storage in a Phoenix backend uses prefix plus SHA256 hash verification, never storing raw tokens. The raw token is shown only once after creation, and keys support optional expiration and soft revocation for safe access control.

The API key management UI integrates with existing Phoenix auth pipelines by discovering your current auth plug and router entries first, then mounting a scoped LiveView management page within authenticated sessions to avoid overwriting partial implementations.

Soft revocation lets you revoke an API key in Phoenix without deleting the database record. The generated context functions include a revoke operation that disables the key while retaining it, along with optional expiration support for time-limited access.

Bearer token verification for scoped API endpoints in Phoenix uses a generated auth plug that checks the prefix and SHA256 hash of the incoming token. The plug integrates into your router pipeline for authenticated and write-required API endpoints.

Existing migrations, schemas, context functions, and LiveView components are audited first during generation to avoid duplicating or overwriting partial implementations. The tool uses discovery-driven gap filling to only add what is missing for API key management.