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

# Get Sender Quotas

> Inspect sender status and daily message, connection-request, and like capacity.

Requires `senders:read`. Each quota includes `limit`, `used`, `remaining`, and `resetAt`. Reset timestamps follow the sender's reset timezone rather than a single global UTC midnight.

Check status and quotas before planning outreach. A snapshot of remaining capacity is not a reservation; execution rechecks sender eligibility and limits.


## OpenAPI

````yaml GET /v1/senders/quotas
openapi: 3.0.0
info:
  title: SendPilot External API
  description: >

    # SendPilot External API v1


    Public API for integrating with SendPilot programmatically.


    ## Authentication


    Requests authenticate with a workspace API key in the `X-API-Key` header:


    ```

    X-API-Key: sp_live_your_api_key_here

    ```


    `Authorization: Bearer sp_live_...` (or `sp_test_...`) is also accepted.
    Prefer one header; `X-API-Key` takes precedence. Clerk OAuth tokens for MCP
    connection URLs are not public REST API keys.


    A key only reaches what its scopes and creator's current workspace
    permissions allow. Each operation lists the scopes it needs in
    `x-sp-scopes`. Use `GET /v1/me` to inspect the effective permissions and
    subscription state.


    ## Rate Limits


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

    - **Per Workspace**: 50,000 requests/day


    Responses that reach the rate limiter include these headers; early
    authentication failures may not:

    - `X-RateLimit-Limit`: Max requests per minute

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

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


    ## LinkedIn Sender Limits


    When using messaging endpoints, these headers show account limits:

    - `X-LinkedIn-Messages-Remaining`: Messages left today

    - `X-LinkedIn-Connections-Remaining`: Connection requests left today

    - `X-LinkedIn-Quota-Reset-At`: When daily limits reset


    ## Retries


    Send an `Idempotency-Key` header on POST and PATCH requests. A retry with
    the same key within 24 hours returns the first result (with
    `Idempotent-Replayed: true`) instead of acting twice. The same key with a
    different request answers 422 `IDEMPOTENCY_KEY_REUSED`; a retry while the
    first request still runs answers 409 `IDEMPOTENCY_IN_PROGRESS`.


    Once execution is attempted, its response (including errors) is retained. If
    a process stops or result storage fails after the attempt, the durable
    record blocks another execution for the replay window and returns 409
    `IDEMPOTENCY_IN_PROGRESS` or `IDEMPOTENCY_REPLAY_UNAVAILABLE`. Check the
    operation's status before using a new key: an uncertain outcome may already
    have acted. Requests refused before execution is claimed, such as
    authentication or rate-limit refusals, can be retried with the same key.


    ## Webhooks


    Configure webhooks in the SendPilot app to receive real-time events:

    - `lead.tag.updated`

    - `lead.updated`

    - `message.sent`

    - `reply.received`

    - `connection_request.sent`

    - `connection_request.accepted`

    - `campaign.started`

    - `campaign.paused`

    - `campaign.resumed`

    - `campaign.finished`


    ## Error Codes


    Errors return a JSON body. Use the machine-readable `code` when supplied;
    validation messages can be arrays, and some legacy errors omit `code`. A
    typical error is:

    ```json

    {
      "statusCode": 400,
      "error": "Bad Request",
      "code": "SPECIFIC_ERROR_CODE",
      "message": "Human-readable description"
    }

    ```
  version: '1.0'
  contact:
    name: SendPilot Support
    url: https://sendpilot.ai
    email: support@sendpilot.ai
servers:
  - url: https://api.sendpilot.ai
security: []
tags: []
paths:
  /v1/senders/quotas:
    get:
      tags:
        - External API - Senders
      summary: Get daily LinkedIn quotas per sender
      description: >-
        Every sender in the workspace with today's connection, message and like
        limits, what is used and remaining, and when each resets.
      operationId: senders.quotas
      parameters: []
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SenderQuotasResponseDto'
        '401':
          description: Invalid or missing API key
        '403':
          description: Key lacks senders:read
      security:
        - api-key: []
components:
  schemas:
    SenderQuotasResponseDto:
      type: object
      properties:
        senders:
          type: array
          items:
            $ref: '#/components/schemas/SenderQuotasDto'
        total:
          type: number
          example: 2
      required:
        - senders
        - total
    SenderQuotasDto:
      type: object
      properties:
        senderId:
          type: string
          example: sender_123
        name:
          type: string
          example: Jane Doe
        linkedinUrl:
          type: string
          example: https://www.linkedin.com/in/janedoe/
        status:
          type: string
          description: Sender status
          example: active
        isPremium:
          type: boolean
        timezone:
          type: string
          example: UTC
        connections:
          $ref: '#/components/schemas/SenderQuotaDto'
        messages:
          $ref: '#/components/schemas/SenderQuotaDto'
        likes:
          $ref: '#/components/schemas/SenderQuotaDto'
      required:
        - senderId
        - name
        - linkedinUrl
        - status
        - isPremium
        - timezone
        - connections
        - messages
        - likes
    SenderQuotaDto:
      type: object
      properties:
        limit:
          type: number
          example: 25
        used:
          type: number
          example: 7
        remaining:
          type: number
          example: 18
        resetAt:
          type: string
          description: 'Next reset: midnight in the sender''s reset timezone'
          example: '2026-09-26T00:00:00.000Z'
      required:
        - limit
        - used
        - remaining
        - resetAt
  securitySchemes:
    api-key:
      type: apiKey
      in: header
      name: X-API-Key
      description: 'API key for authentication (prefix: sp_live_ or sp_test_)'

````