---
title: "read: proxy"
description: "the proxy and its version, the two dates, and a place to its members as a population, with the raw count, the estimate corrected by the recall and the undercount's interval, its calibration by segment, its coverage by channel, and its co-membership with other proxies; for an aggregate-only proxy the counts alone…"
section: reference
address: /reference/read/proxy
contract: 0476e35e6e275db5
---
# read: proxy
the proxy and its version, the two dates, and a place to its members as a population, with the raw count, the estimate corrected by the recall and the undercount's interval, its calibration by segment, its coverage by channel, and its co-membership with other proxies; for an aggregate-only proxy the counts alone…
[figure: The caller sends ProxyReadInput to /v1/read/proxy. The platform returns a card whose body is ProxyReading.]
POST/v1/read/proxy
Read a proxy. 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 [ProxyReadInput](/concepts/proxyreadinput) and returns a card whose body is [ProxyReading](/concepts/proxyreading).
## Request body
The request body is [ProxyReadInput](/concepts/proxyreadinput).
| field | type | required | note |
|---|---|---|---|
| `proxy` | `id` | yes | |
| `window` | [Window](/concepts/window) | no | |
## Response
The route returns a card whose body is [ProxyReading](/concepts/proxyreading). 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 ProxyReadInput allows. The build validates it against the schema of ProxyReadInput.
Example
```sh
curl -X POST https://api.scaleintelligence.co/v1/read/proxy \
-H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/" \
-H "content-type: application/json" \
-d '{ "proxy": "…" }'
```
```typescript
import { client } from "@scale/sdk";
const answer = await client.read.proxy({
"proxy": "…"
});
// answer.body is a ProxyReading. answer.foot holds the basis, the scope and the time.
```
```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/read/proxy",
headers={"Scale-Key": KEY, "Scale-Scope": "tenant/"},
json={
"proxy": "…"
}).json()
```
```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/read/proxy")
.header("Scale-Key", key).header("Scale-Scope", "tenant/")
.json(&ProxyReadInput { /* the fields of the page */ }).send().await?.json().await?;
```