Data & Storage · Integration
LiveSession
Add LiveSession to your product for your customers, and give your AI agents governed access to it.
LiveSession is a session replay and product analytics tool, and its API at api.livesession.io/v1 is read-oriented, so the closest catalogue fit is records, datasets and fields rather than an analytics category. Sessions are queried by website ID with filters on visitor attributes, custom properties and event names, and each session returns a URL to the replay rather than the recording itself, so you can link to a replay but not download the frames. Visitors are identified through the client-side identify call, which means a session only carries your user ID if the tracking snippet was told about it before the session ended, and retrofitting identity onto past sessions is not possible. Custom properties are typed at ingestion, and querying a property with the wrong type filter returns nothing rather than an error. Data retention depends on the plan, so historical queries can come back empty for older ranges that still show in your own records. fastn holds each customer's LiveSession token and website scope and maintains the connection as keys change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own LiveSession workspace so replays are reachable from your app
Attach a deep link to the relevant session replay on every bug report or support ticket in your product
Surface which pages and custom events preceded a churn or failed checkout for a given user
Build a per-account view of session counts and rage-click events from your own dashboard
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Let an agent find the sessions matching a reported error and return replay links rather than raw recordings
Have an agent summarise the common steps before a drop-off, with each query audited per tenant
Restrict an agent to sessions for a single website ID so one customer's replays are never read for another
Example prompt
Find the LiveSession replays where users hit the checkout error yesterday.
Set up LiveSession in 4 steps
- 01Enable the LiveSession connector from your fastn dashboard.
- 02Have each customer authorise their own LiveSession account, so calls run under their credentials rather than a shared key.
- 03Decide which records, datasets and fields your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the LiveSession integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a LiveSession integration without building it. Your customers connect their own LiveSession account inside your product and work their records, datasets and fields there, with no per-customer code on your side.
- Handle the part that actually costs time: schemas differ per customer and change without notice, and volumes can be large. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a LiveSession update is not your on-call problem.
- One integration serves your product and your agents. The same governed LiveSession connection powers in-product features and gives AI agents scoped, audited access, so you read and write your customers' data where it already lives without wiring it twice.
Used by these teams
Compare with
Snowflake
Airtable
PostgreSQLOften used alongside
Tools the same teams tend to run next to LiveSession, across other categories.
Anthropic Claude
OpenAI
Azure OpenAI
Hugging FaceLiveSession integration FAQ
How do I add a LiveSession integration to my product?
Enable the LiveSession connector in your fastn dashboard, then let each customer authenticate their own LiveSession account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no LiveSession client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own LiveSession account?
Yes. Every connection is scoped to the individual customer, so each authorises their own LiveSession account and only ever sees their own records, datasets and fields. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this LiveSession integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Let an agent find the sessions matching a reported error and return replay links rather than raw recordings
Who maintains the LiveSession integration?
fastn does. When LiveSession changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the LiveSession integration adapt when a customer's schema changes?
Schema and field mapping is configuration per customer, so a change on their side is a mapping update rather than a code change and a release on yours.
How are large LiveSession reads handled?
Pagination and throttling are handled for you, and initial backfills are rate-limited so a large import does not exhaust a customer's API allowance.
What can I build with the LiveSession integration?
A common starting point: let a customer connect their own LiveSession workspace so replays are reachable from your app. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the LiveSession integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding LiveSession does not change your per-connector cost. You can start free with 3 connected accounts.
Add LiveSession to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.