From 393b7c18b98938aac10b364ba4dcf4ccb8728932 Mon Sep 17 00:00:00 2001
From: Maximilian Laue <Maximilian.Laue@t-systems.com>
Date: Wed, 3 Jul 2024 15:09:06 +0200
Subject: [PATCH] fix: move `AreaNotCovered` example to 422 instead of 400

---
 code/API_definitions/geofencing-subscriptions.yaml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/code/API_definitions/geofencing-subscriptions.yaml b/code/API_definitions/geofencing-subscriptions.yaml
index b2e401d..ce6accb 100644
--- a/code/API_definitions/geofencing-subscriptions.yaml
+++ b/code/API_definitions/geofencing-subscriptions.yaml
@@ -1106,11 +1106,6 @@ components:
                 status: 400
                 code: "INVALID_TOKEN"
                 message: "Only bearer token is supported"
-            AreaNotCovered:
-              value:
-                status: 400
-                code: "AREA_NOT_COVERED"
-                message: "The specified area cannot be covered or is too small to be valid"
 
     Generic400:
       description: Problem with the client request
@@ -1239,6 +1234,11 @@ components:
                 status: 422
                 code: "MULTIEVENT_SUBSCRIPTION_NOT_SUPPORTED"
                 message: "Multi event types subscription not managed"
+            AreaNotCovered:
+              value:
+                status: 422
+                code: "AREA_NOT_COVERED"
+                message: "The specified area cannot be covered or is too small to be valid"
     Generic429:
       description: Too Many Requests
       headers: