> ## Documentation Index > Fetch the complete documentation index at: https://documentation.qonversion.io/llms.txt > Use this file to discover all available pages before exploring further. # Get analytics chart metadata > Returns the chart's display metadata: available filter attributes and their concrete values (pre-scoped to the project), available segmentation dimensions, supported time units, and chart types. Use this to build a UI / discover the `filter[][]` and `segmentation` values for `GET /v4/analytics/charts/{chart_code}`. ## OpenAPI ````yaml /api-reference/rest-api-v4.yaml get /analytics/charts/{chart_code}/meta openapi: 3.0.3 info: title: Qonversion REST API v4 version: '4.0' description: >- Qonversion REST API v4 follows REST standards. It has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. servers: - url: https://api.qonversion.io/v4 description: Production security: - secretAuth: [] tags: - name: Users description: Retrieve Qonversion users - name: User Properties description: Manage user-level attributes - name: Identities description: Link Qonversion users to your own auth IDs - name: Entitlements description: Entitlement definitions and user grants - name: Purchases description: A user's purchase history - name: Products description: Products configured in the Qonversion dashboard - name: Customers description: Aggregated customer records, properties, permissions, and metrics - name: Segments description: Dynamic and system segments of users - name: Experiments description: Paywall and offering A/B experiments - name: Screens description: No-code paywall screens — CRUD, publish, analytics - name: Analytics description: Charts, cards, cohorts, LTV, and insights - name: Exports description: Asynchronous data exports - name: Events description: Event catalog - name: Scheduled Reports description: Recurring reports delivered to external destinations - name: Integrations description: Third-party integrations configuration - name: Automations description: Event-driven automations - name: Project Settings description: Project-level configuration, secret, and store credentials paths: /analytics/charts/{chart_code}/meta: get: tags: - Analytics summary: Get analytics chart metadata description: > Returns the chart's display metadata: available filter attributes and their concrete values (pre-scoped to the project), available segmentation dimensions, supported time units, and chart types. Use this to build a UI / discover the `filter[][]` and `segmentation` values for `GET /v4/analytics/charts/{chart_code}`. operationId: v4GetAnalyticsChartMeta parameters: - name: chart_code in: path required: true description: >- Chart code. Must be a publicly exposed chart (see `GET /v4/analytics/charts/{chart_code}`). schema: type: string enum: - proceeds - active-subscriptions - paid-subscriptions-movement - users-overview - free-trials - active-trials - trials-movement - user-to-trial - trial-to-paid - user-to-paid - sales - refunds - refund-rate - arppu - arpu - trial-cancellation - subscription-cancellation - subscriptions-overview - new-subscriptions - mrr - arr - mrr-movement - arr-movement - user-to-trial-conversion - subscription-cancellation-rate maxLength: 64 example: proceeds - name: from in: query required: false description: >- Time range start (Unix timestamp, seconds). Used to scope filter value enumeration. schema: type: integer format: int64 - name: to in: query required: false description: >- Time range end (Unix timestamp, seconds). Used to scope filter value enumeration. schema: type: integer format: int64 - name: environment in: query required: false description: 'Environment: `0` = sandbox, `1` = production.' schema: type: integer enum: - 0 - 1 default: 1 responses: '200': description: Chart metadata. headers: Cache-Control: schema: type: string example: no-cache content: application/json: schema: $ref: '#/components/schemas/V4AnalyticsChartMeta' example: object: analytics_chart_meta url: /v4/analytics/charts/proceeds/meta code: proceeds title: Proceeds description: >- Shows net revenue (after refunds), with App Stores' commission already deducted. docUrl: https://documentation.qonversion.io/docs/revenue#proceeds isAvailable: true availabilityMessage: '' type_default: column types: - line - column - area units_available: - hour - day - week - month segmentations: - code: target_platform label: Store - code: country label: Country - code: product_id label: Product filter_conditions: - attribute: target_platform label: Store multiple: true type: list values: - code: iOS label: Apple App Store - code: Android label: Google Play - code: Stripe label: Stripe - attribute: country label: Country multiple: true type: list values: - code: US label: United States of America - code: GB label: United Kingdom - attribute: device_id category: Device label: Device ID type: text '400': description: Invalid request parameters content: application/json: schema: $ref: '#/components/schemas/V4Error' '401': description: Unauthorized content: application/json: schema: $ref: '#/components/schemas/V4Error' '403': description: Insufficient permissions content: application/json: schema: $ref: '#/components/schemas/V4Error' '404': description: Chart not found content: application/json: schema: $ref: '#/components/schemas/V4Error' '429': description: Too many requests content: application/json: schema: $ref: '#/components/schemas/V4Error' '500': description: Internal error content: application/json: schema: $ref: '#/components/schemas/V4Error' '502': description: Upstream service failure content: application/json: schema: $ref: '#/components/schemas/V4Error' '504': description: Upstream timeout content: application/json: schema: $ref: '#/components/schemas/V4Error' security: - secretAuth: [] components: schemas: V4AnalyticsChartMeta: type: object required: - object - url - code - title - isAvailable - segmentations - filter_conditions - units_available properties: object: type: string enum: - analytics_chart_meta url: type: string code: type: string title: type: string description: type: string docUrl: type: string description: Link to the narrative documentation for this chart. isAvailable: type: boolean description: >- False when the chart is blocked by the project's plan or feature flag. availabilityMessage: type: string description: >- Human-readable reason the chart is unavailable. Empty when `isAvailable=true`. type_default: type: string description: Recommended visual type (e.g. `column`). types: type: array items: type: string enum: - line - column - area - bar - pie units_available: type: array items: type: string enum: - hour - day - week - month segmentations: type: array items: $ref: '#/components/schemas/V4AnalyticsSegmentation' filter_conditions: type: array items: $ref: '#/components/schemas/V4AnalyticsFilterCondition' V4Error: type: object required: - error properties: error: type: object required: - type - code - message properties: type: type: string enum: - request - resource - logical - internal code: type: string description: | Machine-readable snake_case error code. Examples include `invalid_data`, `invalid_request`, `invalid_product_id`, `not_found`, `already_exists`, `offering_already_exists`, `product_not_in_project`, `cannot_set_main_directly`, `cannot_demote_main`, `cannot_patch_experiment_variant`, `cannot_delete_experiment_variant`, and `cannot_setmain_experiment_variant`. Resource-specific codes are documented on the corresponding reference page. message: type: string description: Human-readable description. May change; do not parse. details: type: array nullable: true description: Per-field validation errors, present on 400 validation failures. items: type: object properties: field: type: string message: type: string V4AnalyticsSegmentation: type: object required: - code - label properties: code: type: string label: type: string category: type: string V4AnalyticsFilterCondition: type: object required: - attribute - label - type properties: attribute: type: string description: Filter attribute code — use as `filter[][]` query key. category: type: string description: >- Optional UI grouping (`Device`, `Customer / ID`, `Experiment`, `Attribution`). label: type: string type: type: string enum: - list - text description: > * `list` — value must be one of `values[].code`; supports multi-select when `multiple=true`. * `text` — free-form single value (e.g. `user_id`, `device_id`, `q_user_id`). multiple: type: boolean persistent: type: boolean description: Hint to the UI that this filter should always be visible. values: type: array description: Allowed values for `list`-type filters. items: type: object required: - code - label properties: code: type: string label: type: string securitySchemes: secretAuth: type: http scheme: bearer bearerFormat: sk_… description: >- Bearer authentication using the project **Secret Key** (prefixed with `sk_`, or `test_sk_` for sandbox). All v4 public endpoints require the Secret Key — see [Authentication](/reference/v4/authentication). Never expose the Secret Key in client-side code. ````