Restructure Stores API as its own heading with separate sub-tags

Split the single "Stores API" tag into three separate tags
(Store Search, Data Management, Zones) under a new "Stores API"
tag group heading, matching the pattern used by "Map" and "Distance".

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: cmillett

redocly/redocly-merged-config.yaml

@@ -116,12 +116,16 @@ apis:
         tagGroups:
           - name: "Search"
             tags:
-              - "Stores API"
               - "Geolocation API"
               - "Localities API"
               - "Address API"
               - "Datasets API"
               - "Woosmap for what3words API"
+          - name: "Stores"
+            tags:
+              - "Store Search"
+              - "Data Management"
+              - "Zones"
           - name: "Map"
             tags:
               - "Static Map API"

redocly/redocly-validate-config.yaml

@@ -12,7 +12,9 @@ rules:
     severity: error
     requireOperationTags: true
     expectedNames:
-      - "Stores API"
+      - "Store Search"
+      - "Data Management"
+      - "Zones"
       - "Geolocation API"
       - "Localities API"
       - "Address API"

specification/index.yml

@@ -56,16 +56,17 @@ security:
   - PrivateApiKeyAuth: []
   - PrivateApiKeyHeaderAuth: []
 tags:
-  - name: Stores API
+  - name: Search
     description: >
-      Stores API lets you query the Assets which are returned as a [GeoJson](https://geojson.org/).
+      Store Search lets you query the Assets which are returned as a [GeoJson](https://geojson.org/).
       Request is done over HTTPS using GET.
       You must specify a key in your request, included as the value of a `key` parameter for your public key or `private_key` for your private key.
       This key identifies your application for purposes of quota management. Learn how to [get a key](https://developers.woosmap.com/support/api-keys/).
       If your request returns a high number of assets, the result will be paginated. If so, you can request assets by page using `page` and `stores_by_page` parameters (Default is **100**, max is **300**).
-
-      ## Data Management
-
+    externalDocs:
+      url: https://developers.woosmap.com/products/stores-api/overview/
+  - name: Data Management
+    description: >
       Manage the store and asset data within your Woosmap project. It provides full CRUD (Create, Read, Update, Delete) operations
       through standard HTTP methods, supporting batch imports up to 15MB, along with an atomic replace operation for swapping
       entire datasets without downtime.
@@ -79,9 +80,10 @@ tags:
       ```
       POST|GET|PUT|DELETE https://api.woosmap.com/stores
       ```
-
-      ## Zones
-
+    externalDocs:
+      url: https://developers.woosmap.com/products/stores-api/overview/
+  - name: Zones
+    description: >
       The Zones Endpoint lets you associate geographic polygons (zones) with your stores and then search for stores whose zone
       contains a specific point. Unlike distance-based search, which relies on straight-line proximity, zone-based search accounts
       for real-world boundaries like delivery areas, service regions, or franchise territories.
@@ -122,7 +124,7 @@ tags:
       Request is done over HTTPS using GET. Response is formatted as JSON.
       You must specify a key in your request, included as the value of a `key` parameter for your public key or `private_key` for your private key.
       This key identifies your application for purposes of quota management. Learn how to [get a key](https://developers.woosmap.com/support/api-keys/).
-      
+
       >**⚠️ This API has been deprecated in favour of Localities API**
     externalDocs:
       url: https://developers.woosmap.com/products/address-api/get-started/

specification/paths/search/storesAutocomplete.yml

@@ -1,7 +1,7 @@
 servers:
   - url: https://api.woosmap.com
 tags:
-  - Stores API
+  - Store Search
 description: >
   Autocomplete on `localizedNames` with highlighted results on asset name.
   Use the field `localized` in your query parameter to search for localized names.

specification/paths/search/storesBounds.yml

@@ -1,7 +1,7 @@
 servers:
   - url: https://api.woosmap.com
 tags:
-  - Stores API
+  - Store Search
 description: >
   Used to retrieve Bounds for assets.
 security:

specification/paths/search/storesSearch.yml

@@ -1,7 +1,7 @@
 servers:
   - url: https://api.woosmap.com
 tags:
-  - Stores API
+  - Store Search
 description: >
   Used to retrieve assets from query.
 security:

specification/paths/stores/storeGet.yml

@@ -1,7 +1,7 @@
 servers:
   - url: https://api.woosmap.com
 tags:
-  - Stores API
+  - Data Management
 description: >
   Used to retrieve an asset from his `storeId`
 security:

specification/paths/stores/storesCreate.yml

@@ -1,7 +1,7 @@
 servers:
   - url: https://api.woosmap.com
 tags:
-  - Stores API
+  - Data Management
 description: >
   Used to batch create Assets to a specific project identified with the `private_key` parameter.
 security:

specification/paths/stores/storesDelete.yml

@@ -2,7 +2,7 @@
 servers:
   - url: https://api.woosmap.com
 tags:
-  - Stores API
+  - Data Management
 description: >
   Used to delete one or more assets. The `storeId` specified in `query` parameter is the id of the asset to delete. To delete several assets, use the comma as a separator.
   To delete all project assets, omit the `query` parameter.

specification/paths/stores/storesReplace.yml

@@ -1,7 +1,7 @@
 servers:
   - url: https://api.woosmap.com
 tags:
-  - Stores API
+  - Data Management
 description: To replace all your Assets. This endpoint will delete all previous assets and import assets in request body.
   During the operation previous assets could always be displayed on map.
   If the import failed previous assets are not deleted.