---
title: "read: fit frame"
description: "Reads the frame of one fit search to The answer gives the markets ranked, the offering sculpted for each buyer profile, the tactics proposed to test the fit, the verdict for each market, and the set of options that compares them"
section: reference
address: /reference/read/fit_frame
contract: 0476e35e6e275db5
---
# read: fit frame
Reads the frame of one fit search to The answer gives the markets ranked, the offering sculpted for each buyer profile, the tactics proposed to test the fit, the verdict for each market, and the set of options that compares them
[figure: The caller sends FitFrameInput to /v1/read/fit_frame. The platform returns a card whose body is FitSearchFrame.]
POST/v1/read/fit_frame
Read a search's frame. 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 [FitFrameInput](/concepts/fitframeinput) and returns a card whose body is [FitSearchFrame](/concepts/fitsearchframe).
## Request body
The request body is [FitFrameInput](/concepts/fitframeinput).
| field | type | required | note |
|---|---|---|---|
| `search` | `id` | yes | |
## Response
The route returns a card whose body is [FitSearchFrame](/concepts/fitsearchframe). 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 FitFrameInput allows. The build validates it against the schema of FitFrameInput.
Example
```sh
curl -X POST https://api.scaleintelligence.co/v1/read/fit_frame \
-H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/" \
-H "content-type: application/json" \
-d '{ "search": "…" }'
```
```typescript
import { client } from "@scale/sdk";
const answer = await client.read.fit_frame({
"search": "…"
});
// answer.body is a FitSearchFrame. answer.foot holds the basis, the scope and the time.
```
```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/read/fit_frame",
headers={"Scale-Key": KEY, "Scale-Scope": "tenant/"},
json={
"search": "…"
}).json()
```
```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/read/fit_frame")
.header("Scale-Key", key).header("Scale-Scope", "tenant/")
.json(&FitFrameInput { /* the fields of the page */ }).send().await?.json().await?;
```