notes · thoughts ·
The back-and-forth of API integration is work too
Finding missing fields, requesting fixes, and checking again are part of integration. If that time goes unrecorded, it disappears from the schedule.
API integration brings to mind making a call and putting the response on screen. But much of the actual work happens in between. A required field is missing, a type differs from what was expected, or an empty array breaks an assumption in the UI. I check, report it, hear that it has been fixed, and check again.
If we treat this as mere conversation, it leaves almost no trace in the schedule. The frontend ticket is still in progress while the API ticket is already complete. Looking back, it may seem that building the screen took too long. What I was doing during that time was making the response usable.
What does “done” cover?
When the backend says something is done and the frontend says it is ready to integrate, they may mean different states. An accessible endpoint is not enough. We also need to check whether the response shape has been agreed on, required fields are present, and the UI can distinguish the main failure cases.
I would like us to share a definition of API readiness. An up-to-date specification, a sample response, and a way to check success and the main failure cases would reduce uncertainty at the start. This is not about preventing every exception in advance. I want us to see the same picture of what is ready and what still needs checking.
It has to be recorded to be estimated
If I investigate a missing field, I record it in the ticket. I record the fix request and the follow-up check too. Making the integration process visible seems better than digging through old conversations to explain where the time went.
This is not a record for shifting responsibility elsewhere. It is a way to include recurring work in the next estimate. Writing the call quickly does not make response validation and coordination disappear. If we estimate integration as a single connection, the same work returns as an unexpected delay every time.