From 5f4cea95156c1b6348fae38d4ae8de0fad19520d Mon Sep 17 00:00:00 2001 From: jeremyhunton-va <99915461+jeremyhunton-va@users.noreply.github.com> Date: Thu, 9 Apr 2026 13:52:28 +0000 Subject: [PATCH 1/3] added release note for API-53882 which adds supporting documents filtering to the v2 /show endpoint. --- content/benefits/claims/release-notes/2026-04-09.md | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 content/benefits/claims/release-notes/2026-04-09.md diff --git a/content/benefits/claims/release-notes/2026-04-09.md b/content/benefits/claims/release-notes/2026-04-09.md new file mode 100644 index 00000000..4939d4bd --- /dev/null +++ b/content/benefits/claims/release-notes/2026-04-09.md @@ -0,0 +1,5 @@ +We added supporting document filtering to the V2 claims `/show` endpoint located at: + +- `services/claims/v2/veterans/{veteran_icn}/claims/:claim_id` + +The filtering changes will return only veteran/claimant generated supporting documents, and will filter out supporting documents generated from the VA that come from the Benefits Documents Claim Letters Search endpoint. \ No newline at end of file From d1f1779b1a0a53aec362a7342ba18459bb7c3b88 Mon Sep 17 00:00:00 2001 From: jeremyhunton-va <99915461+jeremyhunton-va@users.noreply.github.com> Date: Mon, 20 Apr 2026 13:59:01 +0000 Subject: [PATCH 2/3] updated date timestamp on md file name --- .../claims/release-notes/{2026-04-09.md => 2026-04-21.md} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename content/benefits/claims/release-notes/{2026-04-09.md => 2026-04-21.md} (92%) diff --git a/content/benefits/claims/release-notes/2026-04-09.md b/content/benefits/claims/release-notes/2026-04-21.md similarity index 92% rename from content/benefits/claims/release-notes/2026-04-09.md rename to content/benefits/claims/release-notes/2026-04-21.md index 4939d4bd..1cd39dfa 100644 --- a/content/benefits/claims/release-notes/2026-04-09.md +++ b/content/benefits/claims/release-notes/2026-04-21.md @@ -2,4 +2,4 @@ We added supporting document filtering to the V2 claims `/show` endpoint located - `services/claims/v2/veterans/{veteran_icn}/claims/:claim_id` -The filtering changes will return only veteran/claimant generated supporting documents, and will filter out supporting documents generated from the VA that come from the Benefits Documents Claim Letters Search endpoint. \ No newline at end of file +The filtering changes will return only veteran/claimant generated supporting documents, and will filter out supporting documents generated from the VA that come from the Benefits Documents Claim Letters Search endpoint. From 480451d933518da2bda3e437ae35e108103fa52d Mon Sep 17 00:00:00 2001 From: joshmiranda-va <249175166+joshmiranda-va@users.noreply.github.com> Date: Tue, 21 Apr 2026 12:10:33 -0600 Subject: [PATCH 3/3] Update 2026-04-21.md --- content/benefits/claims/release-notes/2026-04-21.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/content/benefits/claims/release-notes/2026-04-21.md b/content/benefits/claims/release-notes/2026-04-21.md index 1cd39dfa..73a7cf37 100644 --- a/content/benefits/claims/release-notes/2026-04-21.md +++ b/content/benefits/claims/release-notes/2026-04-21.md @@ -1,5 +1,9 @@ -We added supporting document filtering to the V2 claims `/show` endpoint located at: +We updated version 2 of the Benefits Claims API to improve the supporting documents returned by the GET /veterans/{veteranId}/claims/{id} endpoint. -- `services/claims/v2/veterans/{veteran_icn}/claims/:claim_id` +**What’s new?** -The filtering changes will return only veteran/claimant generated supporting documents, and will filter out supporting documents generated from the VA that come from the Benefits Documents Claim Letters Search endpoint. +The endpoint now filters supporting documents to return only those submitted by the Veteran or claimant. Previously, the `supportingDocuments` field could include documents created by VA systems, such as items identified by the Benefits Documents API. + +With this update, VA-generated documents are no longer included in the response. This presents a clearer view of evidence provided by the claimant and helps avoid confusion when reviewing a claim’s supporting documentation. + +To learn more, review the [Benefits Claims API documentation](https://developer.va.gov/explore/api/benefits-claims/docs?version=current).