---
title: "Record a client item delivered outside BriefGate"
method: POST
path: "/v1/intakes/{id}/items/{key}/received-outside"
tags: ["Intakes"]
---

# Record a client item delivered outside BriefGate

`POST /v1/intakes/{id}/items/{key}/received-outside`

## Request

- Base URL: `https://api.briefgate.dev`
- URL: `https://api.briefgate.dev/v1/intakes/{id}/items/{key}/received-outside`
- Auth: HTTP bearer

The client delivered this item some other way — e-mail, WhatsApp, a phone call — and the owner is settling it so the intake can complete. Only items with `assignee: "client"` can be marked here; an owner's own task is ticked off with POST .../done instead. The item moves to `approved` with `received_outside: true`; `value` is left untouched (normally still null), so a caller must check `received_outside` before treating it as a genuine client-supplied answer. Runs the same completion check a client submission runs, so this can complete the intake and fire the same webhook, owner notice and (unless the account has turned it off) client completion mail.

## Path parameters

- `id` string, required
- `key` string, required

## Request body

- object
  - `note` string: Optional — how/when it was received.

## Response `200`

Item marked received

- object
  - `key` string
  - `status` 'approved'
  - `received_outside` true
  - `intake_status` 'draft' | 'sent' | 'in_progress' | 'completed' | 'archived'

## Other responses

- `400`: The item belongs to the owner, not the client
- `401`: Missing or invalid API key
- `403`: Authenticated but not allowed to perform this action
- `404`: Resource not found
- `409`: The item has already been received, or is currently waived
- `422`: Validation error — the body shape is correct but values are invalid

---

[API](https://skmtc.dev/briefgate/apis/briefgate-api.md) · [All operations](https://skmtc.dev/briefgate/apis/briefgate-api/llms.txt) · [OpenAPI document](https://skmtc.dev/briefgate/apis/briefgate-api/revisions/b21afed4748b?raw)