> ## Documentation Index
> Fetch the complete documentation index at: https://omniflow-vpn.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Put v1panelanalytics

> Requires settings.write and the current `version`.
A counter is a provider this repository knows and an identifier validated against its shape — never a snippet. The flexibility given up is exactly the ability to run arbitrary code in a customer's browser, and a customer's browser holds subscription links. `enabled` is separate from having identifiers so turning measurement off does not mean finding the numbers again to turn it back on.
Verification tags are a name from an allowlist and an opaque token. They set no cookie, load no script, and observe nobody, which is why they render regardless of `enabled` and regardless of consent — a verification that only appeared for consenting visitors would verify nothing, because the fetcher is a webmaster tool rather than a person.



## OpenAPI

````yaml https://raw.githubusercontent.com/kewldan/omniflow/main/api/openapi.yaml put /v1/panel/analytics
openapi: 3.0.3
info:
  title: Omniflow API
  version: 1.0.0
  description: >-
    Customer, commerce, payment, wallet, fulfillment, and operations API for
    Omniflow.
servers: []
security: []
paths:
  /v1/panel/analytics:
    put:
      tags:
        - panel
      description: >-
        Requires settings.write and the current `version`.

        A counter is a provider this repository knows and an identifier
        validated against its shape — never a snippet. The flexibility given up
        is exactly the ability to run arbitrary code in a customer's browser,
        and a customer's browser holds subscription links. `enabled` is separate
        from having identifiers so turning measurement off does not mean finding
        the numbers again to turn it back on.

        Verification tags are a name from an allowlist and an opaque token. They
        set no cookie, load no script, and observe nobody, which is why they
        render regardless of `enabled` and regardless of consent — a
        verification that only appeared for consenting visitors would verify
        nothing, because the fetcher is a webmaster tool rather than a person.
      operationId: savePanelAnalytics
      parameters:
        - $ref: '#/components/parameters/CSRFToken'
      requestBody:
        required: true
        content:
          application/json:
            schema:
              allOf:
                - $ref: '#/components/schemas/AnalyticsSettingsInput'
                - type: object
                  required:
                    - version
                  properties:
                    version:
                      type: integer
                      format: int32
      responses:
        '200':
          description: Saved
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PanelAnalytics'
        '403':
          $ref: '#/components/responses/Problem'
        '409':
          $ref: '#/components/responses/Problem'
        '422':
          $ref: '#/components/responses/Problem'
components:
  parameters:
    CSRFToken:
      in: header
      name: X-CSRF-Token
      required: true
      description: >-
        Echoes the token from the current session. Required on every unsafe
        method.
      schema:
        type: string
  schemas:
    AnalyticsSettingsInput:
      type: object
      properties:
        enabled:
          type: boolean
          description: >-
            False on a fresh installation. Nothing renders or is captured until
            this is on.
        counters:
          type: object
          description: >-
            Identifier per provider. `yandex_metrica` is a counter number;
            `google_analytics` is a measurement ID such as G-XXXXXXX.
          additionalProperties:
            type: string
        verifications:
          type: array
          maxItems: 8
          items:
            $ref: '#/components/schemas/AnalyticsVerification'
    PanelAnalytics:
      allOf:
        - $ref: '#/components/schemas/AnalyticsSettingsInput'
        - type: object
          required:
            - version
            - providers
            - verificationNames
          properties:
            version:
              type: integer
              format: int32
            updatedAt:
              type: string
              format: date-time
            updatedBy:
              type: string
              format: uuid
            providers:
              type: array
              description: >-
                The counters this build can render, so the screen offers what
                exists.
              items:
                type: string
            verificationNames:
              type: array
              items:
                type: string
    AnalyticsVerification:
      type: object
      required:
        - name
        - content
      properties:
        name:
          type: string
          enum:
            - google-site-verification
            - yandex-verification
            - msvalidate.01
            - facebook-domain-verification
        content:
          type: string
          minLength: 8
          maxLength: 128
    Problem:
      type: object
      required:
        - type
        - title
        - status
      properties:
        type:
          type: string
          format: uri
        title:
          type: string
        status:
          type: integer
        detail:
          type: string
        request_id:
          type: string
  responses:
    Problem:
      description: Request failed
      content:
        application/problem+json:
          schema:
            $ref: '#/components/schemas/Problem'

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.