From 9a65a09b0cf731dfba0b451c48245aa0db201434 Mon Sep 17 00:00:00 2001
From: Matt Dean <matt.dean3@nhs.net>
Date: Fri, 30 Aug 2024 08:49:32 +0100
Subject: [PATCH] [NRL-1007] Make X-Request-Id a required header in the API
 spec

---
 specification/record-locator/consumer.yaml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/specification/record-locator/consumer.yaml b/specification/record-locator/consumer.yaml
index b40f65c..0f76ce4 100644
--- a/specification/record-locator/consumer.yaml
+++ b/specification/record-locator/consumer.yaml
@@ -1603,7 +1603,7 @@ components:
 
         Mirrored back in a response header.
       in: header
-      required: false
+      required: true
       schema:
         $ref: "#/components/schemas/RequestHeaderRequestId"
     correlationId:
@@ -1646,4 +1646,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.