Pools & shared bots
List pools, live overview metrics, member directories, and bot performance for clubs your users belong to.
Developers / Integrations
Build on Botso.ai
The Botso.ai API is a REST interface to the platform behind our autonomous trading bots, web dashboard, and native apps — pools, tickets, members, funding, payouts, and audit trails. OAuth2 auth, JSON responses, multi-club tenancy.
What it is
A versioned HTTP API (/api/v1) backed by Laravel Passport. Your app authenticates once, selects a club context, and reads or manages pool data with the same permissions model as the web dashboard.
Tickets & treasury
Assign entitlements, record payments, fund pools, and settle payouts — with a full audit log for compliance.
Same auth & users
Password grant for member apps, client credentials for server integrations — one users table, one permission model.
Who it’s for
Club & syndicate apps
Mobile or web apps for members to view pool PnL, earnings, and ticket status — branded for your organisation.
Ticketing & payment partners
Issue pool tickets after checkout via your payment processor. Same OAuth session as the botso dashboard.
CRM & reporting tools
Pull payout history, audit logs, and member lists into spreadsheets, dashboards, or compliance workflows.
Enterprise IT
Wire Botso.ai into internal portals with service-account credentials and org-scoped API keys.
Agency & integrator builds
Eposy and partner agencies ship custom front-ends on top of the platform without forked infrastructure.
Future mobile apps
Native iOS and Android clients use the same endpoints documented for web — token storage and org switching included in our mobile guide.
Why integrate
- Faster go-live — don’t rebuild pool logic; focus on UX and your payment rail.
- Trust by default — on-chain trade transparency and audit trails ship with every integration.
- Multi-club ready — one user, many organisations; header-based club context built in.
- Permission-aware — member read vs org-admin write enforced server-side, not in your UI alone.
- Partner-friendly docs — reference, howto, mobile, and internal guides maintained alongside the API.
- Payment processor path — upcoming checkout API will use the same auth for ticket purchase flows.
Ready to integrate?
Full endpoint reference, authentication flows, curl examples, and sandbox setup — everything external partners need.
Documentation: https://external.botso.ai/v1/