Routine API Integration

[dhakar66]

Implement POST /routines — Create Routine with First Time Block

Endpoint

POST /api/v1/routines (Bearer JWT auth)

What it does

Creates a new routine for the authenticated user along with the first time block and its sessions. Used when no routine exists yet for the user.

Request Body (CreateTimeBlockRequest)

{
  "time": "06:00",
  "time_int": 600,
  "notification_enabled": true,
  "sessions": [
    {
      "session_type": "PLAN",
      "source_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
      "display_order": 0
    }
  ]
}

Success Response — 201

Returns RoutineWithTimeBlocksResponse:

{
  "id": "routine-uuid",
  "time_blocks": [
    {
      "id": "time-block-uuid",
      "time": "06:00",
      "time_int": 600,
      "notification_enabled": true,
      "sessions": [
        {
          "id": "session-uuid",
          "session_type": "PLAN",
          "source_id": "a1b2c3d4-...",
          "title": "AIY - Introduction",
          "language": "en",
          "image_url": "https://...",
          "display_order": 0
        }
      ]
    }
  ]
}

Error Responses

Code	Meaning
401	Invalid/missing JWT
409	Routine already exists for this user
422	Validation error (no sessions, duplicate plan, bad time format)

Validation Rules

• Must have at least one session
• A plan source_id can only appear once across the entire routine
• time must be valid HH:MM 24-hour format (00:00–23:59)
• session_type is either PLAN or RECITATION

[dhakar66]

Routine Data Mapping

---

Overview

Local (Hive)

• RoutineData
  • blocks[]
    • RoutineBlock
      • id (local UUID)
      • hour
      • minute
      • notificationEnabled
      • items[]
        • RoutineItem
          • id (plan/text ID)
          • title
          • imageUrl
          • type (plan / recitation)
          • enrolledAt

API (Server)

• RoutineWithTimeBlocksResponse
  • id (routine_id) → store in Hive
  • time_blocks[]
    • TimeBlockDTO
      • id (server UUID)
      • time (e.g. "06:00")
      • time_int (e.g. 600)
      • notification_enabled
      • sessions[]
        • SessionDTO
          • id (session UUID)
          • session_type (e.g. "PLAN" / "RECITATION")
          • source_id → maps to RoutineItem.id
          • title
          • language
          • image_url
          • display_order → maps to index in items[]

---

[dhakar66]

local routine data has to sync with the api.

[dhakar66]

Question:
when a user adds a plan to their routine in EditRoutineScreen. This affects which day opens when tapping the plan from the routine view (it can differ from the server's startedAt).

Drop it — always use the server's startedAt.
Add it to the API — extend the session schema with an optional enrolled_at field.