> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xem.email/llms.txt
> Use this file to discover all available pages before exploring further.

# Get audience insights

> Get audience analysis



## OpenAPI

````yaml get /api/v1/analytics/audience
openapi: 3.0.3
info:
  title: Xem API
  version: '1.0'
  description: Comprehensive API server for Xem email marketing platform
  contact: {}
  license:
    name: MIT
    url: https://opensource.org/licenses/MIT
servers:
  - url: https://api.xem.email/api/v1
    description: Production server
  - url: http://localhost:8080/api/v1
    description: Development server
security: []
tags:
  - name: Authentication
    description: User authentication and authorization endpoints
  - name: Teams
    description: Team management and collaboration features
  - name: Campaigns
    description: Email campaign creation, management, and tracking
  - name: Analytics
    description: Campaign analytics, audience insights, and performance metrics
  - name: Contacts
    description: Contact management and mailing list operations
  - name: Templates
    description: Email template management and customization
  - name: Automations
    description: Email automation workflows and triggers
  - name: SMTP
    description: SMTP configuration and email delivery settings
  - name: IMAP
    description: IMAP configuration for email inbox management
  - name: Webhooks
    description: Webhook management for real-time event notifications
  - name: Files
    description: File upload and management for attachments and media
  - name: Domains
    description: Domain management for email authentication
  - name: API Keys
    description: API key management for programmatic access
paths:
  /api/v1/analytics/audience:
    get:
      tags: []
      summary: Get audience insights
      description: Get audience analysis
      parameters:
        - name: teamId
          in: query
          description: Team ID
          required: true
          schema:
            type: string
      responses:
        '200':
          description: Audience insights
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/internal_handlers.AudienceInsights'
        '400':
          description: Validation error or team not found
          content:
            application/json:
              schema:
                type: object
                additionalProperties:
                  type: string
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                type: object
                additionalProperties:
                  type: string
      security: []
components:
  schemas:
    internal_handlers.AudienceInsights:
      type: object
      properties:
        behaviors:
          type: object
          additionalProperties:
            $ref: '#/components/schemas/internal_handlers.BehaviorMetrics'
        demographics:
          type: object
          additionalProperties:
            type: integer
        preferences:
          type: object
          additionalProperties:
            $ref: '#/components/schemas/internal_handlers.PreferenceMetrics'
        segments:
          type: array
          items:
            $ref: '#/components/schemas/internal_handlers.AudienceSegment'
    internal_handlers.BehaviorMetrics:
      type: object
      properties:
        count:
          type: integer
        engagementRate:
          type: number
        trend:
          type: string
    internal_handlers.PreferenceMetrics:
      type: object
      properties:
        confidence:
          type: number
        count:
          type: integer
        score:
          type: number
    internal_handlers.AudienceSegment:
      type: object
      properties:
        clickRate:
          type: number
        growth:
          type: number
        name:
          type: string
        openRate:
          type: number
        size:
          type: integer

````