---
title: "read: audience map"
description: "a brand, two facets or a facet and a community, the window to the shared subjects, the share, the lift, the negative control that bounds it, and the size as bounds"
section: reference
address: /reference/read/audience_map
contract: 0476e35e6e275db5
---
# read: audience map
a brand, two facets or a facet and a community, the window to the shared subjects, the share, the lift, the negative control that bounds it, and the size as bounds
[figure: The caller sends AudienceMapInput to /v1/read/audience_map. The platform returns a card whose body is AudienceMapCell.]
POST/v1/read/audience_map
Read the audience map. The call needs the brand rung under a token with the read grant, and it is served by either, by the size bound.
The route takes [AudienceMapInput](/concepts/audiencemapinput) and returns a card whose body is [AudienceMapCell](/concepts/audiencemapcell).
## Request body
The request body is [AudienceMapInput](/concepts/audiencemapinput).
| field | type | required | note |
|---|---|---|---|
| `brand` | `id` | yes | |
| `first` | `id` | yes | |
| `second` | `id` | yes | |
| `window` | [Window](/concepts/window) | yes | |
| `adult` | `bool` | no | when true, the rooms marked adult count in the crossing; left out by default |
## Response
The route returns a card whose body is [AudienceMapCell](/concepts/audiencemapcell). 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 read grant. The platform or the desktop app serves this route.
## Example
The example sends the smallest body that AudienceMapInput allows. The build validates it against the schema of AudienceMapInput.
Example
```sh
curl -X POST https://api.scaleintelligence.co/v1/read/audience_map \
-H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/" \
-H "content-type: application/json" \
-d '{ "brand": "…", "first": "…", "second": "…", "window": { "from": "…", "to": "…" } }'
```
```typescript
import { client } from "@scale/sdk";
const answer = await client.read.audience_map({
"brand": "…",
"first": "…",
"second": "…",
"window": {
"from": "…",
"to": "…"
}
});
// answer.body is a AudienceMapCell. answer.foot holds the basis, the scope and the time.
```
```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/read/audience_map",
headers={"Scale-Key": KEY, "Scale-Scope": "tenant/"},
json={
"brand": "…",
"first": "…",
"second": "…",
"window": {
"from": "…",
"to": "…"
}
}).json()
```
```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/read/audience_map")
.header("Scale-Key", key).header("Scale-Scope", "tenant/")
.json(&AudienceMapInput { /* the fields of the page */ }).send().await?.json().await?;
```