Skip to main content
Founder Sherpa exposes two API endpoints. Most data access is handled through the Supabase client libraries using RLS-protected table queries.

​
Transcript Import

​
Parse transcript

POST /api/import/{importId}/parse
Triggers AI parsing of an uploaded transcript. The import record must already exist (created through the upload UI). Processing runs asynchronously — poll the import status to check for completion. Request body: 
{
  "hypothesisIds": ["uuid-1", "uuid-2"]
}
FieldTypeRequiredDescription
hypothesisIdsstring[]YesUUIDs of hypotheses to use as context for evidence extraction. Must be non-empty.
Responses:
StatusDescription
200Parsing initiated successfully
400Invalid request body or missing hypothesisIds
401Missing or invalid authentication token
422Parsing failed (e.g., import not found or already processed)
Authentication: Bearer token (Supabase Auth JWT)

​
Notifications

​
Trigger digest emails

POST /api/notifications/digest?frequency=daily
Sends activity digest emails to eligible users. This endpoint is protected by CRON_SECRET and is intended to be called by Vercel Cron, not by end users. Query parameters:
ParameterTypeRequiredValues
frequencystringYesdaily or weekly
Responses:
StatusDescription
200Digests processed. Returns { ok: true, frequency, sent }
400Invalid or missing frequency parameter
401Missing or invalid CRON_SECRET
Authentication: Authorization: Bearer <CRON_SECRET>

​
Supabase Data API

For querying and mutating data (projects, personas, hypotheses, evidence, questions, etc.), use the Supabase Data API with the apikey and Authorization headers described in the Authentication guide. The Supabase Data API provides a REST interface auto-generated from the database schema, with full support for filtering, pagination, and relationships. All access is governed by Row Level Security policies that enforce workspace membership.