Developer advocates rejecting empty API completions as failed user actions

A software developer argues that an API call returning a successful status code but empty data should be treated as a failed user action, not a success. They critique systems where a user saves data, a green success toast appears, but the intended content is not actually stored. The author proposes a shared contract object across application layers to explicitly check for and flag empty or truncated completions as failures. They provide a code example that prevents persisting blank summaries and returns a client-readable failure reason. The article urges developers to assert these failure conditions in tests rather than discovering them through user complaints.