From b4833b06846dead358a8cb294d6fad7998cde6bc Mon Sep 17 00:00:00 2001 From: Nicolas Werner Date: Wed, 11 Sep 2024 17:57:21 +0200 Subject: [PATCH] Clarify that third-party location lookups use user-defined query parameters While 14051847653383e432ebacae2cc430cc9ebce1e0 redefined most fields to be the appropriate object type, it missed one of them. Signed-off-by: Nicolas Werner --- data/api/client-server/third_party_lookup.yaml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/data/api/client-server/third_party_lookup.yaml b/data/api/client-server/third_party_lookup.yaml index 97547a6f..3055b8ae 100644 --- a/data/api/client-server/third_party_lookup.yaml +++ b/data/api/client-server/third_party_lookup.yaml @@ -98,12 +98,14 @@ paths: schema: type: string - in: query - name: searchFields + name: fields description: |- One or more custom fields to help identify the third-party location. schema: - type: string + type: object + additionalProperties: + type: string responses: "200": description: At least one portal room was found.