Field selection
Choose returned fields and control relationship expansion
Use select, populate, and depth to request the response shape your integration needs.
Select top-level fields
Set requested fields to true under select:
curl -s -G \
-H "Authorization: users API-Key YOUR_API_KEY" \
--data-urlencode 'select[id]=true' \
--data-urlencode 'select[title]=true' \
--data-urlencode 'select[slug]=true' \
--data-urlencode 'select[startDate]=true' \
"https://api.basker.app/partners/2026-02/remarkable-theatre/events"Explicitly select id, timestamps, and any other fields you depend on. Do not assume the API adds them to an inclusive selection automatically.
Nested selections use bracket notation:
?select[id]=true&select[title]=true&select[tessitura][performanceId]=trueSelect fields from relationships
Key populate by the related collection slug. Include the relationship in select. Then choose fields from the related record:
curl -s -G \
-H "Authorization: users API-Key YOUR_API_KEY" \
--data-urlencode 'select[id]=true' \
--data-urlencode 'select[title]=true' \
--data-urlencode 'select[venue]=true' \
--data-urlencode 'populate[venues][id]=true' \
--data-urlencode 'populate[venues][title]=true' \
"https://api.basker.app/partners/2026-02/remarkable-theatre/events"Control relationship depth
depth controls how many relationship levels the API expands:
| Depth | Behavior |
|---|---|
0 | Relationship fields return IDs |
1 | Direct relationships can return records |
2 | The API can also expand relationships inside those records |
Use depth=0 when IDs are sufficient. Higher depths can make responses substantially larger.
Version-specific defaults
API version 2026-02 applies compact default select and populate shapes to many resources, including content, event, media, form, and custom-object resources. If you supply select or populate, it replaces that part of the resource default. It does not merge extra fields into the default.
API version 2025-07 retains the legacy behavior. It does not apply the current resource defaults. When a stable response shape matters, pin a version and request fields explicitly.
If a field does not appear, check whether you selected it. If a relationship is an ID rather than an object, check both depth and the relevant populate entry.