---
title: visits.addRecording | Doing Work API
description: Add a walkthrough recording the worker sent you, during or after the visit. Listen to it yourself first: if it is clearly a different job or not a walkthro
url: https://doingwork.work/docs/reference/visits-addrecording/
---

# visits.addRecording

Add a walkthrough recording the worker sent you, during or after the visit. Listen to it yourself first: if it is clearly a different job or not a walkthrough, tell the worker and ask before you add it. Send what the worker said it is (described_as), your transcript, and recorded_at (when the clip was made, from the file) if you have it. Core keeps no audio: keep the clip on your side and send your clip_ref. The transcript becomes a voice memo note on the visit with any measurements and the worker's notes. Getting any consent the law requires to record is up to the worker and the shop.

|  |  |
|---|---|
| Who | Agents can call this |
| REST | `POST /v1/visits/recording` |
| MCP tool | `visits_addRecording` |
| Writes | yes, send an Idempotency-Key |
| Area | [Scheduling and visits](https://doingwork.work/docs/reference/#scheduling-and-visits) |

## When to use it

Use these when a worker is heading to, standing at, or just leaving a visit. Everything happens in conversation with the worker: there are no buttons for them to tap and no app to open.

## What to tell the owner

Say what you did in plain words and what happens next.

## Input

| Field | Type | Required |
|---|---|---|
| `visit_id` | string (uuid) | yes |
| `described_as` | string | no |
| `transcript` | string | yes |
| `recorded_at` | string (date-time) | no |
| `duration_seconds` | integer | no |
| `transcribed_with` | string | no |
| `clip_ref` | string | no |
| `worker_notes` | string | no |
| `measurements` | array | no |
| `measurements[].label` | string | yes |
| `measurements[].value` | number | yes |
| `measurements[].unit` | string | no |

## Example

```http
POST https://doingwork.work/v1/visits/recording
content-type: application/json
Idempotency-Key: 3f1c...

{
  "visit_id": "00000000-0000-4000-8000-000000000000",
  "transcript": "..."
}
```

## Output

JSON. The response shape isn't published yet; read the fields you need and ignore the rest. Errors are `{code, message, status}`.

## Errors

| Code | Status | What to do |
|---|---|---|
| `invalid_input`, `invalid_token`, `rate_limited` |  | Can happen on any call. See [errors](https://doingwork.work/docs/errors/). |