Season 3: Welcome to Engineering · Episode 7 of 8
The Integration Ticket
You play: AI Engineering Intern
Included with Core programme and Certification prep
The situation
A partner analytics integration is failing two ways at once. The partner's API returns 401 for every request, and the internal report that joins creators to their events is showing each creator three or four times with inflated numbers. Amara has the ticket; you have the afternoon.
What you'll learn
- Engineering bridge: HTTP methods and status codes, request headers and bearer auth, keeping secrets out of URLs, retrying transient failures with a cap, SQL joins and the fan-out problem, GROUP BY and COUNT, and parsing JSON safely.
Who you work with
Maya Chen
Senior AI Engineer · Your mentor
Amara Okafor
ML and Data Engineer
Scenes
- 1.Two bugs, one ticket
- 2.Read the 401
- 3.Fix the request
- 4.One row per creator
- 5.Parse what the partner sends
- 6.Integration check
What you leave with
You repaired the simulated API authentication and completed the stats GET within its three-attempt policy. The inner-join report aggregates the matched event rows, and the parser handles the supplied malformed and missing-field cases. Record its non-object and Boolean-input limits before extending it.