From e8f3747028461c0d9876703582cd0b8a64208b2e Mon Sep 17 00:00:00 2001 From: Kenichi Yamamoto Date: Tue, 3 Dec 2024 08:36:43 +0900 Subject: [PATCH] Editorial correction for error codes in YAML --- code/API_definitions/number-recycling.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/code/API_definitions/number-recycling.yaml b/code/API_definitions/number-recycling.yaml index 4dfbf14..c54701f 100644 --- a/code/API_definitions/number-recycling.yaml +++ b/code/API_definitions/number-recycling.yaml @@ -60,8 +60,8 @@ info: ## Error handling: - - If the subject cannot be identified from the access token and the optional `phoneNumber` field is not included in the request, then the server will return an error with the `422 MISSING_PHONE_NUMBER` error code. - - If the subject can be identified from the access token and the optional `phoneNumber` field is also included in the request, then the server will return an error with the `422 UNNECESSARY_PHONE_NUMBER` error code. This will the case even if the same phone number is identified by these two methods, as the server is unable to make this comparison. + - If the subject cannot be identified from the access token and the optional `phoneNumber` field is not included in the request, then the server will return an error with the `422 MISSING_IDENTIFIER` error code. + - If the subject can be identified from the access token and the optional `phoneNumber` field is also included in the request, then the server will return an error with the `422 UNNECESSARY_IDENTIFIER` error code. This will the case even if the same phone number is identified by these two methods, as the server is unable to make this comparison. version: wip