alfadocs-connected-app-api-key

What problem does it solve?

This Skill helps you build private AlfaDocs tools for a single practice without exposing an API key in the browser. It is designed for internal dashboards, reports, and automations that need secure server-to-server access to practice data.

Core Features & Use Cases

• Server-side API access: Keep the AlfaDocs key in a Supabase Edge Function and proxy all requests through it.
• Tenant-scoped data handling: Resolve practiceId and archiveId from /me, then reuse them for every AlfaDocs call.
• Safe persistence and webhooks: Scope stored data by practice, protect it with Row Level Security, and parse webhook payloads correctly when AlfaDocs pushes updates.
• Design system guidance: Build the UI with the AlfaDocs component kit and translation patterns instead of generic UI libraries.
• Use case: Create an internal patient or appointment dashboard that reads AlfaDocs data, syncs changes, and never exposes credentials to end users.

Quick Start

Use this Skill to design a private AlfaDocs app that keeps the API key server-side, resolves practice context through a Supabase Edge Function, and safely forwards requests to AlfaDocs.