kibot

Historical Data API

Pull tick, minute, and daily bars directly from Kibot's servers. No FTP, no scheduled Agent runs. The API is for Premium subscribers; guest access covers daily data so you can validate your integration first.

API overview Client examples
Spec
  • 8reference clients
  • 5concurrent connections
  • 20 minsession idle
  • gzipon request
  • RESTover HTTPS

API map

Every endpoint the API exposes, grouped by purpose. Each card links to the concept article with request/response shape, examples, and error handling notes.

01 Getting started

Overview

API model & base URL

Request shape, supported response formats, subscription tiers, and guest access rules.

 Overview

How to get access

Enabling API access on your Kibot account, whitelisting your IP, and choosing a subscription plan.

02 Authentication & session

Session

Login & session tokens

How to authenticate, reuse the session cookie across requests, and handle the 20-minute idle timeout.

 Session

Logout

Explicitly end a session. Recommended for scripts that finish a batch, frees one of your concurrent slots immediately.

03 Data endpoints

GET

history

Bar data for any date range at tick, 1-minute, 5-minute, 60-minute, or daily resolution.

 GET

snapshot

Current-day data for up to 100 symbols in a single request. Requires a Premium subscription.

 GET

adjustments

Splits and dividends with an incremental-update pattern, you never have to re-fetch the full history.

 GET

status

Server health and session status probe. Cheap to call, safe to poll.

04 Responses & transport

Reference

Server responses

HTTP status codes: 200 OK, 400 parameter, 401 auth, 402 subscription, 403 forbidden, 404 symbol, 405 method.

 Reference

Compression

Gzip response negotiation. Opt in with Accept-Encoding: gzip; decoded automatically by most HTTP libs.

05 Clients & samples

Samples

Reference clients

Working examples in curl, Python, Rust, Go, TypeScript/Node, R, C++, and C#/.NET. Login, history, gzip, error handling.

 Samples

Kibot API Client (.NET)

Official reference implementation bundled with C# and VB.NET source. Good base for Windows-hosted pipelines.

 Samples

VB.NET and C# snippets

The canonical login + history download flow in VB.NET and C#, with the modern HttpClient port for .NET 6+.

Limits & rules to know before you build

5

Concurrent connections

Per subscription, shared across API, FTP, and Kibot Agent. Plan your pool size accordingly.

1

IP address per subscription

The API is pinned to the IP you register. Rotating hosts needs a support ticket.

20 min

Idle session timeout

"Works once, fails later" is almost always this. Renew the session on 401 and retry transparently.

100

Symbols per snapshot

Single snapshot call can return current-day data for up to 100 tickers. Batch larger requests.

Next step

  1. Read the API overview end-to-end.
  2. Pick a reference client in your language.
  3. Try a daily-data request as a guest to verify network, auth, and response handling.
  4. Add a subscription on the Buy Data page to unlock tick and snapshot endpoints.
  5. Wire retry-on-401 + session renewal before moving anything to production.