Challenge · API debugging · Premium
The 200 that failed
Meridian's nightly claims sync reports success and the totals are wrong. The claims API returns errors inside 200 responses and a cursor the client ignores. Find both, fix the client's config, and make the dry run tell the truth.
- intermediate
- about 30 min
- 4 objectives
- par 11 steps
- Meridian Health
Mission workspace
This mission is part of premium, with every challenge and incident in the lab. The brief below is the whole problem; the box, the hints and the debrief are what you unlock.
Get full Premium access · ₹2,000 / $25
Every answer, concept and course, every paper breakdown, all published video lessons, hands-on FDE Lab missions, Premium PDF guides and companion files, the full practice-test bank and work-sample downloads. Referral Premium excludes guide PDFs and their companion files.
6 months · One payment · No auto-renewal
Study alongside free video lessons.
Brief
- Customer
- Meridian Health (synthetic customer; every payload and log on this box is made up for the exercise)
- Situation
- Meridian's finance team reconciles claims monthly and is short 12 claims and one whole page against the source system. The sync job logs
synced 240 claims, 0 errorsevery night. The claims API is a partner system nobody at Meridian owns; its documentation is in this directory. - Your role
- You are the FDE who inherited the sync. You can read the recorded API pages, the client's config and source, and run the sync in dry-run mode against the recorded pages.
- Goal
- Count the claims the API rejected inside 200 responses, name the pagination bug, fix both in the client's config, and show a dry run that reports what actually happened.
Objectives
- 1.Count the claims the API rejected inside 200 responses (you commit to an answer)
- 2.Name the pagination bug (you commit to an answer)
- 3.Fix the client: error envelopes are failures and paging stops on a null cursor
- 4.Show a dry run that reports 264 synced and 12 failed