---
title: "get_status for a task"
method: GET
path: "/tasks/{task_id}"
---

# get_status for a task

`GET /tasks/{task_id}`

## Request

- Base URL: `https://api.handsforagents.com/v1`
- URL: `https://api.handsforagents.com/v1/tasks/{task_id}`
- Auth: HTTP bearer

Always read next_action: one or two sentences on what to do now (wait; review the quote and call create_task; pay checkout_url; call confirm_delivery), with paid, quote_valid_until and expected_ship_date. messages is the thread with the operator, newest first (from: operator or agent). Every status can change at any time: call again whenever the user asks, never answer from memory, and report only what the response says, without conclusions of your own. This REST answer is always the complete record; the MCP tools get_status, create_task and confirm_delivery answer briefly by default (get_status with full=true returns this complete record). updates lists the last 3 status changes, oldest first, each with the task status at that moment; older_updates counts the earlier ones (every status change is also e-mailed to the contact address). To answer an operator question, call get_status with message: send the same request as POST with a JSON body {"message": "..."} (plain text, 1-2000 characters); it is stored in the same thread and e-mailed to the operator, and the answer is the usual status, including your message (message_sent: true). Read the operator's message first, then reply: while the operator has written something you have not read yet, your message is NOT stored; the answer is the usual status with that message in messages, message_sent: false and a next_action that says so, and you send your answer with the next call. Send it once and only with what the user told you: the same text again within 10 minutes is ignored (duplicate_ignored: true). E-mail to tasks@handsforagents.com with the quote_id in the subject still works. test_mode true marks a test order: nothing is paid or invoiced.

## Path parameters

- `task_id` string, required

## Response `200`

Task status, updates, evidence and shipments

- Task
  - `task_id` string, required
  - `quote_id` string, required
  - `status` 'awaiting_payment' | 'paid' | 'in_progress' | 'awaiting_balance' | 'delivered' | 'confirmed' | 'disputed' | 'refunded' | 'cancelled', required: The only task statuses there are, in the usual order: awaiting_payment, paid, in_progress, delivered, confirmed (awaiting_balance with a deposit; disputed, refunded, cancelled). paid is not in_progress: the operator sets in_progress when the work starts, and delivered (not the parcel arriving) is what allows accepting with confirm_delivery.
  - `checkout_url` string, uri: The payment link of the payment that is due now (GET /pay/{task_id}, signed; opening it redirects to a Stripe Checkout page). Present while status is awaiting_payment or awaiting_balance and the link is valid: 4 days from when the payment was created, 28 for a balance. Never present for a test order.
  - `checkout_expires_at` string, date-time: When checkout_url stops working. Present together with checkout_url.
  - `payments` object[]
    - `kind` 'full' | 'card_hold' | 'deposit' | 'balance', required
    - `amount` number, required
    - `currency` 'EUR' | 'USD', required
    - `status` 'awaiting' | 'authorised' | 'paid' | 'released' | 'refunded' | 'simulated', required
    - `checkout_url` string, uri: The payment link, while this payment is awaiting and the link is valid.
    - `checkout_expires_at` string, date-time
    - `invoice_url` string, uri
  - `invoice_url` string, uri
  - `paid` boolean: True when nothing is owed right now: a payment is settled (paid, card hold authorised, or simulated in a test order) and none is awaiting.
  - `quote_valid_until` string, date
  - `expected_ship_date` string, date: The delivery or dispatch date stated in the quote.
  - `scope` string: What was quoted, as stated in the quote.
  - `deliverables` string: What you receive, as stated in the quote.
  - `next_action` string: One or two sentences in English: what the agent or the client should do now.
  - `messages` object[]: The thread with the operator, newest first: the operator's notes and your own replies (from: agent over REST; the MCP tools show your own replies as from: you). An operator message you have not been shown yet is always included, also in the answer to your own reply (a message of yours sent while it is unread is not stored: message_sent is false). Read the operator's message first, then reply: call get_status with message (POST with a JSON body over REST); e-mailing the tasks address with the quote_id in the subject also works.
    - `at` string, date-time, required
    - `from` 'operator' | 'agent', required
    - `text` string, required: Plain text, at most 2000 characters. Never HTML.
  - `duplicate_ignored` boolean: Present and true only in the answer to a POST whose message was ignored because the same text was already the newest message of the thread (sent within the last 10 minutes).
  - `message_sent` boolean: Present only in the answer to a POST with a message: true, the message was stored and e-mailed to the operator; false, it was NOT stored because the operator had written something you had not read yet (that message is in messages, now marked as read; next_action says so): send your answer again. Absent when the same text was ignored (duplicate_ignored) and in every plain status call.
  - `test_mode` boolean: Present and true only for a test order: no payment link; the operator simulates the payment after the order is placed (until then nothing is paid or simulated); no invoice, no contract.
  - `performed_by` string: Name of the person who did the work.
  - `updates` object[]: The last 3 status changes and events, oldest first. status is the task status at the moment of that event (not the current one).
    - `at` string, date-time
    - `status` string
    - `note` string
  - `older_updates` integer: How many earlier updates are not listed. Present only when there are any; every status change is also e-mailed to the contact address.
  - `evidence` object[]
    - `name` string
    - `url` string, uri
    - `media_type` string
    - `captured_at` string, date-time
    - `latitude` number
    - `longitude` number
  - `shipments` object[]
    - `carrier` string
    - `tracking_number` string
    - `tracking_url` string, uri

## Other responses

- `401`: Error
- `404`: Error

---

[API](https://skmtc.dev/handsforagents/apis/hands-for-agents-api.md) · [All operations](https://skmtc.dev/handsforagents/apis/hands-for-agents-api/llms.txt) · [OpenAPI document](https://skmtc.dev/handsforagents/apis/hands-for-agents-api/revisions/8349b6792c56?raw)