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

# Get team performance summary

> 
> **Alpha API** - This endpoint is in active development. Schema may change without notice.

Retrieve aggregated performance metrics for your team over a rolling period.

**Includes:**
- Overall scores, close rates, and show rates
- Verdict distribution (hire/retain/replace)
- Weakest and strongest call journey stages
- Top loss reasons (objection categories)
- Per-closer performance breakdown

**Use Cases:**
- Commission dashboards showing team leaderboard
- Manager views with per-rep performance
- Trend analysis across time periods
  

> **Alpha API** - This endpoint is in active development. Schema may change without notice.

Retrieve aggregated performance metrics for your team over a rolling period.

**Includes:**

* Overall scores, close rates, and show rates
* Verdict distribution (hire/retain/replace)
* Weakest and strongest call journey stages
* Top loss reasons (objection categories)
* Per-closer performance breakdown

**Use Cases:**

* Commission dashboards showing team leaderboard
* Manager views with per-rep performance
* Trend analysis across time periods


## OpenAPI

````yaml openapi.json GET /v1/team/performance
openapi: 3.1.0
info:
  contact:
    email: support@aura-app.ai
    name: Aura Support
  description: >-
    # Aura Partner Integrations API


    > **Alpha Release** - This API is under active development. Endpoints,
    request/response schemas, and behaviors may change without prior notice. We
    recommend pinning to specific response fields you need and handling unknown
    fields gracefully.


    Enterprise REST API for external partner integrations including

    commission platforms, external mobile apps, and client booking widgets.


    ## MCP Connector


    Aura also exposes a **Model Context Protocol** server at `/mcp` so AI

    assistants (Claude, ChatGPT) can answer questions about a user's own sales
    data.

    If you are building an assistant integration rather than a server-to-server
    one,

    that is almost certainly the surface you want — it is task-shaped ("prep me
    for

    my next call") rather than resource-shaped, and it handles auth per-user.


    Read-only. OAuth 2.1 + PKCE, with Clerk as the authorization server;
    discover it

    from `/.well-known/oauth-protected-resource`. Setup guide:

    https://docs.api.aura-app.ai/mcp-connector


    ## Authentication


    Authenticated endpoints support two authentication methods:


    **1. API Key (for partners and integrations):**

    ```

    Authorization: Bearer aura_pk_live_xxxxxxxxxxxxxxxx

    ```

    Get your API key from the Aura dashboard at Settings > API Keys.


    **2. Clerk JWT (for mobile and web apps):**

    ```

    Authorization: Bearer <clerk_jwt_token>

    ```

    Use Clerk's authentication SDK to obtain a JWT token with org claims.


    ## Rate Limiting


    - **Per API Key:** 100 requests/minute

    - **Per Organization:** 1000 requests/minute


    Rate limit headers are included in all responses:

    - `X-RateLimit-Limit`: Maximum requests allowed

    - `X-RateLimit-Remaining`: Remaining requests in current window

    - `X-RateLimit-Reset`: Unix timestamp when limit resets


    These counters are held per serving instance, so under concurrency the

    effective ceiling is higher than the number above and the headers describe
    one

    instance's view rather than a global total. Treat a 429 as backpressure to
    obey

    and pace your client to the documented rate — but do not rely on us to
    reject

    your 101st request, and do not derive a global remaining-quota figure from
    the

    headers. The limit may become globally enforced without notice, so a client

    that stays within it will not be affected when that happens.


    ## Pagination


    List endpoints support cursor-based pagination:

    - `limit`: Number of results per page (default: 50, max: 100)

    - `cursor`: Opaque cursor for next page


    ## Error Handling


    All errors follow a standard format:


    ```json

    {
      "success": false,
      "error": "Error message",
      "code": "ERROR_CODE"
    }

    ```


    Common HTTP status codes:

    - **400** Bad Request - Invalid input (`VALIDATION_ERROR`)

    - **401** Unauthorized - Missing or invalid API key (`AUTHENTICATION_ERROR`)

    - **402** Payment Required - The key is valid, but the organization's
    subscription is not active (`PAYMENT_REQUIRED`). Every authenticated
    endpoint can return this. Retrying will not help until the account's payment
    method is updated in Aura; surface it to the account owner rather than
    treating it as an auth failure.

    - **403** Forbidden - Insufficient permissions (`AUTHORIZATION_ERROR`)

    - **404** Not Found - Resource not found (`NOT_FOUND`)

    - **409** Conflict - Resource state prevents the operation (`CONFLICT`)

    - **413** Payload Too Large - Request body exceeds 256KB
    (`PAYLOAD_TOO_LARGE`)

    - **429** Too Many Requests - Rate limit exceeded (`RATE_LIMIT_EXCEEDED`)

    - **500** Internal Server Error - Server error (`INTERNAL_ERROR`)


    ## Webhooks


    Subscribe to real-time events using the Webhooks API. All webhook payloads

    are signed with HMAC-SHA256 for security verification.


    Delivery is at-least-once. Every payload carries an `idempotency_key` that

    is stable across retries of the same event, so you can enforce exactly-once

    with a `(subscription_id, idempotency_key)` unique constraint on your side.


    For full documentation, visit
    [docs.aura-app.ai/api](https://docs.aura-app.ai/api)
  license:
    name: Proprietary
  title: Aura Partner Integrations API
  version: 1.0.0-alpha
servers:
  - description: Production
    url: https://api.aura-app.ai
  - description: Staging
    url: https://staging-api.aura-app.ai
  - description: Local Development
    url: http://localhost:3001
security:
  - bearerAuth: []
tags:
  - description: Lead management operations
    name: Leads
  - description: Call booking and management
    name: Calls
  - description: Booking link configuration (read-only)
    name: Booking Links
  - description: Product catalog (read-only)
    name: Products
  - description: Payment tracking (read-only)
    name: Payments
  - description: Public booking creation
    name: Bookings
  - description: Real-time event subscriptions and webhook management
    name: Webhooks
  - description: >-
      Team member information for commission attribution. **Alpha** - schema may
      change without notice.
    name: Team (Alpha)
  - description: >-
      Dashboard analytics, lead source attribution, and objection analysis.
      **Alpha** - schema may change without notice.
    name: Analytics (Alpha)
  - description: System endpoints (health checks)
    name: System
paths:
  /v1/team/performance:
    get:
      tags:
        - Team (Alpha)
      summary: Get team performance summary
      description: >-

        > **Alpha API** - This endpoint is in active development. Schema may
        change without notice.


        Retrieve aggregated performance metrics for your team over a rolling
        period.


        **Includes:**

        - Overall scores, close rates, and show rates

        - Verdict distribution (hire/retain/replace)

        - Weakest and strongest call journey stages

        - Top loss reasons (objection categories)

        - Per-closer performance breakdown


        **Use Cases:**

        - Commission dashboards showing team leaderboard

        - Manager views with per-rep performance

        - Trend analysis across time periods
          
      parameters:
        - description: 'Rolling window in days (1-365, default: 90)'
          in: query
          name: days
          required: false
          schema:
            default: '90'
            description: 'Rolling window in days (1-365, default: 90)'
            example: '90'
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TeamPerformanceSuccessResponse'
          description: Successfully retrieved team performance
        '400':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MiddlewareErrorResponse'
          description: Request validation failed
          headers:
            X-Request-Id:
              description: Request identifier for support
              schema:
                type: string
        '401':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Invalid or missing API key
        '402':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MiddlewareErrorResponse'
          description: The organization's subscription is not active
          headers:
            X-Request-Id:
              description: Request identifier for support
              schema:
                type: string
        '403':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MiddlewareErrorResponse'
          description: The API key does not have the required scope
          headers:
            X-Request-Id:
              description: Request identifier for support
              schema:
                type: string
        '408':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MiddlewareErrorResponse'
          description: >-
            The request exceeded its processing time limit. Check the outcome
            before retrying a write
          headers:
            X-Request-Id:
              description: Request identifier for support
              schema:
                type: string
        '413':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MiddlewareErrorResponse'
          description: The request body exceeds 256KB
          headers:
            X-Request-Id:
              description: Request identifier for support
              schema:
                type: string
        '429':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: Rate limit exceeded
        '500':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/MiddlewareErrorResponse'
          description: >-
            Unexpected server failure. Include the request identifier when
            contacting support
          headers:
            X-Request-Id:
              description: Request identifier for support
              schema:
                type: string
      security:
        - bearerAuth: []
components:
  schemas:
    TeamPerformanceSuccessResponse:
      properties:
        data:
          $ref: '#/components/schemas/TeamPerformance'
        success:
          enum:
            - true
          type: boolean
      required:
        - success
        - data
      type: object
    MiddlewareErrorResponse:
      properties:
        code:
          type: string
        error:
          type: string
        requestId:
          type: string
        success:
          enum:
            - false
          type: boolean
      required:
        - success
        - error
        - code
      type: object
    ErrorResponse:
      properties:
        code:
          description: Error code for programmatic handling
          example: NOT_FOUND
          type: string
        error:
          description: Human-readable error message
          example: Lead not found
          type: string
        requestId:
          description: Request ID for support debugging
          example: req_abc123
          type: string
        success:
          enum:
            - false
          type: boolean
      required:
        - success
        - error
        - code
      type: object
    TeamPerformance:
      nullable: true
      properties:
        avg_overall_score:
          description: Average AI overall score (0-100)
          example: 75.2
          nullable: true
          type: number
        close_rate:
          description: >-
            Close rate as percentage (0-100), computed as closed/(closed+lost).
            Null when no closed/lost calls in the period.
          example: 32
          nullable: true
          type: number
        coverage:
          $ref: '#/components/schemas/TeamCoverage'
        per_closer:
          description: Per-closer performance breakdown
          items:
            $ref: '#/components/schemas/CloserPerformance'
          type: array
        period_days:
          description: Number of days in the rolling window
          example: 90
          type: number
        show_rate:
          description: >-
            Show rate as percentage (0-100). Currently always null in the
            rolling-window response (placeholder for future use).
          example: null
          nullable: true
          type: number
        strongest_stage:
          description: Strongest call journey stage
          example: discovery
          nullable: true
          type: string
        top_loss_reasons:
          description: Top objections leading to lost deals
          items:
            $ref: '#/components/schemas/LossReason'
          type: array
        total_calls:
          description: >-
            Calls with an AI analysis in the period — NOT all calls. See
            coverage for the full denominator.
          example: 5
          type: number
        verdict_distribution:
          additionalProperties:
            type: number
          description: 'AI verdict distribution (e.g., {hire: 5, retain: 3})'
          nullable: true
          type: object
        weakest_stage:
          description: Weakest call journey stage
          example: closing
          nullable: true
          type: string
      required:
        - period_days
        - total_calls
        - coverage
        - avg_overall_score
        - close_rate
        - show_rate
        - verdict_distribution
        - weakest_stage
        - strongest_stage
        - top_loss_reasons
        - per_closer
      type: object
    TeamCoverage:
      description: >-
        How much of the team and period every figure here describes. Read it
        before quoting any rate.
      properties:
        analysed_calls:
          description: Calls with a comprehensive AI analysis in the window.
          example: 5
          type: number
        booking_calls_in_window:
          description: >-
            All booking calls in the window. The denominator: every rate in this
            response covers analysed_calls out of this.
          example: 136
          type: number
        closers_analysed:
          description: Closers with at least one analysed call.
          example: 2
          type: number
        closers_with_calls:
          description: >-
            Closers with any booking call. per_closer has one row per closer
            here, including those with no analysed calls.
          example: 17
          type: number
      required:
        - analysed_calls
        - booking_calls_in_window
        - closers_analysed
        - closers_with_calls
      type: object
    CloserPerformance:
      properties:
        avg_overall_score:
          description: Average AI overall score (0-100)
          example: 78.5
          nullable: true
          type: number
        booking_calls:
          description: >-
            All booking calls for this closer in the window — what they did, as
            opposed to call_count, which is what we measured. Present even when
            call_count is 0: a closer with no analysed calls is absent from the
            sample, not from the team.
          example: 100
          type: number
        call_count:
          description: Number of calls
          example: 25
          type: number
        close_rate:
          description: >-
            Close rate as percentage (0-100), computed as closed/(closed+lost).
            Null when this closer has neither.
          example: 35
          nullable: true
          type: number
        closer_id:
          description: Closer user ID
          example: user_2abc123xyz
          type: string
        closer_name:
          description: Closer name
          example: John Smith
          nullable: true
          type: string
        revenue:
          description: >-
            Revenue in dollars (numeric, two-decimal precision). NOT cents.
            Always null here: this response is computed from call analyses and
            does not join sales. It previously reported 0, which read as 'this
            rep earned nothing' rather than 'not measured here'. Use
            /v1/analytics/dashboard for measured per-rep revenue.
          example: null
          nullable: true
          type: number
        show_rate:
          description: >-
            Show rate as percentage (0-100). Always null here: a show rate needs
            the calls that were never analysed, and this response is computed
            over analysed calls only. Use /v1/analytics/dashboard for a measured
            show rate.
          example: null
          nullable: true
          type: number
      required:
        - closer_id
        - closer_name
        - call_count
        - avg_overall_score
        - close_rate
        - booking_calls
        - show_rate
        - revenue
      type: object
    LossReason:
      properties:
        count:
          description: Number of occurrences
          example: 5
          type: number
        objection:
          description: Objection category
          example: price
          type: string
      required:
        - objection
        - count
      type: object

````

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