---
title: "act: sign up"
description: "the company's name, and its domain where known, from a signed-in person who belongs to no tenant to the tenant, made on the trial plan with the person as its first member and owner, in one transaction with its events"
section: reference
address: /reference/act/sign_up
contract: 0476e35e6e275db5
---
# act: sign up
the company's name, and its domain where known, from a signed-in person who belongs to no tenant to the tenant, made on the trial plan with the person as its first member and owner, in one transaction with its events
[figure: The caller sends SignUpInput to /v1/act/sign_up. The platform returns a card whose body is Tenant.]
POST/v1/act/sign_up
Sign up. The call needs the user rung under a token with the act grant, and it is served by the platform.
The route takes [SignUpInput](/concepts/signupinput) and returns a card whose body is [Tenant](/concepts/tenant).
## Request body
The request body is [SignUpInput](/concepts/signupinput).
| field | type | required | note |
|---|---|---|---|
| `company` | `text` | yes | the company's name as the person states it |
| `domain` | `text` | no | the company's website, which the map from a domain reads next |
## Response
The route returns a card whose body is [Tenant](/concepts/tenant). 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 user rung and a token with the act grant. The platform serves this route.
## Example
The example sends the smallest body that SignUpInput allows. The build validates it against the schema of SignUpInput.
Example
```sh
curl -X POST https://api.scaleintelligence.co/v1/act/sign_up \
-H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/" \
-H "content-type: application/json" \
-d '{ "company": "…" }'
```
```typescript
import { client } from "@scale/sdk";
const answer = await client.act.sign_up({
"company": "…"
});
// answer.body is a Tenant. answer.foot holds the basis, the scope and the time.
```
```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/act/sign_up",
headers={"Scale-Key": KEY, "Scale-Scope": "tenant/"},
json={
"company": "…"
}).json()
```
```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/act/sign_up")
.header("Scale-Key", key).header("Scale-Scope", "tenant/")
.json(&SignUpInput { /* the fields of the page */ }).send().await?.json().await?;
```