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

Protocol and mapping overview

Feature Legacy API (FetchFeedServiceAccount) Modern Chronicle API (FetchServiceAccountForCustomer)
HTTP method GET GET
Permissions Partner token or legacy API keys chronicle.googleapis.com/feedServiceAccounts.fetch

Request payload field-by-field parity

The modern Chronicle API FetchServiceAccountForCustomerRequest requires parent scoping instead of relying on implicit auth tokens.

Legacy field (FetchFeedServiceAccountRequest) Modern field (FetchServiceAccountForCustomerRequest) Field type Parity and migration notes
— (empty request) parent (in HTTP path) string Google Cloud scoping context: The legacy request took an empty body ({}) and derived customer bounds implicitly from auth token context. The modern API specifies parent resource paths explicitly: projects/{project}/locations/{region}/instances/{instance}.

Response payload field-by-field parity

The modern Chronicle API (FetchServiceAccountForCustomer) response wraps the service account in a standard Google Cloud resource format.

Legacy field (FetchFeedServiceAccountResponse message) Modern field (FeedServiceAccount message) Field type Parity and migration notes
service_account name string Parity mapped / restructured: Legacy returned the raw service account string. The modern API maps this into the standard canonical resource path under name: projects/{project}/locations/{location}/instances/{instance}/feedServiceAccounts/{service_account_email}.
subject_id subject_id string Parity mapped: Unique subject identifier for the service account. Rename to subjectId in JSON responses.

Key differences between the Backstory and Chronicle APIs

  • Google Cloud project scoping integration:
    • Scoped natively under parent project instance folder bindings rather than relying on implicit auth tokens.
  • Resource path formatting:
    • Raw service account strings are encapsulated inside standard Google Cloud canonical resource names (projects/.../feedServiceAccounts/<sa>).