---
title: "read: attributes"
description: "a population and, where wanted, a window to the attributes its units carry, each with its plain name, the units that carry it, the value type read and up to three examples, most carried first, with the units read and in, and the partial answer when the budget ran out"
section: reference
address: /reference/read/attributes
contract: 0476e35e6e275db5
---
# read: attributes
a population and, where wanted, a window to the attributes its units carry, each with its plain name, the units that carry it, the value type read and up to three examples, most carried first, with the units read and in, and the partial answer when the budget ran out
[figure: The caller sends AttributesInput to /v1/read/attributes. The platform returns a card whose body is PopulationAttributes.]
POST/v1/read/attributes
The attributes of a population. The call needs the strategy rung under a token with the read grant, and it is served by the platform.
The route takes [AttributesInput](/concepts/attributesinput) and returns a card whose body is [PopulationAttributes](/concepts/populationattributes).
## Request body
The request body is [AttributesInput](/concepts/attributesinput).
| field | type | required | note |
|---|---|---|---|
| `population` | [Population](/concepts/population) | yes | |
| `window` | [Window](/concepts/window) | no | the units read; the whole record when absent |
## Response
The route returns a card whose body is [PopulationAttributes](/concepts/populationattributes). 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 strategy rung and a token with the read grant. The platform serves this route.
## Example
The example sends the smallest body that AttributesInput allows. The build validates it against the schema of AttributesInput.
Example
```sh
curl -X POST https://api.scaleintelligence.co/v1/read/attributes \
-H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/" \
-H "content-type: application/json" \
-d '{ "population": "…" }'
```
```typescript
import { client } from "@scale/sdk";
const answer = await client.read.attributes({
"population": "…"
});
// answer.body is a PopulationAttributes. answer.foot holds the basis, the scope and the time.
```
```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/read/attributes",
headers={"Scale-Key": KEY, "Scale-Scope": "tenant/"},
json={
"population": "…"
}).json()
```
```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/read/attributes")
.header("Scale-Key", key).header("Scale-Scope", "tenant/")
.json(&AttributesInput { /* the fields of the page */ }).send().await?.json().await?;
```