DeleteFeed 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 (DeleteFeed) to the modern Chronicle API (DeleteFeed).

Protocol and mapping overview

Feature Legacy API (DeleteFeed) Modern Chronicle API (DeleteFeed)
HTTP method DELETE DELETE
Permissions Partner token or legacy API keys chronicle.googleapis.com/feeds.delete

Request payload field-by-field parity

The modern Chronicle API DeleteFeedRequest targets resources using Google Cloud resource name paths and adds explicit control for purge queues.

Legacy field (DeleteFeedRequest) Modern field (DeleteFeedRequest) Field type Parity and migration notes
name name (in HTTP path) string Google Cloud scoping context: The legacy request used path format feeds/<id>. The modern API routes this using the standard Google Cloud resource tree structure: projects/{project}/locations/{region}/instances/{instance}/feeds/{id}.
— delete_backlog bool New field: If set to true, explicitly purges uningested backlog items in the out-of-band retry queue when deleting the feed. Rename to deleteBacklog in JSON.

Response payload field-by-field parity

Both the legacy Backstory Feed Management API (DeleteFeed) and the modern Chronicle API (DeleteFeed) return an empty response message upon successful execution.

Legacy field Modern field Field type Parity and migration notes
google.protobuf.Empty google.protobuf.Empty Empty Parity mapped: Successful requests return HTTP 200 OK (mapping to an empty response object {}).

Key differences between the Backstory and Chronicle APIs

  • Google Cloud project scoping integration:
    • Scoped natively under parent project instance folder bindings.
  • Resource path renaming:
    • Legacy path formats feeds/<id> are migrated to standard Google Cloud path parameters projects/*/locations/*/instances/*/feeds/<id>.
  • Backlog cleanup control:
    • Introduces a boolean flag delete_backlog allowing administrators to explicitly drop pending retry queues when terminating feed definitions.