info:
  name: Get Analytics Tests
  type: http
  seq: 7

http:
  method: POST
  url: '{{base_url}}/api/sync/kobo/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
