skills.rest
alfadocs
alfadocsOFFICIAL
Explore all skills by this author →
WebsiteGitHub

alfadocs-connected-app-api-key

Proxy AlfaDocs API requests through a Supabase Edge Function with Row Level Security.

Updated Mar 9, 2026
Search Tags:#supabase#row level security#api key#webhooks#proxy#edge function#alfadocs
One-click install
npx skills add https://github.com/alfadocs/ai-harness-instructions --skill alfadocs-connected-app-api-key
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: alfadocs-connected-app-api-key
Source: https://github.com/alfadocs/ai-harness-instructions/tree/main/lovable/skills/alfadocs-connected-app-api-key
Command: npx skills add https://github.com/alfadocs/ai-harness-instructions --skill alfadocs-connected-app-api-key

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about alfadocs-connected-app-api-key

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I secure an AlfaDocs API key when building a frontend dashboard without exposing credentials to the browser?▼

To secure an AlfaDocs API key without exposing it to the browser, you can route requests through a Supabase Edge Function acting as a server-to-server proxy. This keeps credentials server-side while your frontend interacts safely with practice data.

How do I resolve practiceId and archiveId from AlfaDocs /me context for tenant-scoped data access?▼

You resolve practiceId and archiveId by querying the AlfaDocs /me context endpoint within your Supabase Edge Function. Once retrieved, these identifiers are reused to scope all subsequent API calls to the correct practice tenant.

How do I secure patient records synced from AlfaDocs using Supabase Row Level Security?▼

To secure synced AlfaDocs patient records, you apply Supabase Row Level Security policies that scope stored data by the resolved practiceId. This ensures queries only return records belonging to the specific tenant.

Can I use a generic UI component library to build an internal AlfaDocs app?▼

While generic UI libraries function, building an internal AlfaDocs app requires using the AlfaDocs UI component kit and its specific translation patterns. This ensures design consistency and proper integration with AlfaDocs data structures.

How do I parse AlfaDocs webhook payloads to sync patient appointment updates automatically?▼

To sync patient appointment updates, you parse incoming AlfaDocs webhook payloads within your Supabase Edge Function. The parsed data is then validated and written to your database using tenant-scoped Row Level Security rules.

Does this proxy approach work for writing patient records back to AlfaDocs via server-to-server requests?▼

Yes, the Supabase Edge Function proxy supports both reading and writing patient records. It safely forwards server-to-server requests to AlfaDocs, allowing your internal automations to update practice data without exposing the API key.

Related Skills

Explore More Software Engineering Skills→
alfadocsalfadocs

alfadocs-connected-app-oauth

Implement AlfaDocs OAuth2 PKCE login via a Supabase Edge Function.

Official
Advanced
alfadocsalfadocs

alfadocs-patient-deep-link

Generate AlfaDocs patient deep links from practice and patient IDs.

Official
Intermediate
dadbodgeoffdadbodgeoff
783

row-level-security

Implement PostgreSQL Row Level Security policies for multi-tenant data isolation.

Community
Advanced
BaraArdiwinataBaraArdiwinata

authentication-proxy

Route browser authentication requests through Next.js API proxy routes.

Community
Intermediate