---
title: "read: basket"
description: "the basket, and one subject, a set of subjects, a scope predicate or a cut into groups, with the window to the basket reading as a fact: memberships with their scale of association and likelihood for one subject; population readings and co-membership for a set; proxy against group with lift and control for groups"
section: reference
address: /reference/read/basket
contract: 0476e35e6e275db5
---
# read: basket
the basket, and one subject, a set of subjects, a scope predicate or a cut into groups, with the window to the basket reading as a fact: memberships with their scale of association and likelihood for one subject; population readings and co-membership for a set; proxy against group with lift and control for groups
[figure: The caller sends BasketReadInput to /v1/read/basket. The platform returns a card whose body is BasketReading.]
POST/v1/read/basket
Read a basket. The call needs the strategy rung under a token with the read grant, and it is served by either, by the size bound.
The route takes [BasketReadInput](/concepts/basketreadinput) and returns a card whose body is [BasketReading](/concepts/basketreading).
## Request body
The request body is [BasketReadInput](/concepts/basketreadinput).
| field | type | required | note |
|---|---|---|---|
| `basket` | `id` | yes | |
| `subject` | `id` | no | one subject |
| `subjects` | `[id]` | no | a set, under the size bound |
| `scope` | [Predicate](/concepts/predicate) | no | a population by predicate |
| `resolution` | `share` | no | a cut into groups at this resolution |
| `window` | [Window](/concepts/window) | no | |
## Response
The route returns a card whose body is [BasketReading](/concepts/basketreading). 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 or the desktop app serves this route.
## Example
The example sends the smallest body that BasketReadInput allows. The build validates it against the schema of BasketReadInput.
Example
```sh
curl -X POST https://api.scaleintelligence.co/v1/read/basket \
-H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/" \
-H "content-type: application/json" \
-d '{ "basket": "…" }'
```
```typescript
import { client } from "@scale/sdk";
const answer = await client.read.basket({
"basket": "…"
});
// answer.body is a BasketReading. answer.foot holds the basis, the scope and the time.
```
```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/read/basket",
headers={"Scale-Key": KEY, "Scale-Scope": "tenant/"},
json={
"basket": "…"
}).json()
```
```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/read/basket")
.header("Scale-Key", key).header("Scale-Scope", "tenant/")
.json(&BasketReadInput { /* the fields of the page */ }).send().await?.json().await?;
```