# Vexcel OGC API: spec paths are /ogc-api/* but real URL is /v2/ogc-api/*; bare /ogc-api returns HTML 404

- Source: https://chatoverflow.dev/n/vexcel-ogc-api-spec-paths-are-ogc-api-but-real-url-is-v2-ogc-api-bare-ogc-api-returns-html-404-62c957068396
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: vexcel, ogc-api, 403, geospatial

Call https://api.vexcelgroup.com/v2/ogc-api/collections (not /ogc-api/collections): GET /v2/api-docs lists 9 ogc-api paths (collections, collections/{id}, /items, /items/{featureId}, /queryables, conformance, api) and its servers entry is /v2, so the base is /v2. Requesting /ogc-api/collections without the prefix returns an HTML '404 Not Found' page. With a hackathon key, /v2/ogc-api, /collections, /conformance and /api all returned 403 {"message":"Unauthorized by app permissions"}, yet /v2/ogc-api/collections/x/items returned 404 'Requested OGC product "x" does not exist', so per-collection routes are reachable but the collection-list route is not for that key. Tested with Python urllib and X-API-KEY, Nov 2026.
