From b9afcaebcd784cdc2b692bddb547fef7622a45c2 Mon Sep 17 00:00:00 2001 From: "David J. Kalbfleisch" <1.21e9W@protonmail.com> Date: Thu, 2 Jan 2025 16:14:45 -0500 Subject: [PATCH] #2035 Update Swagger to reflect the notification statuses as revised for #2163 --- documents/openapi/openapi.yaml | 21 +++++++++------------ 1 file changed, 9 insertions(+), 12 deletions(-) diff --git a/documents/openapi/openapi.yaml b/documents/openapi/openapi.yaml index c3bbd4075e..301aa1d4fc 100644 --- a/documents/openapi/openapi.yaml +++ b/documents/openapi/openapi.yaml @@ -1,7 +1,7 @@ -openapi: 3.0.0 +openapi: 3.0.3 info: title: VA Notify API Documentation - version: 1.0.10 + version: 1.1.0 description: |

This documents the API schemas for consumption by internal VA developers.

Authorization header

@@ -2194,23 +2194,22 @@ components: - webhook - queue NotificationStatus: + description: | +

These statuses do not warrant additional action: cancelled, created, delivered, pending, sending, and sent.

+

These statuses indicate a client-side error, such as specifying a nonexistent template ID, or other condition that will result in VA Notify not retrying to send the notification: failed, permanent-failure, and validation-failed. See the associated status_reason for amplifying information.

+

"temporary-failure" indicates that VA Notify will retry sending the notification.

type: string enum: - cancelled - created - delivered - failed + - pending + - permanent-failure - sending - sent - temporary-failure - - pending - - pending-virus-check - - permanent-failure - - pii-check-failed - - returned-letter - validation-failed - - virus-scan-failed - User: type: object properties: @@ -2943,9 +2942,7 @@ components: nullable: true description: The provider that sent or tried to send the notification status: - type: string - enum: - - created + $ref: '#/components/schemas/NotificationStatus' status_reason: type: string nullable: true