# Take a lead over

> Mark that someone on your team is handling a company. Revnu stops contacting it and cancels its queued emails, without marking it declined.

Canonical: https://revnu.com/docs/lead-take-over
Last updated: 2026-10-30

```bash
curl -X POST -H "Authorization: Bearer $REVNU_API_TOKEN" \
  -H "content-type: application/json" \
  -d '{"stage":"meeting_booked","note":"Dana is running the demo on Tuesday."}' \
  https://revnu.com/api/v1/leads/sn7…/handling
```

## Body

| Field | Meaning |
|---|---|
| `stage` | Required. How far your team got: `contacted`, `meeting_booked`, `customer` or `not_a_fit`. `meeting_booked`, `customer` and `not_a_fit` also move the deal to meeting, won or lost, never backwards. |
| `note` | Optional, up to 500 characters: what the team is doing with them. Omit it to keep the last note. |

Any other field is a `400`. Call again to change the stage.

## Response

`200 { "domain", "stage", "cancelledEmails" }`. `cancelledEmails` counts the queued emails to that company that were cancelled. `404` for an unknown or another account's lead.

## Frequently asked questions

### How do I hand it back?

[`DELETE /leads/{id}/handling`](https://revnu.com/docs/lead-hand-back.md). Emails cancelled here are not re-queued.

### Is this the same as the block list?

No. A taken-over lead stays live in Leads and your agent still reads it; it just won't contact it. To refuse a company for good, use the [block list](https://revnu.com/docs/blocklist-add.md).

### Which scope does this need?

`leads:write`. A token without it gets `403` with `requiredScope` in the body.