> For the complete documentation index, see [llms.txt](https://docs.moderncollections.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.moderncollections.io/webhooks/events/placement.status_changed.md).

# placement.status\_changed

The workhorse webhook. Fires when a placement's `status` field makes one of the surfaced transitions below. Most integrators key their entire integration off this event.

## When this fires

* A placement is recalled by the creditor (`* → recalled`) — fired from `POST /v1/placements/{id}/recall`.
* A placement is fully paid (`pending_payment → paid`) — fired when an out-of-band payment recorded via `POST /v1/placements/{id}/payment-received` clears the balance. A Stripe payment made through the debtor portal does **not** currently fire this webhook, even when it flips the placement to `paid`.

Other status transitions (e.g. `pending_enrichment → ready → in_outreach`) happen internally but currently do not emit this webhook. If you need visibility into those transitions, poll the placement detail endpoint or open a request with platform support.

## Payload

Two slightly different shapes are emitted depending on which transition fired. Both include `event`, `timestamp`, `placement_id`, `previous_status`, and `new_status`.

### Recalled (`* → recalled`)

```json
{
  "event": "placement.status_changed",
  "timestamp": "2026-05-12T14:32:00+00:00",
  "placement_id": "550e8400-e29b-41d4-a716-446655440000",
  "previous_status": "in_outreach",
  "new_status": "recalled"
}
```

### Paid in full (`pending_payment → paid`)

```json
{
  "event": "placement.status_changed",
  "timestamp": "2026-05-12T14:32:00+00:00",
  "placement_id": "550e8400-e29b-41d4-a716-446655440000",
  "previous_status": "pending_payment",
  "new_status": "paid",
  "recovered_amount": 7500.0,
  "fee_amount": 375.0
}
```

## Fields

| Field              | Type              | Notes                                                                  |
| ------------------ | ----------------- | ---------------------------------------------------------------------- |
| `event`            | string            | Always `"placement.status_changed"`.                                   |
| `timestamp`        | string (ISO-8601) | When the event was constructed.                                        |
| `placement_id`     | string (UUID)     | The placement whose status changed.                                    |
| `previous_status`  | string            | The status before the transition.                                      |
| `new_status`       | string            | The status after the transition.                                       |
| `recovered_amount` | number            | **Paid transition only.** Total recovered in the placement's currency. |
| `fee_amount`       | number            | **Paid transition only.** Our contingency fee for the placement.       |

## Status values seen in this event today

| `new_status` | When                                             |
| ------------ | ------------------------------------------------ |
| `recalled`   | Creditor pulled the placement; outreach stopped. |
| `paid`       | Funds arrived for the full balance.              |

## See also

* [`call.completed`](/webhooks/events/call.completed.md)
* [`payment.commitment_made`](/webhooks/events/payment.commitment_made.md)
* [POST /v1/placements](/rest-api/placements.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.moderncollections.io/webhooks/events/placement.status_changed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.