Record field dictionary

Read what a returned field means before using it in another request. This dictionary explains short message keys, identifiers, source-specific rows, and nested evidence fields.

At a glance

What you're looking at

A row's id depends on the source and grain. A message, case, person, review, and Listening post use different identifier namespaces. Short output keys are not automatically valid filter names. MCP filters use the operation's structured input schema. Use Query syntax for filter formats and the MCP field reference for request fields.

Most fields are nullable or optional. Null means unknown or unavailable. An omitted field can mean the projection did not request it. Dynamic maps such as custom fields, rubric assessments, and platform metadata have no universal child-field list. Inspect their returned keys and organization definitions. Do not invent a value or treat null as zero.

Example: read message identifiers

This fictional row shows the different identifiers:

{
  "id": "TWITTER_message_42",
  "pmid": "1900000000000000042",
  "prid": "TWITTER_message_40",
  "tid": "TWITTER_thread_40",
  "uid": "900000000000000001",
  "usr": "example_customer",
  "src": "TWITTER",
  "ch": "example_channel",
  "rt": "COMMENT",
  "content": "Where can I check my refund?"
}

Keep id for Sift message reads. Keep pmid for platform identity. Keep prid to trace the parent. A reply operation needs the case's actionId. Do not substitute one of these message identifiers.

Short message keys

These keys occur on messages rows. Full names in this table describe their meaning. They are not extra keys guaranteed on the same row.

Choose the correct identifier

An identifier has meaning only within its resource and namespace. Preserve it exactly. Do not convert IDs to numbers.

Message content and dates

Message rows also carry the following fields. A field can be omitted or null when the source has no value.

Case result fields

query.search.actions rows describe cases. query.search.action_records rows describe records. action_contexts rows add conversation context. A projection can add fields. Missing values do not mean zero.

Optional case projections

Pass these names in project after checking sift.spec("query.search.actions"). They add stored fields. They do not make every field available on every case.

Author profile fields

author is nullable. Every child is nullable when the stored profile lacks that value. These are stored facts, not a live platform fetch.

Engagement fields

engagement is nullable. Each counter can be null. Null means unknown, not zero. Counters are stored snapshots.

What score means

Read score according to the operation and record type. It is not one cross-platform rating.

Use sift.spec("query.search.actions") to check the current projection contract. Do not infer a like count, reaction count, or engagement formula from score or the platform alone. If the task needs separate counters, request engagement and use its named fields. Null means unknown or unavailable. It does not mean zero.

Use postScore only where the operation supports that filter. Do not compare review ratings with vote counts.

People and identity fields

For users, read scope before joining rows. people deduplicates profiles. identities returns native identities. ids returns only id. Additional people fields depend on the selected view.

Reply review fields

reviews means reply-approval reviews. App Store and Google Play review content belongs to messages or actions. Review rows can contain additional source fields.

Internal note fields

comments returns teammate notes on a case. Use messages search for customer-visible platform content.

Lifecycle event fields

lifecycle_events records case activity. These events differ from the MCP Events webhook subscription.

Listening result fields

A Listening result is a deduplicated post. Preserve the separate capture time and publication time. Nested author and engagement fields use the dictionaries above.

Structured case context fields

With contextFormat: json, each row adds context. With text format, context is a string. Full depth adds the customer timeline.

Search envelope

These are result fields, not query inputs. An agent's first page, or a call with includeTotal, also returns total.

Moderation summary fields

moderationSummary can be absent or null. The selected evaluation's status must be complete before a decision is final. Read evaluationId, status, recommendation, humanDecision, and disposition separately. disposition uses the effective human or automated decision. ruleIds and ruleHits hold rule identifiers and evidence polarity. display.outcomeSentence gives a readable outcome. display.policyNames uses the current rule names, which can change. Source metadata includes sourceSystem, sourcePlatform, sourceAdId, advertiserName, campaignId, market, and placement. Use the API field reference for the complete moderation decision and evidence contract.

Tips

• Preserve the source, grain, scope, and row identifier beside evidence.
• Use a supplied link instead of building a Sift URL from a platform ID.
• Check stored update times before describing profile or engagement data as current.
• Keep reported feedback separate from an estimated score.
• Before a new follow-up call, inspect its exact input and output with sift.spec(id).
• For loose row schemas, make a permitted read with limit: 1 and inspect the actual keys.

Related