null value is different from an omitted property; preserve that distinction in your client.
Tasks
Task list, create, update, and detail responses share these fields:
Task details add
assigneeProfiles, createdByProfile, linkedRecords, linkedMeetings, section, activity, comments, and files. These collections can be empty. Use the returned detail collections for counts on this endpoint: its summary count fields default to zero. Activity contains the latest 30 entries; comments is the comment subset of those entries, not a complete comment history.
Task detail collections
linkedRecords contains compact chips with recordId, title, avatarUrl, objectTypeId, objectTypeName, and optional objectTypeSlug, objectTypeIcon, and objectTypeColor. These are different from search record previews.
section is null or an object with id, name, color, recordId, and recordTitle. Its section ID, name, and color can be null for an ungrouped record link.
Each file contains id, storageId, name, mimeType, size (bytes), displaySize (small, medium, or full), url (nullable), source (direct, comment, description, or activity), uploadedBy, uploadedByProfile, and optional activityId. File createdAt is a Unix timestamp in milliseconds, unlike the ISO dates on the task itself. Use the returned URL; a missing URL does not mean the file metadata is absent.
Profiles and activity
A profile containsauthUserId, name, email, and avatarUrl. A missing actor or creator profile is null; do not require a profile to render an activity.
An activity entry contains id, action, comment (string or null), actor (profile or null), and ISO createdAt. The entity activity endpoint returns the latest 50 entries without pagination. Other activity actions can have no comment text.
Record previews
Record previews are display-oriented results, not full raw record values:
Recent records and search include up to eight metadata fields. Field visibility respects plan restrictions: enriched and Pro interaction fields are omitted for non-Pro workspaces. To synchronize raw field values with a developer key, use the separate records API.
Schedule items
Upcoming meetings, the daily brief, and linked meeting details return schedule items. Native meetings and connected calendar events share:
Calendar events additionally contain
calendarName and externalUrl; externalUrl is null unless full details are visible. Render only the details returned for the current viewer. Calendar event IDs cannot be used as native linkedMeetingIds when writing a task.
Notifications
Notifications containid, type, category, entityType, entityId, title, body, isRead, readAt, createdAt, actor, and webUrl. readAt and actor can be null. webUrl can also be null when there is no supported target.
category is one of mentions, assigned, task_updates, record_activity, or other. Use isRead for unread styling. Marking unread clears readAt; dismissal is allowed only for a read notification.
The notification list returns { data, hasMore, nextCursor }. The daily brief’s notification array is limited and does not include pagination metadata.
Search results
Search returns{ query, data }. Each result has kind (task, record, or meeting), id, title, subtitle, badge, and webUrl, plus the corresponding task, record, or meeting payload. Switch on kind before reading the nested payload.
Results are ranked and limited, with no cursor or total count. Search task payloads contain only status, priority, and dueDate; use task details for the full task. Record payloads use the nested record metadata above, and meeting payloads use schedule items. Privacy filtering still applies. An empty result does not establish that the workspace has no matching private data.