BotsArchive API

Beginner's Pick Open Data / No Auth Required Beginner HTTPS
Free to Use Varies (check documentation)

Overview

BotsArchive provides a public database of Telegram bots with details returned in JSON format. No authentication is needed, so you can start exploring bot listings immediately. It is useful for building Telegram bot directories or discovering bots for a specific purpose.

Beginner Tip

No API key is required — just make a GET request to the endpoint to receive bot details as JSON. Use the category or keyword parameters to filter results.

Available Data

BotsArchive data via REST API

Example Response

JSON Response
{
  "status": "success",
  "data": {
    "result": "Data from BotsArchive",
    "description": "JSON formatted details about Telegram Bots available in database",
    "timestamp": "2025-01-15T10:00:00Z"
  }
}

Field Reference

id Unique identifier of the Telegram bot entry.
name Display name of the Telegram bot.
username Telegram @username of the bot.
description Short description of what the bot does.
category Category the bot belongs to, such as Games or Utilities.

Implementation Example

Request
const url = "https://botsarchive.com/";
const response = await fetch(url);
if (!response.ok) throw new Error(`Request failed: ${response.status}`);
const data = await response.json();
console.log(data);

What Can You Build?

Note: These code examples are AI-generated and unverified. Always refer to the official API documentation for accurate usage.

Common Errors & Troubleshooting

404 Not Found The bot ID or endpoint path you requested does not exist in the archive.
Check the documentation at botsarchive.com/docs.html to confirm the correct endpoint and available IDs.
Empty or null response body The archive may not have data for the queried bot or category.
Try a different search term or browse the site to verify the bot is listed.
JSON parse error Response is not valid JSON, possibly due to a server-side error.
Check the HTTP status code first; if 5xx, wait and retry after a short delay.

Metadata Score Breakdown

Estimated from metadata — endpoint not independently tested

This score is estimated from observable metadata — HTTPS support, authentication model, declared CORS, and documentation reachability — because the API requires authentication or exposes no publicly testable endpoint. The five-signal breakdown is only shown for live-tested APIs.

Metadata estimate · endpoint not independently tested

Technical Specifications

Auth No Auth
HTTPS REQUIRED
CORS UNKNOWN
Category Open Data
Difficulty Beginner
Verified: 2026-04-04

Related Tags

Similar APIs

View All →