Welile ID API

Base URL https://welileid.com/api/v1 · Machine-readable spec at /api/v1/openapi.json

Sign-in flow

  1. Use the native Google Sign-In or Sign in with Apple SDK to get an ID token.
  2. POST it to /auth/google or /auth/apple. Tokens are inside session; user and has_profile are top-level fields.
  3. Store tokens in Keychain / Android Keystore. Send Authorization: Bearer <access_token> on every call.
  4. If has_profile is false, upload photos via /uploads then POST /profile.
  5. On a 401, call /auth/refresh and retry once.

Errors always look like { "error": { "code", "message" } }.

Load actual household data

  1. After restoring or refreshing the session, call GET /me. If no profile exists, finish ID setup.
  2. For Home, fetch /profile and /family in parallel. Family totals exclude the Anchor.
  3. For Family, fetch /members, /family and /members/linked-photos.
  4. My ID uses the profile signed photo URLs and /invites. Account also uses /memberships and /whatsapp/contacts.
  5. After saving, refetch affected lists and totals. Do not replace failed requests with invented or empty data.

Reads use the signed-in account’s actual records. Collection reads traverse database pages internally; there are no client pagination parameters. Email authentication endpoints are not yet available in this REST API.

System

Authentication

Account

Photos

Profile

Family members

Invites

WhatsApp

Ads

Admin

Not a replacement National ID.