Backend recipe
Bolt, with evidence.
Use a protected backend function or an owned Supabase ledger export.
Official docs checked · platform acceptance pending
Prepare and verify
- Confirm your project has server functions; a static frontend cannot safely call with a private key.
- Put the key in backend secrets, authenticate callers and use server-side fetch for the REST API.
- For a Supabase-backed ledger, review the export adapter and test exact purchase references.
Know the boundary.
No native Bolt integration. Supabase connection availability depends on the current Bolt plan; do not replace an existing database just to follow this recipe.
Start with synthetic data. Ropely staging remains restricted; a cloud-hosted recipe needs an accessible, authorized deployment. Account-level acceptance is separate from local SDK tests.