---
title: "act: routing"
description: "Writes, previews or arms a routing rule from a predicate and the people or the team it attaches to A write or an arm gives the rule."
section: reference
address: /reference/act/routing
contract: 0476e35e6e275db5
---
# act: routing
Writes, previews or arms a routing rule from a predicate and the people or the team it attaches to A write or an arm gives the rule.
[figure: The caller sends RoutingInput to /v1/act/routing. The platform returns a card whose body is RoutingAnswer.]
POST/v1/act/routing
Write, preview and arm a routing rule. The call needs the brand rung under a token with the act grant, and it is served by the platform.
The route takes [RoutingInput](/concepts/routinginput) and returns a card whose body is [RoutingAnswer](/concepts/routinganswer).
## Request body
The request body is [RoutingInput](/concepts/routinginput).
| field | type | required | note |
|---|---|---|---|
| `rule` | [RoutingRule](/concepts/routingrule) | yes | |
| `do` | `one of write \| preview \| arm` | yes | |
## Response
The route returns a card whose body is [RoutingAnswer](/concepts/routinganswer). 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/, then /brand/, then /strategy/ |
| `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 brand rung and a token with the act grant. The platform serves this route.
## Example
The example sends the smallest body that RoutingInput allows. The build validates it against the schema of RoutingInput.
Example
```sh
curl -X POST https://api.scaleintelligence.co/v1/act/routing \
-H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/" \
-H "content-type: application/json" \
-d '{ "rule": { "name": "…", "predicate": "…", "to": { "kind": "a user", "id": "…" }, "armed": false }, "do": "write" }'
```
```typescript
import { client } from "@scale/sdk";
const answer = await client.act.routing({
"rule": {
"name": "…",
"predicate": "…",
"to": {
"kind": "a user",
"id": "…"
},
"armed": false
},
"do": "write"
});
// answer.body is a RoutingAnswer. answer.foot holds the basis, the scope and the time.
```
```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/routing",
headers={"Scale-Key": KEY, "Scale-Scope": "tenant/"},
json={
"rule": {
"name": "…",
"predicate": "…",
"to": {
"kind": "a user",
"id": "…"
},
"armed": false
},
"do": "write"
}).json()
```
```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/routing")
.header("Scale-Key", key).header("Scale-Scope", "tenant/")
.json(&RoutingInput { /* the fields of the page */ }).send().await?.json().await?;
```