Audited every request (247 .yml files) against the routes the server
actually registers (extracted from internal/router, group prefixes
resolved). Results:
- 44 stale requests: deleted where the endpoint no longer exists
(universal-progress GET/PUT /api/progress/:id — routes never existed,
the handlers were deleted in H1; queue stats/clear-failed/process;
admin profile page; auth/account) and FIXED where the endpoint exists
under a different path (kobo token-in-path scheme: every
/api/sync/kobo/<seg> and /api/v1/kobo/<seg> URL now carries
{{kobo_device_token}}; /sync/* missing their /api prefix; koreader
/api/v1/koreader/sync/* -> /api/sync/koreader/*; link-book and
unlinked-books moved to /api/devices/:id/sync/*).
- koreader Sync Highlights/Sync Notes pointed at endpoints that never
existed with a body shape to match — rewritten against POST
/api/sync/koreader/bookmarks (the annotations funnel carries
highlights and notes arrays).
- 9 files the GUI refused to load: 4 had bruno-invalid script type
"tests" (converted to after-response), 4 were info/type:collection
doc files with bogus http blocks (converted to folder.yml folder
docs), 1 had a dead pre-YAML schema and no route (deleted).
- devices/koreader requests now carry request-level bearer auth
({{koreader_device_token}}) — they inherited the collection's user-JWT
bearer, which device endpoints rightly reject — and their bodies
reference {{media_item_id}} instead of dead placeholder uuids.
- environments: opds_base_url was empty (every OPDS request missed the
/opds prefix); set to http://localhost:8765/opds and un-doubled the
prefix in opds/scenarios.
Known limitation, for the handoff: bru CLI cannot execute .yml request
bodies (the collection is GUI OpenCollection format; the CLI runner
reads bodies from .bru files only). A .bru migration is the remaining
bruno work if CLI runs are wanted.
97 lines
2.6 KiB
YAML
97 lines
2.6 KiB
YAML
info:
|
|
name: Get Analytics Tests
|
|
type: http
|
|
seq: 7
|
|
|
|
http:
|
|
method: POST
|
|
url: '{{base_url}}/api/sync/kobo/{{kobo_device_token}}/v1/analytics/gettests'
|
|
auth: inherit
|
|
headers:
|
|
- key: Content-Type
|
|
value: application/json
|
|
body:
|
|
type: json
|
|
json:
|
|
platform: android
|
|
firmware_version: 4.30.19023
|
|
|
|
docs: |-
|
|
## Get Kobo Analytics Tests
|
|
|
|
Retrieves A/B testing configuration and feature flags for Kobo device.
|
|
|
|
**Method:** POST
|
|
|
|
**Endpoint:** /api/sync/kobo/v1/analytics/gettests
|
|
|
|
**Authentication:** Bearer token
|
|
|
|
**Request Body:**
|
|
- `platform` (string): Device platform
|
|
- `android`: Kobo Android app
|
|
- `kobo`: Native Kobo firmware
|
|
- `firmware_version` (string): Firmware version (e.g., "4.30.19023")
|
|
- `device_model` (string, optional): Device model identifier
|
|
- `locale` (string, optional): Device locale (e.g., "en_US")
|
|
|
|
**Response:**
|
|
- `tests` (array): Active A/B tests
|
|
- `test_name` (string): Test identifier
|
|
- `variant` (string): Assigned variant (A, B, C, etc.)
|
|
- `enabled` (boolean): Whether test is active
|
|
- `parameters` (object): Test-specific parameters
|
|
- `features` (object): Feature flags
|
|
- `feature_name` (boolean/string): Feature state
|
|
- `configuration` (object): Device configuration
|
|
- `sync_interval_minutes` (integer): Recommended sync frequency
|
|
- `batch_size` (integer): Max items per batch sync
|
|
- `timeout_seconds` (integer): Request timeout
|
|
- `version` (string): Configuration version
|
|
|
|
**Status Codes:**
|
|
- 200: Success
|
|
- 401: Unauthorized
|
|
- 400: Invalid request parameters
|
|
|
|
**Analytics Testing Purpose:**
|
|
- Kobo uses A/B testing for UX features
|
|
- Feature flags for gradual rollout
|
|
- Performance monitoring configuration
|
|
- Sync behavior optimization
|
|
- Device-specific tuning
|
|
|
|
**Common Tests:**
|
|
- Sync frequency optimization
|
|
- UI/UX variations
|
|
- Network usage patterns
|
|
- Battery life improvements
|
|
- Feature set variations by model
|
|
|
|
**Feature Flags:**
|
|
- New sync features
|
|
- Beta functionality
|
|
- Platform-specific capabilities
|
|
- Experimental features
|
|
|
|
**Configuration Parameters:**
|
|
- Optimal sync intervals for device
|
|
- Batch size limits based on device capabilities
|
|
- Timeout values for network conditions
|
|
- Retry logic configuration
|
|
- Cache policy settings
|
|
|
|
**Usage:**
|
|
- Called during device initialization
|
|
- Refreshed daily or weekly
|
|
- Cached on device
|
|
- Affects sync behavior
|
|
- Can be overridden by server
|
|
|
|
**Use Cases:**
|
|
- Device initialization
|
|
- Feature rollout testing
|
|
- Performance optimization
|
|
- UX experiment participation
|
|
- Configuration management
|