ListFeeds parity mapping

Supported in:

This guide details the request and response mapping specifications and property parity analysis for migrating from the legacy Backstory Feed Management API (ListFeeds) to the modern Chronicle API (ListFeeds).

Protocol and mapping overview

Feature Legacy API (ListFeeds) Modern Chronicle API (ListFeeds)
HTTP method GET GET
Permissions Partner token or legacy API keys chronicle.googleapis.com/feeds.list

Request payload field-by-field parity

The modern Chronicle API ListFeedsRequest requires parent scoping.

Legacy field (ListFeedsRequest) Modern field (ListFeedsRequest) Field type Parity and migration notes
— parent (in HTTP path) string Google Cloud scoping context: Scopes the list target under parent projects using the standard resource name path in the URL. Pattern: projects/{project}/locations/{location}/instances/{instance_uuid}.
page_size page_size int32 Parity mapped: Pagination page size limits. Rename to pageSize in JSON payloads.
page_token page_token string Parity mapped: Paging resumption token. Rename to pageToken in JSON payloads.

Response payload field-by-field parity

Both the legacy Backstory Feed Management API (ListFeeds) and the modern Chronicle API (ListFeeds) return pagination results with matching nested models.

Legacy field (ListFeedsResponse message) Modern field (ListFeedsResponse message) Field type Parity and migration notes
feeds feeds repeated Feed Parity mapped: Array list of feeds (with nested field translations evaluated under CreateFeed or GetFeed). Rename to feeds in JSON.
next_page_token next_page_token string Parity mapped: Next page resumption token. Rename to nextPageToken in JSON.

Key differences between the Backstory and Chronicle APIs

  • Google Cloud project scoping integration:
    • Scoped natively under parent project instance folder bindings.
  • Explicit paging token behavior:
    • While the legacy backstory endpoint defined next_page_token and request pagers, pagination was not fully implemented or enforced consistently across all backstory feed systems. The Chronicle API provides standard Google Cloud paging checkpoint logic.