Attach your account id to a stored event
Late user binding: when your auth provider mints the user id (Supabase, Auth0, Clerk, Firebase), there is no external_user_id to send at verdict time — screen first, create the user, then attach the id the provider returned. Portreeve keeps the mapping: a later review.resolved webhook names this id, and the identity graph gains the account edge as if the id had arrived on the original request.
Write-once. The first attach wins; replaying the same value returns 200 idempotently; a different value is a 409 conflict. An id sent at verdict time counts as the first write.
Authentication
Authorization: Bearer sk_live_… (or sk_test_…). Server-side only — never ship a secret key to a browser or a mobile app. The key determines the tenant and the mode; there is no mode parameter on any request.
Path parameters
The event id returned by POST /v1/verdict.
Request
Your user id for the account this event belongs to — the same value you would have sent on the verdict call had your auth provider not minted it afterwards. 1–256 characters, write-once.
Response
The id is attached (or was already attached with this exact value).
Always true. The endpoint has no failure mode that returns 200.