Deeply API Documentation main logoDeeply API Documentation main logo textDeeply API Documentation main logo text
User GuideServer API Reference
Search...
k
LanguageENKO

© 2026 Deeply Inc.

Deeply Logo Icon

Deeply API Documentation

    Release Notes

    Quick Start

    API Quick Start Guide
    Authorization
    Rate Limit

    Architecture

    Overall Architecture
    Edge Server System

    Events

    Events
    Event Categories
    List Events
    GET
    Get An Event
    GET

    Composite Events

    Composite Events
    List Composite Events
    GET
    Get A Composite Event
    GET
    Listen Live Composite Events
    WebSocket

    Live Events

    Live Events
    Listen Live Events
    WebSocket

    Edges

    Edge Server
    List Edge Servers
    GET
    Get An Edge Server
    GET
    Update Edge Server
    PATCH

    Microphones

    Mic Device
    List Mic Devices
    GET
    Get A Mic Device
    GET
    Update Mic Device
    PATCH

    Auth

    Reissue Token
    GET
    1. Reference
    2. API Quick Start Guide
    3. Rate Limit

    Rate Limit

    Learn about Deeply OpenAPI's rate limiting system, including per-application request quotas, throttling policies, and error handling. Understand how to monitor your API usage, handle rate limit responses, and request quota increases for your production needs. This guide covers best practices for managing API request frequency and avoiding service disruptions.

    Last updated: November 11, 2026

    Overview

    Rate limiting is implemented to ensure fair usage of our API resources and maintain service stability for all users. This document outlines our rate limiting policies and what to do when you reach these limits.

    Rate Limit per API Endpoint

    Each API endpoint is limited to:

    • 10 requests per second
    • 1,000 requests per minute

    These limits are tracked per endpoint and reset automatically each second.

    Requesting Higher Limits

    If you need higher limits for your application, please contact our support for additional quotas.

    Rate Limit Exceeded

    If you exceed the rate limit, you will receive a 429 status code with the following response body:

    1
    2
    3
    4
    5
    6
    7
    8
    {
      "detail": {
        "message": "Rate limit exceeded. Please try again in 60 seconds.",
        "limit": 1000,
        "remaining": 0,
        "reset": 1640995200
      }
    }

    Best Practices for Handling Rate Limits

    To avoid hitting rate limits, we recommend:

    1. Implement Request Queuing: For bulk operations, queue requests and process them at a controlled rate (maximum 10 requests per second).
    Authorization
    Overall Architecture
    OverviewRate Limit per API EndpointRequesting Higher LimitsRate Limit ExceededBest Practices for Handling Rate Limits