Resolve org/member context from *** session for billing proxy

Shipped

April 17, 2026 at 3:13 AM UTC

Author

kamo

Commit

936da4a

BillingService controllers require X-Org-Id and X-Member-Id headers. When calling directly (bypassing APIService), these weren't being set. Now the Next.js proxy reads the *** cookie, looks up the session in Redis, extracts orgID and memberID, and forwards them as headers.