Logrocket V2

LogRocket records user sessions (DOM mutations, network requests, console logs) and correlates them with error tracking and performance metrics. For agents: query sessions by user ID to retrieve replay links for support escalations, aggregate error occurrence data for prioritization, and export session data for analysis pipelines. The API is primarily used for querying stored session and error data rather than real-time ingestion (that's handled by the JavaScript SDK). Session replay links are valuable in support ticket automation — attach a replay URL to a Jira ticket automatically. Confidence is docs-derived.

REST API at api.logrocket.com/v1. Resources: sessions, errors, users. GET /v1/sessions lists recording sessions (filter by userId, startDate, duration). GET /v1/sessions/{id} retrieves session details (replay URL, user properties, network requests summary). GET /v1/errors lists tracked errors (filter by type, occurrence count, lastSeen). GET /v1/errors/{id} retrieves error details (stack trace, affected session count). GET /v1/users lists tracked users. Session identification in SDK: LogRocket.identify(userId, {name, email, custom_properties}) — links sessions to users for API querying. JavaScript SDK: LogRocket.init('project-id') for browser instrumentation.

API key auth: Authorization: Token {api_key}. Keys from LogRocket Dashboard → Settings → API Keys. Project-scoped. HTTPS enforced. No OAuth2. Session replay URLs: time-limited presigned URLs to recording player. SDK identification: client-side LogRocket.identify() is needed for user-based API filtering. Organization-level and project-level key separation.

Standard HTTP status codes with JSON error bodies. Rate limiting: per-key limits (modest for standard queries). Session availability: sessions are processed after recording (5-15 minute delay before queryable). Error aggregation: errors grouped by stack trace hash — deduplication helps prioritize. Retention: plan-dependent (30 days to 1 year). LogRocket uptime at status.logrocket.com. SDK integration: page load performance impact is minimal (async loading). Session size limits: very long sessions may be split or truncated.

docs.logrocket.com covers JavaScript SDK guide, REST API reference, identify guide, and framework integration docs. Getting started: create LogRocket account (free trial), install SDK (npm install logrocket), init and identify — first sessions recording in under 5 minutes. No mobile SDK needed for web-only apps. REST API useful for extracting session data programmatically. Community via LogRocket support chat and documentation. Documentation quality is solid for the session replay use case.