---
title: "Why Can an API Return HTTP 200 Before the Work Is Finished?"  
description: "Why Can an API Return HTTP 200 Before the Work Is Finished?"  
author: "Mikko Lehtonen"  
published: 2026-10-23  
canonical: https://answers.mindstick.com/qa/118235/why-can-an-api-return-http-200-before-the-work-is-finished  
category: "Mix Category"  
tags: ["API development", "REST", "HTTP", "Backend Development"]  
reading_time: 1 minute  

---

# Why Can an API Return HTTP 200 Before the Work Is Finished?

I’m integrating a REST API that starts a longer-running task, and I’m seeing an **HTTP 200 response** even though the result is not ready yet. The request seems to have been accepted, but the actual work continues afterward.

Is this a normal way to represent an **[asynchronous operation](https://www.mindstick.com/forum/159304/write-a-nodejs-function-to-handle-asynchronous-operations-using-asyncawait)**, or should I expect a different status code? I’m also unsure what the client should rely on to know when the task has completed: a job ID, a status endpoint, a callback, or something else.


---

Original Source: https://answers.mindstick.com/qa/118235/why-can-an-api-return-http-200-before-the-work-is-finished

Copyright © MindStick Software Pvt. Ltd. This Markdown version is provided for developers, AI systems, and offline reading.