{
  "aid": "dyte.io:main-v2",
  "name": "Dyte REST APIs",
  "type": "Index",
  "description": "## Rate Limiting\n\nRate limits specify the maximum number of requests (GET, POST, PUT, or DELETE) a user can make in a given time period. When you exceed a rate limit, the API request fails and returns the HTTP 429 status code. The HTTP 429 status code indicates that the user made too many requests in a given period of time (\"rate limiting\").\n\nWe apply rate limits at the IP address level.\n\n### Rate Limit by IP Address\n\nThe rate limit threshold is set at 2000 calls per minute per IP address. After 2000 calls, a 429 status code is sent, and access to any of our APIs is denied. \n\nNote: Rate limit is applied at the domain level, which means that all APIs are included in the threshold.\n\n| Number of Requests | Resources | Time Window | Status Code Returned when Threshold Exceeds |\n|--|--|--|--|\n| 2000 | Per IP | Per minute | HTTP 429 |\n\n### Sample\n\nThe following sample shows the API response for the status code 429.\n\n```http\nHTTP/1.1 429 Too Many Requests\nretry-after: 4\nx-envoy-ratelimited: true\ndate: Tue, 06 Sep 2022 08:32:55 GMT\nserver: envoy\n```\n\n### Why Do You Set a Rate Limit?\n\nRate limiting is required to prevent the network from becoming overloaded as a result of numerous requests. This could be due to hacking activity, overuse of the Dyte APIs by a bot, or a bug in the code. Setting a rate limit helps to prevent this type of API overuse.\n\nSetting a rate limit also protects us from various types of attacks, such as:\n- [Brute Force Attack](https://www.fortinet.com/resources/cyberglossary/brute-force-attack)\n- [DDOS attack](https://aws.amazon.com/shield/ddos-attack-protection/)\n- [Web-scraping](https://www.geeksforgeeks.org/what-is-web-scraping-and-how-to-use-it/)",
  "url": "https://raw.githubusercontent.com/jentic/jentic-public-apis/refs/heads/main/apis/openapi/dyte.io/main/v2/apis.json",
  "tags": [
    "dyte.io",
    "main"
  ],
  "created": "2026-03-29",
  "modified": "2026-03-29",
  "specificationVersion": "0.19",
  "access": "3rd-Party",
  "maintainers": [
    {
      "FN": "Jentic",
      "X-github": "jentic",
      "url": "https://github.com/jentic"
    }
  ],
  "apis": [
    {
      "aid": "dyte.io:main-v2",
      "name": "Dyte REST APIs",
      "description": "## Rate Limiting\n\nRate limits specify the maximum number of requests (GET, POST, PUT, or DELETE) a user can make in a given time period. When you exceed a rate limit, the API request fails and returns the HTTP 429 status code. The HTTP 429 status code indicates that the user made too many requests in a given period of time (\"rate limiting\").\n\nWe apply rate limits at the IP address level.\n\n### Rate Limit by IP Address\n\nThe rate limit threshold is set at 2000 calls per minute per IP address. After 2000 calls, a 429 status code is sent, and access to any of our APIs is denied. \n\nNote: Rate limit is applied at the domain level, which means that all APIs are included in the threshold.\n\n| Number of Requests | Resources | Time Window | Status Code Returned when Threshold Exceeds |\n|--|--|--|--|\n| 2000 | Per IP | Per minute | HTTP 429 |\n\n### Sample\n\nThe following sample shows the API response for the status code 429.\n\n```http\nHTTP/1.1 429 Too Many Requests\nretry-after: 4\nx-envoy-ratelimited: true\ndate: Tue, 06 Sep 2022 08:32:55 GMT\nserver: envoy\n```\n\n### Why Do You Set a Rate Limit?\n\nRate limiting is required to prevent the network from becoming overloaded as a result of numerous requests. This could be due to hacking activity, overuse of the Dyte APIs by a bot, or a bug in the code. Setting a rate limit helps to prevent this type of API overuse.\n\nSetting a rate limit also protects us from various types of attacks, such as:\n- [Brute Force Attack](https://www.fortinet.com/resources/cyberglossary/brute-force-attack)\n- [DDOS attack](https://aws.amazon.com/shield/ddos-attack-protection/)\n- [Web-scraping](https://www.geeksforgeeks.org/what-is-web-scraping-and-how-to-use-it/)",
      "image": "",
      "baseURL": "https://api.dyte.io/v2",
      "humanURL": "https://docs.dyte.io",
      "version": "v2",
      "tags": [
        "dyte.io",
        "main"
      ],
      "properties": [
        {
          "type": "OpenAPI",
          "name": "OpenAPI definition",
          "url": "https://raw.githubusercontent.com/jentic/jentic-public-apis/refs/heads/main/apis/openapi/dyte.io/main/v2/openapi.json",
          "mediaType": "application/openapi+json"
        },
        {
          "type": "GitHubRepo",
          "url": "https://github.com/jentic/jentic-public-apis/tree/main/apis/openapi/dyte.io/main/v2"
        }
      ],
      "contact": [
        {
          "FN": "API Support"
        }
      ]
    }
  ]
}