Register the authenticated Supabase identity as a mother account
const url = 'https://example.com/mother/accounts';const options = { method: 'POST', headers: { 'Idempotency-Key': 'example', Authorization: 'Bearer <token>', 'Content-Type': 'application/json' }, body: '{"expectedProfileRevision":0,"expectedAddressRevision":0,"fullName":"example","birthDate":"2026-04-15","address":{"postalCode":"example","roadAddress":"example","detailAddress":"example"},"consentAcceptances":[{"policyKey":"example","versionLabel":"example"}]}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/mother/accounts \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: application/json' \ --header 'Idempotency-Key: example' \ --data '{ "expectedProfileRevision": 0, "expectedAddressRevision": 0, "fullName": "example", "birthDate": "2026-04-15", "address": { "postalCode": "example", "roadAddress": "example", "detailAddress": "example" }, "consentAcceptances": [ { "policyKey": "example", "versionLabel": "example" } ] }'Native Supabase Auth signup, identity linking, and contact verification happen before this operation. The provider is re-read from the bearer session; this API never accepts credentials, OTP material, provider tokens, actor role, member id, or branch scope in the request body.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Header Parameters
Section titled “Header Parameters”Request Bodyrequired
Section titled “Request Bodyrequired”object
object
Responses
Section titled “Responses”Exact replay returns the original authoritative account profile
object
object
object
Active mother account, complete profile, receipts, and ownership relationship created
object
object
object
A valid Supabase bearer session is required
object
object
object
object
object
Authenticated staff or unsupported actor identity cannot create a mother account
object
object
object
object
object
Account identity or idempotency facts conflict without exposing another account
object
object
object
object
object
Profile input is invalid, contact is unverified, or a consent version is not published
object
object
object
object
object
Account creation did not reach a safe success state; repair reference may be returned