Gleap's documentation is split in two, and knowing which half you're in saves a lot of searching.
This help center: what the product does and how to set it up from the dashboard.
docs.gleap.ai: the SDKs and APIs, with every method, its arguments, and installation per platform.
The rule of thumb: if the answer is a line of code, it's in the developer docs.
Three sections. Documentation holds the SDKs, one set of pages per platform: JavaScript, iOS, Android, React Native, Flutter, FlutterFlow, Ionic / Capacitor, Cordova, plus Windows Desktop, .NET MAUI and Unity in beta. Alongside them are pages on Kai Code and surveys, server-side event tracking and a handful of guides, such as data regions and identity verification.
The API Reference has the REST endpoints, for backends that talk to Gleap directly. The Conversations API is for building your own support UI on top of Gleap conversations from your backend, without the messenger.
Most platforms have the same set, so once you know the JavaScript page names you can find the iOS ones. The recurring ones:
User identity: identifying contacts, and verifying that identity with a user hash.
Track events and Custom data: what a person did, and extra data you attach to their reports.
Console logs and Network logs: the debug data attached to a report.
Callbacks: reacting in your code to what happens in the messenger.
A few pages are web only. Widget control, Replays, Environment and Cookies exist for JavaScript; Privacy controls and Content Security Policy for JavaScript and Ionic / Capacitor. Replays in mobile apps are switched on in the dashboard instead, under Settings → Developer → Developer options.
The fastest route isn't the docs at all: Settings → Widget → Installation in your project has the setup steps per platform, with your API key already in them. Use that to install, and the docs for everything after.
Point your coding agent at https://docs.gleap.ai/llms.txt, an index of every developer docs page written for agents, so it reads the current docs rather than guessing. To let an assistant work with your Gleap data itself, such as tickets, contacts and help center articles, connect the Gleap MCP server.
