Project

General

Profile

Actions
Copy link

Task #136

open
SG SG

Task #1: Product Improvement

Task #3: ULIP application/Integration

15. VAHAN 04/05/06 Migration

Task #136: 15. VAHAN 04/05/06 Migration

Added by Srishti Ghosh 8 days ago. Updated 8 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Srishti Ghosh
Target version:
Backlogs
Start date:
10/12/2026
Due date:
10/23/2026 (Due in 1 day)
% Done:

50%

Estimated time:
Spent time:
0:55 h

Description

User Story
As a Canofy user, I want vehicle verification to keep working after ULIP retires VAHAN/01-03, so that vehicle lookups don't break without notice.

Description
ULIP has made migration from VAHAN/01/02/03 (XML responses) to VAHAN/04/05/06 (JSON responses) mandatory. Inputs stay the same (vehicle number, chassis number, engine number); the response changes from XML with snake_case tags to a JSON object with camelCase keys.

ULIP access process

  1. Submit a data request for the VAHAN/04-06 staging APIs (reusing the existing use case)
  2. Generate the addendum from the eTnC tab, print on letterhead, upload signed and sealed copy
  3. After approval, upload test cases
  4. Production access enabled once test cases are approved

Progress so far

  • Live check on staging (12/10): VAHAN/04-06 return 403, so they are not yet granted to our credentials. VAHAN/01-03 still work.
  • App changes built on branch feature/AI-vahan-04-05-06-migration: client calls VAHAN/04/05/06, response parser rewritten for JSON, new not-found message handled, offline tests added.
  • Also fixed existing failure-path bugs in vehicle verification (failed searches not being saved, error message being cleared, history always showing success).

Pending

  • ULIP grant for VAHAN/04-06 on staging
  • Live test against the real responses, then version bump, PR into test, test cases upload
Actions
Copy link

Also available in: PDF Atom