FullStory provides digital experience analytics APIs for managing users, events, sessions, exports, recording settings, privacy rules, and related organization data.
1Open Slashspace and go to Settings, then Connectors.
2On Discover, search for FullStory and click Connect.
3Sign in to FullStory in your browser. Slashspace updates when the account is connected.
Then ask for what you need in any Agent mode chat. FullStory is on in every chat unless you switch it off.
What your chats can do
30 tools from FullStory.
Cancel OperationIrreversibly request cancellation of a cancelable in-progress FullStory operation, currently intended for segment exports. Confirm the operation before calling because a successful cancellation request cannot be undone.
Create AnnotationAdd a persistent annotation to the FullStory timeline for a point or time range. Warning: FullStory provides no matching delete endpoint, so a successful call cannot be cleaned up through this API.
Create Element BlockCreate a beta FullStory element recording or masking rule. Requires an Admin API key. Privacy-critical: an incorrect selector, UNMASK action, or live scope can expose sensitive data, while EXCLUDE or MASK can suppress useful recording. Review every field and prefer preview scope before calling.
Create Extraction RuleCreate and immediately activate one FullStory beta extraction rule using the provider's nested rule, source, and mapping contract. Extraction can capture sensitive element, URL, header, or body values and can materially increase collected data volume. Archiving later only stops future capture; it does not erase data already collected. Review selectors, network filters, mapping targets, property scope, and privacy policy before calling. The beta contract may change without notice. Requires an Architect or Admin API key.
Delete Element BlockPermanently delete a custom FullStory privacy element-block rule. This is irreversible: removing a block or mask can expose sensitive content in future recordings. Confirm the exact custom rule first; built-in rules cannot be deleted. This API is in beta and may change without notice.
Delete User DataPermanently delete a FullStory user and their associated data by FullStory-generated ID. This is an irreversible privacy mutation; confirm the target before calling.
Get FullStory AccountValidate the connected API key and return its FullStory organization, identity, and API-key role. Do not use the role to infer paid product entitlements.
Get Element BlockGet one FullStory privacy element-block rule by ID, including its exact selector source, recording or masking operation, platforms, and editability. Warning: this exposes privacy-sensitive recording configuration. This API is in beta; functionality and documentation are subject to breaking change without notification.
Get Extraction RuleGet one FullStory beta extraction rule by ID, including its archive state and complete nested source and mappings.
Get Import StatusGet status and success/error counts for an asynchronous FullStory event or user import job.
Get OperationGet detailed status, progress, operation-specific results, and failure details for one asynchronous FullStory operation.
Get Organization QuotasReturn current FullStory session and server-event quota usage, limits, and quota periods.
Get Recording SettingsGet one current FullStory recording-settings category. Privacy settings may contain sensitive configuration and large built-in rule sets; the complete provider response is preserved.
Get SegmentGet metadata and the FullStory app URL for one segment.
Get UserRetrieve one user by FullStory-generated user ID, including profile fields and a FullStory app link.
Import EventsStart an asynchronous import of 1 to 50,000 server events. This permanently adds analytics data; use an idempotency key when retrying.
Import UsersStart an asynchronous upsert import of 1 to 50,000 users. This mutates personal profile data.
List DatasetsList beta datasets readable by the connected FullStory organization.
List Element BlocksReturn one page of custom and built-in FullStory privacy element-block rules. These rules determine what FullStory records or masks.
List Extraction RulesList all FullStory beta extraction rules matching one required scope and optional filters, together with current active-rule usage and limits.
List Import RecordsReturn one page of successful or failed records from a FullStory event or user import job, including failure details when requested.
List OperationsReturn one page of asynchronous FullStory operations, optionally filtered by state or type.
List Recording Settings HistoryReturn one page of historical FullStory recording settings for blocking, domain, geo, privacy, features, or targeting. Privacy history requires an Architect-level API key; the other categories require Standard or higher.
List SegmentsReturn one page of FullStory segments, optionally filtered by creator.
List SessionsFind recent FullStory session replay links by application UID, email, or exact session UID. Provide at least one selector; session_uid cannot be combined with uid or email. This is a filtered single-page lookup, not an unfiltered or paginated list; a no-match 404 returns an empty sessions list.
Search UsersFind FullStory users by UID, email, display name, or identification state. Provide at least one of uid, email, display_name, or is_identified. A no-match 404 is returned as an empty result page.
Set Extraction Rule ArchivedArchive a FullStory beta extraction rule to stop future capture, or unarchive it to resume capture. Warning: this changes collection behavior immediately. Archiving does not erase data already collected, and data not captured while the rule is archived cannot be recovered by unarchiving. Confirm the rule ID and intended state before calling. Requires an Architect or Admin API key.
Update Element BlockFully replace an editable beta FullStory element recording or masking rule. Requires an Admin API key. This is an irreversible privacy configuration update, not a patch: read the existing rule first and provide every required replacement field. An incorrect selector, UNMASK action, or live scope can expose sensitive data, while EXCLUDE or MASK can suppress desired recording.
Update Extraction RulePartially update a FullStory beta extraction rule using last-write-wins semantics. Provide at least one of name, description, source, or mappings. Omitted fields remain unchanged; read the current rule first. Warning: changing a rule's source or mappings changes what FullStory captures and may affect privacy, downstream analytics, and data volume.
Upsert UserCreate or update one FullStory user. Supplying fullstory_user_id updates that record; otherwise uid identifies an upsert. This mutates personal profile data.
