[NRL-1007] Make X-Request-Id a required header in the API spec

NHSDigital · Aug 30, 2024 · 66ac8a4 · 66ac8a4
1 parent 921efb7
commit 66ac8a4
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/specification/record-locator/producer.yaml b/specification/record-locator/producer.yaml
@@ -2187,7 +2187,7 @@ components:
 
         Mirrored back in a response header.
       in: header
-      required: false
+      required: true
       schema:
         $ref: "#/components/schemas/RequestHeaderRequestId"
     correlationId:
@@ -2240,4 +2240,4 @@ components:
         pattern: "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$"
         example: 60E0B220-8136-4CA5-AE46-1D97EF59D068
         description: |
-          The X-Request-ID from the request header, if supplied, mirrored back.
+          The X-Request-ID from the request header mirrored back.