---
title: "act: assign"
description: "Assigns one lead to one user by hand, or hands it on to The answer gives the assignment, with the person who made it as its reason"
section: reference
address: /reference/act/assign
contract: 0476e35e6e275db5
---

# act: assign

Assigns one lead to one user by hand, or hands it on to The answer gives the assignment, with the person who made it as its reason

[figure: The caller sends AssignInput to /v1/act/assign. The platform returns a card whose body is LeadAssignment.]

<span class="op-method">POST</span><span class="op-path">/v1/act/assign</span>

Assign by hand. Hand on. The call needs the strategy rung under a token with the act grant, and it is served by the platform.

The route takes [AssignInput](/concepts/assigninput) and returns a card whose body is [LeadAssignment](/concepts/leadassignment).



## Request body
The request body is [AssignInput](/concepts/assigninput).



| field | type | required | note |
|---|---|---|---|
| `lead` | `id` | yes |  |
| `user` | `id` | yes |  |
| `reason` | `text` | yes |  |



## Response
The route returns a card whose body is [LeadAssignment](/concepts/leadassignment). Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true.

## Headers


| header | required | meaning |
|---|---|---|
| `Scale-Scope` | yes | the scope the call runs in: tenant/<id>, then /brand/<id>, then /strategy/<id> |
| `Scale-As-True-On` | no | the date the facts must have been true on; defaults to now |
| `Scale-As-Known-On` | no | the date the facts must have been known on; defaults to now |
| `Scale-Key` | no | for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing |



A caller needs the strategy rung and a token with the act grant. The platform serves this route.

## Example
The example sends the smallest body that AssignInput allows. The build validates it against the schema of AssignInput.

<details class="wire"><summary>Example</summary>





```sh
curl -X POST https://api.scaleintelligence.co/v1/act/assign \
  -H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/<id>" \
  -H "content-type: application/json" \
  -d '{ "lead": "…", "user": "…", "reason": "…" }'
```




```typescript
import { client } from "@scale/sdk";
const answer = await client.act.assign({
    "lead": "…",
    "user": "…",
    "reason": "…"
  });
// answer.body is a LeadAssignment. answer.foot holds the basis, the scope and the time.
```




```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/assign",
    headers={"Scale-Key": KEY, "Scale-Scope": "tenant/<id>"},
    json={
      "lead": "…",
      "user": "…",
      "reason": "…"
    }).json()
```




```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/assign")
    .header("Scale-Key", key).header("Scale-Scope", "tenant/<id>")
    .json(&AssignInput { /* the fields of the page */ }).send().await?.json().await?;
```




</details>

## MCP tool
The MCP tool `si.act.assign` takes the same input and returns the same card. The tool changes data and needs a grant. An MCP host that renders cards draws this card from `ui://scale-intelligence/cards/LeadAssignment`. The [tool's page](/reference/tools/si-act-assign) describes it.
