---
title: "updateFeedItem"
method: PUT
path: "/feed-items/{feed_item}"
tags: ["Feed Item"]
deprecated: true
---

# updateFeedItem

`PUT /feed-items/{feed_item}`

> **Deprecated.**

Update a Feed Item

## Path parameters

- `feed_item` integer, required

## Request body

- object
  - `comment` string — Comment for the Feed Item

## Response `200`

Success

- union
  - FeedItemAssociation
    - `id` integer — Primary identifier of record
    - `agent_id` integer, nullable — Primary identifier of the Agent that performed interaction associated with Feed Item
    - `agent_type` 'member' | 'business', nullable — Type of Agent that performed interaction associated with Feed Item
    - `agent_name` string, nullable — Name of Agent that performed interaction associated with Feed Item. When the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture), Member-morph agents return the supporter-derived display name; for creation-type items on fundraising_page / fundraising_team feedables with no Supporter, the page / team title is the fallback (only when it does not match the author member's snapshotted name); otherwise null. Business agents are unaffected. Prefer the new `author_display_name` field for new consumers — `agent_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
    - `member_name` string, nullable — Snapshotted name of the Member associated with the Feed Item (legacy alias preceding the polymorphic `agent` relation). When the owning Organization has Contact-First Architecture enabled, this is replaced with the supporter-derived display name; for creation-type items on fundraising_page / fundraising_team feedables with no Supporter, the page / team title is the fallback (only when it does not match the author member's snapshotted name); for Business agents and otherwise null. Prefer the new `author_display_name` field for new consumers — `member_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
    - `feedable_id` integer — Primary identifier of Fundraising Entity associated with Feed Item’s described interaction
    - `feedable_type` 'fundraising_team' — Type of the Fundraising Entity associated with Feed Item’s described interaction
    - `feedable_value` string, nullable — Name or title of the Item. Under Contact-First Architecture (npo_apiv2_ff_contact_first_architecture), this is null when `feedable_type` is `fundraising_page` or `fundraising_team` (any row type) — the snapshotted page / team title would otherwise re-leak member-seeded names from unguarded write paths (`CompleteRegistrations`, `CreateFundraisingPageForLead`, and the registration-recovery commands).
    - `linkable_id` integer, nullable — Primary identifier of Entity whose creation, update, or association is described by Feed Item
    - `linkable_type` 'fundraising_page', nullable — Type of the Entity whose creation, update, or association is described by Feed Item
    - `linkable_value` string, nullable — Name or title of the Entity whose creation, update, or association is described by Feed Item. Under Contact-First Architecture (npo_apiv2_ff_contact_first_architecture), this is null when `linkable_type` is `fundraising_page` or `fundraising_team` (any row type — the snapshotted page / team title would otherwise re-leak member-seeded names), and for TYPE_ASSOCIATION items where `linkable_type` is a Member morph (the persisted column would otherwise re-leak the member's full name).
    - `linkable_effective_at` string, date-time — Date/time when Linkable is effective
    - `type` 'comment' | 'onboarding' | 'creation' | 'update' | 'association' — Type of the Item
    - `comment` string, nullable — Comment
    - `comments_count` integer, nullable — Amount of Comments that the Feed Item has
    - `likes_count` integer, nullable — Amount of Likes that the Feed has
    - `created_at` string, date-time — Date/time when object was created
    - `updated_at` string, date-time — Date/time when object was updated
    - `visibility` 'public' | 'admin' — Visibility status of the Item
    - `latest_comments` Comment[] — Array of latest Comments made in response to Item (limit 2 items)
      - `body` string — The content of the Comment
      - `commentable_id` integer — Primary identifier of associated Commentable Entity
      - `commentable_type` 'feed_item' | 'update' | 'story' — Type of associated Commentable Entity
      - `commenter_name` string — The full name of the creator of the Comment. CFA semantics apply only to comments embedded in a parent FeedItem's `latest_comments` (the FeedItem-level `getLatestCommentsAttribute` override drives the privacy pass). For comments returned by the standalone Post / Story / Update comment endpoints, the legacy shape is preserved regardless of the org's Contact-First Architecture flag — those surfaces are tracked for migration under PRO-4055. When CFA applies (FeedItem-embedded path) and the flag is on (npo_apiv2_ff_contact_first_architecture), this returns the supporter-derived display name (or empty string when no Supporter is found) instead of the member's name. Prefer the new `author_display_name` field for new consumers — `commenter_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
      - `author_display_name` string, nullable — Supporter-derived display name for the comment author. Populated only on FeedItem-embedded comments (`latest_comments`) — the standalone Post / Story / Update comment endpoints do not include this property; that gap is tracked for migration under PRO-4055. On the FeedItem-embedded path: populated when the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture); also populated (often null) on the fail-closed path when the owning Organization cannot be resolved for the parent FeedItem on a supporter-bearing feedable type. Null when no Supporter record matches the commenter for that org. New consumers should prefer this field over `commenter_name`.
      - `created_at` string, date-time — Date/time of initial record creation
      - `id` integer — Primary identifier of record
      - `likes_count` integer — Amount of likes a Comment has received
      - `member_id` integer — The ID of the Member that created of the Comment
      - `updated_at` string, date-time — Date/time of last record update
    - `author_display_name` string, nullable — Supporter-derived display name for the item author. Populated when the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture); also populated on the fail-closed path when the owning Organization cannot be resolved on a supporter-bearing feedable type (soft-deleted feedable, etc.) — Business-agent items surface the business display name and Member-agent items surface null. Resolves to the supporter's first + last name for member-authored items, the business display name for Business-agent items, or null when no Supporter record matches and no safe fallback is available. New consumers should prefer this field over `member_name` / `agent_name`.
  - FeedItemComment
    - `id` integer — Primary identifier of record
    - `agent_id` integer, nullable — Primary identifier of the Agent that performed interaction associated with Feed Item
    - `agent_type` 'member' | 'business', nullable — Type of Agent that performed interaction associated with Feed Item
    - `agent_name` string, nullable — Name of Agent that performed interaction associated with Feed Item. When the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture), Member-morph agents return the supporter-derived display name; for creation-type items on fundraising_page / fundraising_team feedables with no Supporter, the page / team title is the fallback (only when it does not match the author member's snapshotted name); otherwise null. Business agents are unaffected. Prefer the new `author_display_name` field for new consumers — `agent_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
    - `member_name` string, nullable — Snapshotted name of the Member associated with the Feed Item (legacy alias preceding the polymorphic `agent` relation). When the owning Organization has Contact-First Architecture enabled, this is replaced with the supporter-derived display name; for creation-type items on fundraising_page / fundraising_team feedables with no Supporter, the page / team title is the fallback (only when it does not match the author member's snapshotted name); for Business agents and otherwise null. Prefer the new `author_display_name` field for new consumers — `member_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
    - `feedable_id` integer — Primary identifier of Fundraising Entity associated with Feed Item’s described interaction
    - `feedable_type` string — Type of the Fundraising Entity associated with Feed Item’s described interaction
    - `feedable_value` string, nullable — Name or title of the Item. Under Contact-First Architecture (npo_apiv2_ff_contact_first_architecture), this is null when `feedable_type` is `fundraising_page` or `fundraising_team` (any row type) — the snapshotted page / team title would otherwise re-leak member-seeded names from unguarded write paths (`CompleteRegistrations`, `CreateFundraisingPageForLead`, and the registration-recovery commands).
    - `linkable_id` integer, nullable — Primary identifier of Entity whose creation, update, or association is described by Feed Item
    - `linkable_type` string, nullable — Type of the Entity whose creation, update, or association is described by Feed Item
    - `linkable_value` string, nullable — Name or title of the Entity whose creation, update, or association is described by Feed Item. Under Contact-First Architecture (npo_apiv2_ff_contact_first_architecture), this is null when `linkable_type` is `fundraising_page` or `fundraising_team` (any row type — the snapshotted page / team title would otherwise re-leak member-seeded names), and for TYPE_ASSOCIATION items where `linkable_type` is a Member morph (the persisted column would otherwise re-leak the member's full name).
    - `linkable_effective_at` string, date-time — Date/time when Linkable is effective
    - `type` 'comment' | 'onboarding' | 'creation' | 'update' | 'association' — Type of the Item
    - `comment` string — Comment
    - `comments_count` integer, nullable — Amount of Comments that the Feed Item has
    - `likes_count` integer, nullable — Amount of Likes that the Feed has
    - `created_at` string, date-time — Date/time when object was created
    - `updated_at` string, date-time — Date/time when object was updated
    - `visibility` 'public' | 'admin' — Visibility status of the Item
    - `latest_comments` Comment[] — Array of latest Comments made in response to Item (limit 2 items)
      - `body` string — The content of the Comment
      - `commentable_id` integer — Primary identifier of associated Commentable Entity
      - `commentable_type` 'feed_item' | 'update' | 'story' — Type of associated Commentable Entity
      - `commenter_name` string — The full name of the creator of the Comment. CFA semantics apply only to comments embedded in a parent FeedItem's `latest_comments` (the FeedItem-level `getLatestCommentsAttribute` override drives the privacy pass). For comments returned by the standalone Post / Story / Update comment endpoints, the legacy shape is preserved regardless of the org's Contact-First Architecture flag — those surfaces are tracked for migration under PRO-4055. When CFA applies (FeedItem-embedded path) and the flag is on (npo_apiv2_ff_contact_first_architecture), this returns the supporter-derived display name (or empty string when no Supporter is found) instead of the member's name. Prefer the new `author_display_name` field for new consumers — `commenter_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
      - `author_display_name` string, nullable — Supporter-derived display name for the comment author. Populated only on FeedItem-embedded comments (`latest_comments`) — the standalone Post / Story / Update comment endpoints do not include this property; that gap is tracked for migration under PRO-4055. On the FeedItem-embedded path: populated when the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture); also populated (often null) on the fail-closed path when the owning Organization cannot be resolved for the parent FeedItem on a supporter-bearing feedable type. Null when no Supporter record matches the commenter for that org. New consumers should prefer this field over `commenter_name`.
      - `created_at` string, date-time — Date/time of initial record creation
      - `id` integer — Primary identifier of record
      - `likes_count` integer — Amount of likes a Comment has received
      - `member_id` integer — The ID of the Member that created of the Comment
      - `updated_at` string, date-time — Date/time of last record update
    - `author_display_name` string, nullable — Supporter-derived display name for the item author. Populated when the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture); also populated on the fail-closed path when the owning Organization cannot be resolved on a supporter-bearing feedable type (soft-deleted feedable, etc.) — Business-agent items surface the business display name and Member-agent items surface null. Resolves to the supporter's first + last name for member-authored items, the business display name for Business-agent items, or null when no Supporter record matches and no safe fallback is available. New consumers should prefer this field over `member_name` / `agent_name`.
  - FeedItemCreation
    - `id` integer — Primary identifier of record
    - `agent_id` integer, nullable — Primary identifier of the Agent that performed interaction associated with Feed Item
    - `agent_type` 'member' | 'business', nullable — Type of Agent that performed interaction associated with Feed Item
    - `agent_name` string, nullable — Name of Agent that performed interaction associated with Feed Item. When the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture), Member-morph agents return the supporter-derived display name; for creation-type items on fundraising_page / fundraising_team feedables with no Supporter, the page / team title is the fallback (only when it does not match the author member's snapshotted name); otherwise null. Business agents are unaffected. Prefer the new `author_display_name` field for new consumers — `agent_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
    - `member_name` string, nullable — Snapshotted name of the Member associated with the Feed Item (legacy alias preceding the polymorphic `agent` relation). When the owning Organization has Contact-First Architecture enabled, this is replaced with the supporter-derived display name; for creation-type items on fundraising_page / fundraising_team feedables with no Supporter, the page / team title is the fallback (only when it does not match the author member's snapshotted name); for Business agents and otherwise null. Prefer the new `author_display_name` field for new consumers — `member_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
    - `feedable_id` integer — Primary identifier of Fundraising Entity associated with Feed Item’s described interaction
    - `feedable_type` string — Type of the Fundraising Entity associated with Feed Item’s described interaction, same as linkable_type
    - `feedable_value` string, nullable — Name or title of the Item. Under Contact-First Architecture (npo_apiv2_ff_contact_first_architecture), this is null when `feedable_type` is `fundraising_page` or `fundraising_team` (any row type) — the snapshotted page / team title would otherwise re-leak member-seeded names from unguarded write paths (`CompleteRegistrations`, `CreateFundraisingPageForLead`, and the registration-recovery commands).
    - `linkable_id` integer, nullable — Primary identifier of Entity whose creation, update, or association is described by Feed Item
    - `linkable_type` string, nullable — Type of the Entity whose creation, update, or association is described by Feed Item same as feedable_type
    - `linkable_value` string, nullable — Name or title of the Entity whose creation, update, or association is described by Feed Item. Under Contact-First Architecture (npo_apiv2_ff_contact_first_architecture), this is null when `linkable_type` is `fundraising_page` or `fundraising_team` (any row type — the snapshotted page / team title would otherwise re-leak member-seeded names), and for TYPE_ASSOCIATION items where `linkable_type` is a Member morph (the persisted column would otherwise re-leak the member's full name).
    - `linkable_effective_at` string, date-time — Date/time when Linkable is effective
    - `type` 'comment' | 'onboarding' | 'creation' | 'update' | 'association' — Type of the Item
    - `comment` 'null', nullable — Comment
    - `comments_count` integer, nullable — Amount of Comments that the Feed Item has
    - `likes_count` integer, nullable — Amount of Likes that the Feed has
    - `created_at` string, date-time — Date/time when object was created
    - `updated_at` string, date-time — Date/time when object was updated
    - `visibility` 'public' | 'admin' — Visibility status of the Item
    - `latest_comments` Comment[] — Array of latest Comments made in response to Item (limit 2 items)
      - `body` string — The content of the Comment
      - `commentable_id` integer — Primary identifier of associated Commentable Entity
      - `commentable_type` 'feed_item' | 'update' | 'story' — Type of associated Commentable Entity
      - `commenter_name` string — The full name of the creator of the Comment. CFA semantics apply only to comments embedded in a parent FeedItem's `latest_comments` (the FeedItem-level `getLatestCommentsAttribute` override drives the privacy pass). For comments returned by the standalone Post / Story / Update comment endpoints, the legacy shape is preserved regardless of the org's Contact-First Architecture flag — those surfaces are tracked for migration under PRO-4055. When CFA applies (FeedItem-embedded path) and the flag is on (npo_apiv2_ff_contact_first_architecture), this returns the supporter-derived display name (or empty string when no Supporter is found) instead of the member's name. Prefer the new `author_display_name` field for new consumers — `commenter_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
      - `author_display_name` string, nullable — Supporter-derived display name for the comment author. Populated only on FeedItem-embedded comments (`latest_comments`) — the standalone Post / Story / Update comment endpoints do not include this property; that gap is tracked for migration under PRO-4055. On the FeedItem-embedded path: populated when the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture); also populated (often null) on the fail-closed path when the owning Organization cannot be resolved for the parent FeedItem on a supporter-bearing feedable type. Null when no Supporter record matches the commenter for that org. New consumers should prefer this field over `commenter_name`.
      - `created_at` string, date-time — Date/time of initial record creation
      - `id` integer — Primary identifier of record
      - `likes_count` integer — Amount of likes a Comment has received
      - `member_id` integer — The ID of the Member that created of the Comment
      - `updated_at` string, date-time — Date/time of last record update
    - `author_display_name` string, nullable — Supporter-derived display name for the item author. Populated when the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture); also populated on the fail-closed path when the owning Organization cannot be resolved on a supporter-bearing feedable type (soft-deleted feedable, etc.) — Business-agent items surface the business display name and Member-agent items surface null. Resolves to the supporter's first + last name for member-authored items, the business display name for Business-agent items, or null when no Supporter record matches and no safe fallback is available. New consumers should prefer this field over `member_name` / `agent_name`.
  - FeedItemUpdate
    - `id` integer — Primary identifier of record
    - `agent_id` integer, nullable — Primary identifier of the Agent that performed interaction associated with Feed Item
    - `agent_type` 'member' | 'business', nullable — Type of Agent that performed interaction associated with Feed Item
    - `agent_name` string, nullable — Name of Agent that performed interaction associated with Feed Item. When the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture), Member-morph agents return the supporter-derived display name; for creation-type items on fundraising_page / fundraising_team feedables with no Supporter, the page / team title is the fallback (only when it does not match the author member's snapshotted name); otherwise null. Business agents are unaffected. Prefer the new `author_display_name` field for new consumers — `agent_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
    - `member_name` string, nullable — Snapshotted name of the Member associated with the Feed Item (legacy alias preceding the polymorphic `agent` relation). When the owning Organization has Contact-First Architecture enabled, this is replaced with the supporter-derived display name; for creation-type items on fundraising_page / fundraising_team feedables with no Supporter, the page / team title is the fallback (only when it does not match the author member's snapshotted name); for Business agents and otherwise null. Prefer the new `author_display_name` field for new consumers — `member_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
    - `feedable_id` integer — Primary identifier of Fundraising Entity associated with Feed Item’s described interaction
    - `feedable_type` string — Type of the Fundraising Entity associated with Feed Item’s described interaction, same as linkable_type
    - `feedable_value` string, nullable — Name or title of the Item. Under Contact-First Architecture (npo_apiv2_ff_contact_first_architecture), this is null when `feedable_type` is `fundraising_page` or `fundraising_team` (any row type) — the snapshotted page / team title would otherwise re-leak member-seeded names from unguarded write paths (`CompleteRegistrations`, `CreateFundraisingPageForLead`, and the registration-recovery commands).
    - `linkable_id` integer, nullable — Primary identifier of Entity whose creation, update, or association is described by Feed Item
    - `linkable_type` string, nullable — Type of the Entity whose creation, update, or association is described by Feed Item same as feedable_type
    - `linkable_value` string, nullable — Name or title of the Entity whose creation, update, or association is described by Feed Item. Under Contact-First Architecture (npo_apiv2_ff_contact_first_architecture), this is null when `linkable_type` is `fundraising_page` or `fundraising_team` (any row type — the snapshotted page / team title would otherwise re-leak member-seeded names), and for TYPE_ASSOCIATION items where `linkable_type` is a Member morph (the persisted column would otherwise re-leak the member's full name).
    - `linkable_effective_at` string, date-time — Date/time when Linkable is effective
    - `type` 'comment' | 'onboarding' | 'creation' | 'update' | 'association' — Type of the Item
    - `comment` 'null', nullable — Comment
    - `comments_count` integer, nullable — Amount of Comments that the Feed Item has
    - `likes_count` integer, nullable — Amount of Likes that the Feed has
    - `created_at` string, date-time — Date/time when object was created
    - `updated_at` string, date-time — Date/time when object was updated
    - `visibility` 'public' | 'admin' — Visibility status of the Item
    - `latest_comments` Comment[] — Array of latest Comments made in response to Item (limit 2 items)
      - `body` string — The content of the Comment
      - `commentable_id` integer — Primary identifier of associated Commentable Entity
      - `commentable_type` 'feed_item' | 'update' | 'story' — Type of associated Commentable Entity
      - `commenter_name` string — The full name of the creator of the Comment. CFA semantics apply only to comments embedded in a parent FeedItem's `latest_comments` (the FeedItem-level `getLatestCommentsAttribute` override drives the privacy pass). For comments returned by the standalone Post / Story / Update comment endpoints, the legacy shape is preserved regardless of the org's Contact-First Architecture flag — those surfaces are tracked for migration under PRO-4055. When CFA applies (FeedItem-embedded path) and the flag is on (npo_apiv2_ff_contact_first_architecture), this returns the supporter-derived display name (or empty string when no Supporter is found) instead of the member's name. Prefer the new `author_display_name` field for new consumers — `commenter_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
      - `author_display_name` string, nullable — Supporter-derived display name for the comment author. Populated only on FeedItem-embedded comments (`latest_comments`) — the standalone Post / Story / Update comment endpoints do not include this property; that gap is tracked for migration under PRO-4055. On the FeedItem-embedded path: populated when the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture); also populated (often null) on the fail-closed path when the owning Organization cannot be resolved for the parent FeedItem on a supporter-bearing feedable type. Null when no Supporter record matches the commenter for that org. New consumers should prefer this field over `commenter_name`.
      - `created_at` string, date-time — Date/time of initial record creation
      - `id` integer — Primary identifier of record
      - `likes_count` integer — Amount of likes a Comment has received
      - `member_id` integer — The ID of the Member that created of the Comment
      - `updated_at` string, date-time — Date/time of last record update
    - `author_display_name` string, nullable — Supporter-derived display name for the item author. Populated when the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture); also populated on the fail-closed path when the owning Organization cannot be resolved on a supporter-bearing feedable type (soft-deleted feedable, etc.) — Business-agent items surface the business display name and Member-agent items surface null. Resolves to the supporter's first + last name for member-authored items, the business display name for Business-agent items, or null when no Supporter record matches and no safe fallback is available. New consumers should prefer this field over `member_name` / `agent_name`.
  - FeedItemOnboarding
    - `id` integer — Primary identifier of record
    - `agent_id` integer, nullable — Primary identifier of the Agent that performed interaction associated with Feed Item
    - `agent_type` 'member' | 'business', nullable — Type of Agent that performed interaction associated with Feed Item
    - `agent_name` string, nullable — Name of Agent that performed interaction associated with Feed Item. When the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture), Member-morph agents return the supporter-derived display name; for creation-type items on fundraising_page / fundraising_team feedables with no Supporter, the page / team title is the fallback (only when it does not match the author member's snapshotted name); otherwise null. Business agents are unaffected. Prefer the new `author_display_name` field for new consumers — `agent_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
    - `member_name` string, nullable — Snapshotted name of the Member associated with the Feed Item (legacy alias preceding the polymorphic `agent` relation). When the owning Organization has Contact-First Architecture enabled, this is replaced with the supporter-derived display name; for creation-type items on fundraising_page / fundraising_team feedables with no Supporter, the page / team title is the fallback (only when it does not match the author member's snapshotted name); for Business agents and otherwise null. Prefer the new `author_display_name` field for new consumers — `member_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
    - `feedable_id` integer — Primary identifier of Fundraising Entity associated with Feed Item’s described interaction
    - `feedable_type` 'organization' — Type of the Fundraising Entity associated with Feed Item’s described interaction
    - `feedable_value` string, nullable — Name or title of the Item. Under Contact-First Architecture (npo_apiv2_ff_contact_first_architecture), this is null when `feedable_type` is `fundraising_page` or `fundraising_team` (any row type) — the snapshotted page / team title would otherwise re-leak member-seeded names from unguarded write paths (`CompleteRegistrations`, `CreateFundraisingPageForLead`, and the registration-recovery commands).
    - `linkable_id` integer, nullable — Primary identifier of Entity whose creation, update, or association is described by Feed Item
    - `linkable_type` 'null', nullable — Type of the Entity whose creation, update, or association is described by Feed Item
    - `linkable_value` string, nullable — Name or title of the Entity whose creation, update, or association is described by Feed Item. Under Contact-First Architecture (npo_apiv2_ff_contact_first_architecture), this is null when `linkable_type` is `fundraising_page` or `fundraising_team` (any row type — the snapshotted page / team title would otherwise re-leak member-seeded names), and for TYPE_ASSOCIATION items where `linkable_type` is a Member morph (the persisted column would otherwise re-leak the member's full name).
    - `linkable_effective_at` string, date-time — Date/time when Linkable is effective
    - `type` 'comment' | 'onboarding' | 'creation' | 'update' | 'association' — Type of the Item
    - `comment` string, nullable — Comment
    - `comments_count` integer, nullable — Amount of Comments that the Feed Item has
    - `likes_count` integer, nullable — Amount of Likes that the Feed has
    - `created_at` string, date-time — Date/time when object was created
    - `updated_at` string, date-time — Date/time when object was updated
    - `visibility` 'public' | 'admin' — Visibility status of the Item
    - `latest_comments` Comment[] — Array of latest Comments made in response to Item (limit 2 items)
      - `body` string — The content of the Comment
      - `commentable_id` integer — Primary identifier of associated Commentable Entity
      - `commentable_type` 'feed_item' | 'update' | 'story' — Type of associated Commentable Entity
      - `commenter_name` string — The full name of the creator of the Comment. CFA semantics apply only to comments embedded in a parent FeedItem's `latest_comments` (the FeedItem-level `getLatestCommentsAttribute` override drives the privacy pass). For comments returned by the standalone Post / Story / Update comment endpoints, the legacy shape is preserved regardless of the org's Contact-First Architecture flag — those surfaces are tracked for migration under PRO-4055. When CFA applies (FeedItem-embedded path) and the flag is on (npo_apiv2_ff_contact_first_architecture), this returns the supporter-derived display name (or empty string when no Supporter is found) instead of the member's name. Prefer the new `author_display_name` field for new consumers — `commenter_name` is preserved for back-compat with existing apps and will be cleaned up per-app under PRO-2280.
      - `author_display_name` string, nullable — Supporter-derived display name for the comment author. Populated only on FeedItem-embedded comments (`latest_comments`) — the standalone Post / Story / Update comment endpoints do not include this property; that gap is tracked for migration under PRO-4055. On the FeedItem-embedded path: populated when the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture); also populated (often null) on the fail-closed path when the owning Organization cannot be resolved for the parent FeedItem on a supporter-bearing feedable type. Null when no Supporter record matches the commenter for that org. New consumers should prefer this field over `commenter_name`.
      - `created_at` string, date-time — Date/time of initial record creation
      - `id` integer — Primary identifier of record
      - `likes_count` integer — Amount of likes a Comment has received
      - `member_id` integer — The ID of the Member that created of the Comment
      - `updated_at` string, date-time — Date/time of last record update
    - `author_display_name` string, nullable — Supporter-derived display name for the item author. Populated when the owning Organization has Contact-First Architecture enabled (npo_apiv2_ff_contact_first_architecture); also populated on the fail-closed path when the owning Organization cannot be resolved on a supporter-bearing feedable type (soft-deleted feedable, etc.) — Business-agent items surface the business display name and Member-agent items surface null. Resolves to the supporter's first + last name for member-authored items, the business display name for Business-agent items, or null when no Supporter record matches and no safe fallback is available. New consumers should prefer this field over `member_name` / `agent_name`.

## Other responses

- `400` — Malformed payload provided
- `403` — Requester is not authorized to perform action
- `404` — Feed Item not found

---

[API](https://skmtc.net/gofundme/apis/gofundme-pro-api.md) · [All operations](https://skmtc.net/gofundme/apis/gofundme-pro-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/gofundme/gofundme-pro-api/versions/d22bb925eeed/schema)
