DocsAnalytics and reporting
Export Xtrusio Data and Understand Available Integrations
Use the export options available in your account. Confirm separate integration or API requirements with your delivery team.
Availability and responsibility
Use the export options available in your account. Confirm separate integration or API requirements with your delivery team. An export is useful when the recipient understands its fields, scope and limitations. Confirm what is included before using an exported file as a complete record of the account. Customer API access is not a standard feature. Xtrusio's team manages APIs internally; client-facing API access can be provided when required within agreed subscription scope. Internal endpoints are not a generally supported customer API.

Validate an export
- Identify the report or dataset and active filters.
- Use the supported export control.
- Inspect the resulting file's columns or structure.
- Match a small sample to the source records.
- Check dates, identifiers, missing values and URL fields.
- Record the export scope with the file. Export columns and JSON fields depend on the selected dataset and the account's available controls. Treat the downloaded file as the schema for that export, then retain a sanitized sample and field definitions with the receiving workflow.
Example
A catalogue CSV may contain publisher records without article or citation history. Its successful download does not establish that all campaign data can be exported through the same control.
If an integration is requested
Ask which data must move, in which direction, how often, and who may access it. The team can then confirm an existing connector, a supported file workflow or scoped development. Do not invent API endpoints, authentication methods or rate limits. Keep credentials out of export examples. The handoff should include a small sample, field definitions and version or compatibility information where relevant. Custom client-facing API work is documented with the scoped integration rather than presented as a universal public API.
Available output types
Core application outputs include execution CSV, individual execution/question JSON, article Word downloads and clipboard copy, according to permissions. Catalogue CSV, scan logs and campaign-plan utilities include staff-only workflows; do not assume every export is client self-service. Xtrusio Analytics offers dataset exports in TSV, HTML, JSON, XML, CSV and RSS, with image export for reports where available. These outputs are separate from the core application's exports. Confirm the controls for the configured report and role.