---
title: "Record an outcome (legacy) or change a test gift's status"
method: PATCH
path: "/sends/{id}"
tags: ["Gifts"]
---

# Record an outcome (legacy) or change a test gift's status

`PATCH /sends/{id}`

## Request

- Base URL: `https://gtmswag.com/api/v1`
- URL: `https://gtmswag.com/api/v1/sends/{id}`
- Auth: HTTP bearer

Keys may set `outcome` only; prefer `POST /sends/{id}/outcomes`, which deduplicates. Changing `status` needs a signed-in person (keys get 403 HUMAN_APPROVAL_REQUIRED) and only follows the allowed steps on test gifts; live fulfillment status is managed by operations (403 LIVE_STATUS_PROTECTED).

## Path parameters

- `id` string, required

## Request body

- object
  - `status` 'queued' | 'in_production' | 'shipped' | 'delivered' | 'cancelled': Test gifts only, signed-in people only: the next fulfillment step.
  - `outcome` 'none' | 'replied' | 'meeting_booked' | 'meeting_held': Customer-reported result; never infer it from delivery.

## Response `200`

Success: `{"data": Send}`.

- SendResponse: The success body: `{"data": Send}`.
  - `data` Send, required: One gift (send) with its immutable mode, status, outcome and timeline.
    - `id` string, required
    - `recipient` Recipient, required
      - `recipientId` string, required
      - `name` string, required
      - `email` string, required
      - `company` string, required
      - `sourceSystem` string
      - `externalId` string
      - `profileUrl` string
      - `importId` string
      - `importRowId` string
      - `addressMode` 'known' | 'confirm'
    - `campaignId` string, nullable, required
    - `status` 'awaiting_address' | 'queued' | 'in_production' | 'shipped' | 'delivered' | 'cancelled', required
    - `totalCents` integer, required
    - `testMode` boolean, required
    - `fundedBy` 'balance': balance: the gift was paid from the workspace balance when it was approved; it never needs a checkout.
    - `autoApproved` boolean: true when the playbook's auto-approve rule approved the gift rather than a person.

## Other responses

- `400`: Bad request: `VALIDATION_ERROR`, `INVALID_JSON`. Each example says when.
- `401`: Not authenticated: `AUTH_REQUIRED`. no credentials, or an OAuth token on a route that only takes workspace keys; the key is malformed, unknown or revoked.
- `403`: Forbidden: `HUMAN_APPROVAL_REQUIRED`, `LIVE_STATUS_PROTECTED`. Each example says when.
- `404`: Not found: `NOT_FOUND`. Each example says when.
- `409`: Conflict: `INVALID_REQUEST`. Each example says when.
- `413`: Request too large: `INVALID_REQUEST`. the body exceeds 1 MiB.
- `415`: Unsupported media type: `INVALID_REQUEST`. a write with a body that is not `Content-Type: application/json` (a key request with no body needs no Content-Type).
- `429`: Too many requests: `RATE_LIMIT`. more than 240 requests in the current minute for this workspace (REST and MCP share the limit); wait `retryAfterMs`.
- `default`: Any other refusal or failure, such as 403 CSRF (a cross-origin `Origin` header), 403 HTTPS_REQUIRED or 500 INTERNAL_ERROR, with what to do next.

---

[API](https://skmtc.dev/gtmswag/apis/gtm-swag-api.md) · [All operations](https://skmtc.dev/gtmswag/apis/gtm-swag-api/llms.txt) · [OpenAPI document](https://skmtc.dev/gtmswag/apis/gtm-swag-api/revisions/9ff86fa99afe?raw)