---
title: "ask: groups"
description: "a scope, the two dates, and the resolution of the cut to the cluster response cards: each group with the share each layer of likeness contributed, its top communities, words and domains, its size and trend by month, and the proxies that placed its members"
section: reference
address: /reference/ask/groups
contract: 0476e35e6e275db5
---
# ask: groups
a scope, the two dates, and the resolution of the cut to the cluster response cards: each group with the share each layer of likeness contributed, its top communities, words and domains, its size and trend by month, and the proxies that placed its members
[figure: The caller sends GroupsInput to /v1/ask/groups. The platform returns a card whose body is [ClusterCard].]
POST/v1/ask/groups
Read the groups. The call needs the strategy rung under a token with the ask grant, and it is served by either, by the size bound.
The route takes [GroupsInput](/concepts/groupsinput) and returns a card whose body is [ClusterCard](/concepts/clustercard).
## Request body
The request body is [GroupsInput](/concepts/groupsinput).
| field | type | required | note |
|---|---|---|---|
| `scope` | [Predicate](/concepts/predicate) | yes | |
| `resolution` | `share` | yes | |
## Response
The route returns a card whose body is [ClusterCard](/concepts/clustercard). 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 ask grant. The platform or the desktop app serves this route.
## Example
The example sends the smallest body that GroupsInput allows. The build validates it against the schema of GroupsInput.
Example
```sh
curl -X POST https://api.scaleintelligence.co/v1/ask/groups \
-H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/" \
-H "content-type: application/json" \
-d '{ "scope": { "tree": { "form": "group" }, "population": "…", "tree_hash": "…", "register_hash": "…", "compiler_version": "…", "comparator_versions": {} }, "resolution": 0 }'
```
```typescript
import { client } from "@scale/sdk";
const answer = await client.ask.groups({
"scope": {
"tree": {
"form": "group"
},
"population": "…",
"tree_hash": "…",
"register_hash": "…",
"compiler_version": "…",
"comparator_versions": {}
},
"resolution": 0
});
// answer.body is a [ClusterCard]. answer.foot holds the basis, the scope and the time.
```
```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/ask/groups",
headers={"Scale-Key": KEY, "Scale-Scope": "tenant/"},
json={
"scope": {
"tree": {
"form": "group"
},
"population": "…",
"tree_hash": "…",
"register_hash": "…",
"compiler_version": "…",
"comparator_versions": {}
},
"resolution": 0
}).json()
```
```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/ask/groups")
.header("Scale-Key", key).header("Scale-Scope", "tenant/")
.json(&GroupsInput { /* the fields of the page */ }).send().await?.json().await?;
```