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

# Time series report

> **Read-only.** It changes nothing.

Parallel daily series — engagements, invites, messages, InMails, follows, event invites, opportunities, emails sent/opened/clicked/bounced, accepted, replied — aligned to a shared `dates` array. The right endpoint for "how did we trend over the last 30 days". A series per day, not a total: for one campaign's totals use `analytics_campaign`, and for months rather than days use `analytics_trend`. Note it scopes by LinkedIn account, not by campaign.



## OpenAPI

````yaml /api-v2/openapi.json post /analytics_reporting
openapi: 3.1.0
info:
  title: LinkedCamp API
  version: 2.0.0
  description: >-
    Version 2 of the LinkedCamp API. Every endpoint is a POST to `/{endpoint}`
    with its arguments as a JSON object, and returns JSON.
servers:
  - url: https://api.linkedcamp.com/v2
security:
  - ApiKey: []
  - Bearer: []
tags:
  - name: Account
  - name: Notifications
  - name: Reference
  - name: Campaigns
  - name: Campaign audience
  - name: Sequences
  - name: Blocked dates
  - name: Leads
  - name: Lead notes
  - name: Activities
  - name: Tags
  - name: Blacklist
  - name: Conversations
  - name: Messages
  - name: Saved replies
  - name: Templates
  - name: Merge fields
  - name: Personalised images
  - name: LinkedIn accounts
  - name: Email accounts
  - name: AI agents
  - name: Knowledge base
  - name: Personas
  - name: Analytics
  - name: Posts
  - name: Posting schedule
  - name: Tasks
  - name: Appointments
  - name: Reminders
  - name: Automations
paths:
  /analytics_reporting:
    post:
      tags:
        - Analytics
      summary: Time series report
      description: >-
        **Read-only.** It changes nothing.


        Parallel daily series — engagements, invites, messages, InMails,
        follows, event invites, opportunities, emails
        sent/opened/clicked/bounced, accepted, replied — aligned to a shared
        `dates` array. The right endpoint for "how did we trend over the last 30
        days". A series per day, not a total: for one campaign's totals use
        `analytics_campaign`, and for months rather than days use
        `analytics_trend`. Note it scopes by LinkedIn account, not by campaign.
      operationId: analytics_reporting
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                linkedAccountId:
                  type: string
                  description: Narrow to one LinkedIn account.
                userId:
                  type: string
                  description: >-
                    Read a SUB-ACCOUNT instead of your own data. Accepted only
                    from an agency owner, and only for an account inside your
                    own agency: take the id from `subaccount_list` and never
                    construct or guess one. An id outside that list is refused.
                    Omit it to read your own data, and name the account to the
                    user when you pass it.
                range:
                  type: object
                  properties:
                    from:
                      type:
                        - string
                        - number
                      description: Start of the window.
                    to:
                      type:
                        - string
                        - number
                      description: End of the window.
                    startDate:
                      type:
                        - string
                        - number
                      description: Alias for `from`.
                    endDate:
                      type:
                        - string
                        - number
                      description: Alias for `to`.
                  additionalProperties: false
                  description: >-
                    Date window as { from, to } — epoch milliseconds or ISO
                    8601. Omit for the backend default.
                filter:
                  type: array
                  items:
                    type: string
                  description: >-
                    Restrict to specific series names, e.g.
                    ["invites","accepted","replied"].
              additionalProperties: false
      responses:
        '200':
          description: >-
            The result, as JSON. Writes answer `{ "ok": true, "message": ...,
            "data": ... }`.
          content:
            application/json:
              schema:
                type: object
                additionalProperties: true
        '400':
          description: >-
            The body is not valid JSON, an argument is invalid, or the request
            was refused.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: No API key, or the key was rejected.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: >-
            Your plan, permissions or access tier don't include this, or a
            record belongs to another account.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: A record named in the arguments does not exist.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '422':
          description: >-
            The request was valid but the operation was refused, such as
            launching a campaign that is not ready.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '502':
          description: The service failed or could not be reached. Reads are safe to retry.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '504':
          description: >-
            The operation timed out. A write may still complete; read it back
            before retrying.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    Error:
      type: object
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              enum:
                - UNAUTHENTICATED
                - FORBIDDEN
                - PLAN_REQUIRED
                - VALIDATION
                - INVALID_JSON
                - NOT_FOUND
                - METHOD_NOT_ALLOWED
                - UPSTREAM
                - TOOL_ERROR
            message:
              type: string
            hint:
              type: string
              description: What to do about it, when there is something to do.
  securitySchemes:
    ApiKey:
      type: apiKey
      in: header
      name: X-Api-Key
      description: Your LinkedCamp API key.
    Bearer:
      type: http
      scheme: bearer
      description: Your LinkedCamp API key as a bearer token.

````

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