This page documents the canonical HTTP contract for this endpoint.
When to use this endpoint
Use it after /api/leads/query when you know which lead IDs and which research table you care about.
This keeps the main lead query fast and makes research hydration explicit.
Body parameters
lead_idsrequiredarray<string>
Lead IDs whose rows should be resolved; may be empty.
source_table_idrequiredstring
Research table ID; must be present as a string.
field_ids· optionalarray<string>
Optional column ID subset; null omits the restriction.
| Name | Type | Description |
|---|---|---|
| lead_idsrequired | array<string> | Lead IDs whose rows should be resolved; may be empty. |
| source_table_idrequired | string | Research table ID; must be present as a string. |
| field_ids | array<string> | Optional column ID subset; null omits the restriction. |
Errors
| Status | Meaning |
|---|---|
| 400 | Request body does not validate. |
| 401 | Invalid API key or missing auth. |
| 403 | Missing leads:read scope. |
