Overview#
A government statistician needs monthly transaction data delivered to a national financial intelligence unit in a specific XML schema, on a fixed schedule, with an encrypted transfer and a delivery receipt for audit purposes. Setting that up as a manual process creates operational risk every month. The Export API makes it a configured pipeline: format, schedule, destination, encryption, and retry logic are defined once, and the delivery happens without manual intervention until something needs changing.
The same API handles everything from a one-off CSV extract for an analyst to a high-volume nightly sync feeding an external data warehouse. Format support covers the full range needed in regulated environments: PDF/A-3 for archival, XML and JSON for regulatory submission schemas, Excel for working analysts, and Parquet for analytics platforms.
Key Features#
- Multi-format export covering PDF/A-3, JSON, CSV, XML, Parquet, Excel, and additional data interchange formats suited to regulatory and intelligence workflows
- High-throughput processing with efficient streaming and batch modes for datasets of any size
- Real-time webhook integration delivering event-driven data to external systems with low latency
- Scheduled export automation with cron-based scheduling and timezone-aware execution for international reporting obligations
- Streaming exports for large datasets, enabling progressive delivery without memory constraints on either side of the transfer
- Compression and encryption options at the job level, with configurable algorithms and key management for classified or sensitive transfers
- Format conversion and data transformation during export, including field mapping and type casting for destination-specific schemas
- Multiple delivery destinations: cloud storage, SFTP, HTTP endpoints, and email
- Export job management with progress monitoring, status tracking, pause and resume, and resumable operations after transient failures
- Automatic retry with exponential backoff for resilient delivery to external systems
- Export templates for repeatable data extraction patterns, reducing configuration overhead for recurring submission types
- Complete audit trail of all export operations with user context and data lineage for compliance and forensic review
- Multi-tenant isolation ensuring organisational export data separation
Use Cases#
- Regulatory Data Submission: Compliance teams export structured compliance data in required formats for automated submission to regulatory authorities, with delivery receipts logged to the audit trail
- Data Warehouse Synchronisation: Organisations schedule periodic exports to maintain synchronised copies of investigation and analytics data in external warehouses for long-term analysis
- Partner Data Sharing: Intelligence teams share investigation results with partner organisations through secure, encrypted export deliveries scoped to the Community of Interest channel
- Business Intelligence Integration: Analysts export processed data in analytics-friendly formats for consumption by external BI and reporting platforms, without manual data preparation
Integration#
- Connects with data sources through typed API interfaces for flexible data extraction
- Compatible with major cloud storage providers for automated export delivery
- Supports webhook-based event notification for downstream processing automation
- Role-based access controls governing export permissions by user, format, and destination
- Complete audit logging of all export jobs with data lineage tracking
- Multi-tenant isolation ensuring organisational export data separation
Open Standards#
- ISO 19005 (PDF/A, parts 1-4): Archival-grade PDF exports are rendered as PDF/A-1B, PDF/A-2B, PDF/A-3B, or PDF/A-4F conformant documents depending on the target court or regulatory regime, ensuring long-term reproducibility and embeddable attached files.
- OASIS Common Alerting Protocol (CAP) v1.2: Incident and alert data can be exported as fully conformant CAP 1.2 XML documents, using the OASIS namespace
urn:oasis:names:tc:emergency:cap:1.2, for delivery to emergency management and regulatory systems. - NIEM 6.0 (National Information Exchange Model): Structured incident exports targeting justice or emergency-management recipients are produced as NIEM 6.0 JSON-LD payloads, covering NIEM Core, Justice (JXDM 7.2), and Emergency Management domain namespaces.
- OASIS STIX 2.1: Alert data destined for cyber-threat intelligence sharing can be exported as STIX 2.1 Bundles containing Indicator and Report objects, interoperable with any TAXII-capable platform.
- RFC 3161 (Internet PKI Time-Stamp Protocol): Export manifests and PDF/A packages optionally carry an RFC 3161 timestamp authority receipt that cryptographically binds the document digest to a trusted clock, satisfying evidentiary integrity requirements.
- RFC 5652 / PKCS#7 CMS (Cryptographic Message Syntax): Detached digital signatures over export manifests are produced as CMS/PKCS#7 DER objects, providing non-repudiation for classified or court-admissible deliveries.
- EDRM (Electronic Discovery Reference Model) XML: A legacy-compatible EDRM 1.2 XML export path is available for legal discovery workflows that require documents packaged to the EDRM load-file schema.
- ISO/IEC 27037:2012: The Bates-numbering and chain-of-custody services comply with ISO/IEC 27037 guidelines for the identification, collection, and preservation of digital evidence, alongside US Federal Rules of Evidence 901 and FRCP 34.
Last Reviewed: 2026-02-05 Last Updated: 2026-04-14