Six live integrations, wired in both directions. Game and league data flows in, your CRM and your Discord stay in step, and a public REST API covers whatever we have not built yet.
6 live integrations4 game & league sources1 public REST API
Every connection writes into or reads out of the same org record. Nothing here is a second copy waiting to drift from the first.
Ranks, ELO, match history and tournament fixtures, on a schedule.
Closed-won deals arrive with their company and contacts attached.
Player and prospect writes over the public API, on an org-scoped key.
One permission model over all of it — so a scout, a coach and a commercial lead read the same numbers.
Reminders, RSVPs and roster changes, in the channel they already read.
Delivery progress written back onto the originating deal.
Signatures, consent requests and reminders, sent and logged.
A public REST API over everything above, read with the same key.
Ranks, match history and fixtures pulled on a schedule, mapped to the players and teams already on your roster.
League of Legends and Valorant ranks, match history and player stats, refreshed into Scout and Tactical.
Scout · TacticalCS2 ELO, match data and player history — plus a player-side OAuth link, so a prospect can prove the account is theirs.
Scout · IdentityPublic profile data, game ownership and playtime, used to confirm a prospect is who the tryout form says they are.
Scout · IdentityTournament, team and match data across the major titles, feeding the league calendar and the scout pipeline.
League · ScoutEnkelt does not ask the commercial side to move into a new tool, or the players to check one more. It meets both where they are.
Two-way sponsorship sync. A deal that reaches your won stage arrives as a sponsor and a draft contract; fulfilment and renewals go back the other way.
Sponsorships · CommercialThe Enkelt bot posts match reminders, RSVP prompts, roster changes and VOD sessions into the channels your team already reads.
Schedule · NotificationsNothing to connect here — these are ours, not yours. Billing and delivery run on the same vendors you would have picked, and they are named because you are entitled to know who touches your data.
Subscription billing for every plan — hosted checkout, the customer portal, and signature-verified webhook events.
BillingTransactional email delivery for match reminders, contract signatures, consent requests and team notifications.
NotificationsSponsorship is the one place an esports org already has a system of record — and the one place that record usually stops. Connect the pipeline once and a won deal keeps going, instead of becoming somebody's manual re-entry job.
Fulfilment syncs back
Every team, player, prospect, contract and fixture is reachable over a public REST API, authenticated with an org-scoped key and rate-limited per key. Structured JSON in, structured JSON out.
/roster?teamId=tm_5f3aThe active roster for a team, with role and status.
/playersCreate or sync a player profile from your own system.
/schedule?startDate=…&endDate=…Fixtures inside a date window, across every team.
/contracts/expiring?days=30Contracts approaching their end date.
Keys are issued per org, scoped to that org's data, and revocable from settings. Every call is logged.
Inbound webhooks are signature-verified and replay-protected before a single record is touched.
curl https://enkelt.ai/api/public/v1/roster?teamId=tm_5f3a
-H "Authorization: Bearer $ENKELT_KEY"
{
"success": true,
"data": [
{ "ign": "Kekmek", "role": "mid", "status": "active" },
…
],
"meta": { "count": 5, "responseTime": "38ms" }
}Read the API reference, or email partners@enkelt.ai with the use case.