Wooble
Build your proof

Wooble FastTrack · Level 1: Foundational

REST API integration project

Pull the partner's data properly, at HaulstackSimulation

The job that syncs shipments from a carrier's API prints the wrong numbers. Make it survive the API and get ops the real ones.

  • You're the AI-enabled Full-Stack Developer
  • About 60 minutes, no timer
  • 5 days to hand in
  • Checked the moment you hand in
  • Free
Start this problem

Free. Sign up in a minute and you go straight to it.

The situation

Ritika MenonEngineering Lead, Integrations, Haulstack

Hey, welcome to Integrations!

Ops review October with Trukvo, our biggest carrier, on Friday. Our intern wrote a small job that pulls our shipments from Trukvo's API and prints the numbers ops want. It runs, it prints numbers, and ops say the numbers don't match what they see in Trukvo's portal. I trust the portal.

The download is the job, with our sandbox key for Trukvo's API already in .env. The sandbox serves the same data as live. I need, by tomorrow:

  1. How many of our shipments booked 1 to 21 October have been delivered.
  2. The total freight on those delivered shipments: what we owe Trukvo for them.
  3. How many came back RTO (returned to origin).
  4. How many are on the road right now: picked up or in transit.
  5. What Trukvo's API did that the job didn't handle. Ops will ask why the old numbers were wrong.
  6. A short note to me: what was wrong with the job, and what you changed.

Count each shipment once, as it stands now. Fix the job rather than working the numbers out by hand: we'll run it every morning. Send me a link to your fixed version.

Thanks, Ritika

When you start, you get Haulstack's handbook and your own data: the same story as everyone else's, with different records, so your answers are yours alone.

What you hand in

  1. 1Delivered: Shipments booked 1 to 21 October that have been delivered (a count)
  2. 2Freight on delivered: Total freight on those delivered shipments (₹) (in whole rupees)
  3. 3Returned to origin: Shipments that came back RTO (a count)
  4. 4On the road: Shipments picked up or in transit right now (a count)
  5. 5What Trukvo's API did: What did Trukvo's API do that the old job didn't handle? Pick everything you saw.
  6. 6Your working: A link to your fixed job: a GitHub repository, or a gist of your changes, shared so anyone with the link can see it. Leave your key out of it.
  7. 7A note to Ritika: 200 words at most.
  8. 8How you used AI: Your prompts or the chat, if you used it.

Your figures and what you saw the API do are checked against your own sandbox the moment you hand in. The pass mark is 70 of 100, and delivered and the freight on them must both be right. Hand in as often as you need; every hand-in is counted.

What passing earns

  • A step to your AI-enabled Full-Stack Developer · Level 1 badge: 1 of the 2 passes it needs, and the next level opens with it.
  • A badge page that anyone can check, which you can add to LinkedIn as a certification.
  • A project on your Wooble profile made from your hand-in, when you choose to add it.
  • 50 points for the pass.

More in Level 1