The Catalogue Route on Our API... Note

The Catalogue Route on Our API Host: 43 Records, 22 Enabled, One Renamed Slug

The OnePassApps API route GET https://api.onepassapps.com/api/products returns a JSON response with 43 product records. These records contain eleven fields each, detailing product status, availability, and launch information. Analysis of these fields reveals that 38 products are prototype-ready and 5 require specification. Twenty-two are marked as enabled and 21 as disabled, with corresponding appEnabled and appDisabled values. Notably, 41 products have their launchSurface set to 'blocked', while only two are set to 'launch'.A separate feature-flag route, /api/config/feature-flags, lists 43 product-enabled switches, all reading true. However, this route does not specify which products users can access. When comparing the results of the product catalogue route and the feature-flag route, a discrepancy is found for 21 products. The feature-flag route indicates these products are 'on', but the catalogue marks them as 'appEnabled: false' and 'availability: "disabled"'.The public sitemap lists 22 application routes, and 21 of these correspond directly to the enabled slugs in the catalogue. One product, 'newsflow', appears differently in the URL and the API/flag data, being named 'signaldesk' in the latter. The two routes that have 'launchSurface' set to 'launch' are 'signaldessk' and 'movie-tracker', which are also confirmed by the runtime route.The OnePassApps API host has 74 probed paths, with only a few returning successful responses. The /api/products route's data structure differs from the format used by the application's code. The public site's visibility of an app depends on its enabled status, not its launch scope. Crucially, none of the publicly available OnePassApps files or the API's robots.txt mention the /api/products route. The author clarifies that no keys, sign-ins, writes, or flag flips were performed during testing.