Share with family
Coordinate household alerts without sharing an account or device. A free family has one owner and up to three additional members, with shared services and unlimited notifications.
Invite the household
A household can share a Family account group while each person keeps their own sign-in. Create it through the signed-in POST /api/teams route, or POST /api/agent/teams with the required scope, using kind: "family". An account can join only one family.
{"name":"Our family","kind":"family"}notify families create "Our family"
notify families invite family_id --email person@example.com
notify families listReplace family_id with the returned ID. IDs retain the team_… prefix; check kind to identify a family. Inspect people with notify families get, members, and invites. Owners may rename, remove-member, or revoke-invite; members may leave.
The owner has three additional places. Pending invitations reserve a place until they expire or are revoked; trying to exceed capacity returns 409. Invitees join as member. Families have no admin role or domain-restricted invitations.
The recipient opens the invite link and signs in on the website. POST /api/team-invites/:code/accept requires a human session; an email-addressed invitation is restricted to that account.
Share services and apps
A shared service can collect a household answer. Any accepted family member using a supported interactive client may respond, and the first valid server-confirmed answer settles the prompt. respondingUserId identifies that person. Unaccepted invitees, removed members, and outsiders cannot respond. The service creator retains its callback configuration and webhook credential.
To share your service, POST { "familyId": "team_…" } to /api/services/:id/share or /api/agent/services/:id/share. POST { "familyId": null } to make it personal. The agent route needs services:write.
notify services share service_id --family family_id
notify services share service_id --personalMembers receive shared alerts and have their own read state for shared inbox history. The original creator controls sharing, token rotation, and webhook URL access. The family owner may rename or delete a shared service. Leaving the family returns the creator’s services to personal use.
A family’s accepted members have unlimited notifications. Device targeting, interactive answers, callbacks, activities, and shared web apps remain included. Each member registers and manages their own devices.
403 for families: rotations, paging, device groups, member-device administration, domain verification, audit logs, retention, and team billing. For a family web app, POST { "teamId": "team_…" } to /api/apps/:appId/share or /api/agent/apps/:appId/share. The app’s original contributor can also use notify apps share app_id --team team_id. List shared apps with GET /api/teams/:familyId/apps; every viewer approves app sign-in individually.Bring a web app
Make your warehouse board or household planner available inside Notify. Register its origin and send updates that open the relevant page. Add optional microAuth() when your site needs sign-in.
Delivery and reliability
Understand what a send proves, how retries behave, and how device availability affects an update. Use these rules when turning the guides into unattended workflows.