API Overview
Thotbot is built from the ground up as an API-first platform. The web application interacts with the exact same distributed worker platform exposed through our public REST endpoints.
The frontend has intentional architectural choices that keep it stateless and scalable across edge locations. For programmatic automation, batch archival, or custom client tools, direct API integration provides optimal throughput and flexibility.
Versioning
All public API endpoints are versioned with a prefix (e.g. /v1/, /v2/) to guarantee stability. Once an endpoint is established in a version tier, its contract will not break unexpectedly. Breaking changes are isolated to new version tiers with migration notices.
Unversioned endpoints are reserved for internal browser hydration and should not be relied upon by external applications.
Rate Limiting
Endpoints are monitored with generous sliding-window rate limits designed to safeguard service availability while accommodating high-throughput usage. If your workload requires elevated quotas, reach out to our team.
Certain upstream provider endpoints impose third-party restrictions outside of our control; our worker proxies automatically manage request queuing to prevent upstream blocks.
Pro Tip: Provide an API key header even when polling unauthenticated informational routes (such as node status). Keyed sessions bypass IP-based rate limiting memory caches, enhancing privacy. See our Privacy Policy for technical details.
OpenAPI Specification
Our complete REST API contract is formalized with OpenAPI 3.0. You can consume or inspect the raw schema directly at:
https://thotbot.cc/openapi/api.yamlImport this specification into tooling such as Bruno, Postman, or Insomnia, or generate SDK client bindings in Go, Python, or TypeScript.
Next Steps
Ready to begin sending authenticated requests? Continue to our authentication guide: