Skip to content

Legal

Data Export Formats

Last updated: October 7, 2026

This page lists each way to get Your data out of Axiospec, who can do it, and the format You get. It is the list that the section on switching and exporting data in Our Terms and Conditions refers to. Exports are free.

The formats

Every export uses an open, documented format that other software can read:

  • ZIP archives, which hold the other files.
  • JSON (RFC 8259). Dates and times are in ISO 8601. Numbers that were stored as readings are written as text, so no digit is lost.
  • CSV (RFC 4180), in UTF-8 with a byte order mark. Columns are separated by commas. When the app is set to German, Spanish, French or Portuguese, columns are separated by semicolons and readings use a decimal comma, so Excel in those languages opens the file correctly.
  • PDF for reports and calibration certificates.
  • iCalendar (RFC 5545) for calibration due dates.
  • Uploaded files come back in the format You uploaded them in.

Exports You can run yourself

Workspace data

Who: administrators. Where: Settings, then My Profile, then Your personal data, at /account/data. You confirm first with Your password, or with a code We email You if Your account has no password.

What You get: a ZIP with one JSON file for each kind of record the workspace holds. Each file holds every row the workspace owns, including retired and deleted rows, with every field except those listed under "What We do not export" below. The field names are the names used in Our database. A file called manifest.json lists each file with every field in it, and says what is left out and why. A large export comes as a download link that works for 15 minutes.

The ZIP holds these files:

  • tenants.json: the workspace and its settings
  • users.json: users
  • sites.json: sites
  • locations.json: locations
  • user_sites.json: which sites each user can access
  • vendors.json: vendors
  • assets.json: instruments
  • ledger_entries.json: calibration records
  • calibration_compliance_contexts.json: the compliance rules in force when each calibration was approved
  • stored_certificates.json: records of the calibration certificates issued
  • asset_documents.json: records of uploaded documents and photos
  • custody_logs.json: custody entries
  • calibration_plans.json: calibration plans
  • scheduled_calibrations.json: scheduled calibrations
  • uncertainty_budgets.json: uncertainty budgets
  • gage_studies.json: gage studies
  • notification_logs.json: the log of reminders and emails sent
  • compliance_alert_sends.json: the daily compliance alerts sent
  • system_audit_logs.json: the activity log
  • audit_exports.json: the audit archives created
  • import_sessions.json: imports
  • migration_intake_files.json: records of the files You sent Us for migration
  • webhook_endpoints.json: webhook settings
  • webhook_events.json: webhook events
  • webhook_deliveries.json: the log of webhook calls to Your endpoints
  • tenant_sso_configs.json: single sign-on settings
  • data_subject_requests.json: data protection requests

The ZIP has no file contents. It lists each uploaded file, but the file itself is not in it. Certificates, photos and evidence files come in the audit archive below. Other uploaded documents download one by one from each instrument's page. When You switch to another provider, email support@axiospec.com and We send You all of the files.

Use this export, with Your files, when You move to another provider.

Personal data

Who: administrators. Where: /account/data.

What You get: a ZIP with the personal data the workspace holds, as one JSON file and one CSV file for each category. The categories are members, trusted devices, two-factor status, site access, instruments, locations, calibration records, custody, document details, data requests, vendor contacts, scheduled contacts, gage studies, the email log, the admin activity log, workspace settings, and imports and hand-offs. A README.txt file and a manifest.json file describe the contents.

Audit archive

Who: managers, administrators and auditors. Where: the Audit Center in the app.

What You get: a ZIP with a PDF summary report (audit_summary.pdf), a CSV manifest of the calibration records (audit_manifest.csv), a CSV of the calibration points (calibration_points.csv), the calibration certificates as PDF, the instrument and calibration photos and evidence files You uploaded, and a README-verification.txt file. That file explains how to check the record chain without Us.

Instrument list

Who: anyone who can see the instrument list, including read-only auditors. Where: the Instruments page or the dashboard. You can also export only the instruments You select.

What You get: a CSV file with one row for each instrument that matches Your filters, including Your custom fields.

Calibration history of one instrument

Who: anyone who can see the instrument. Where: the instrument's page.

What You get: a CSV file with every calibration record of that instrument. Each certificate can also be downloaded from that page as a PDF.

Calibration due dates

Who: anyone who can see the Due Calendar. Where: the Due Calendar.

What You get: an iCalendar (.ics) file with the due dates, or a calendar feed You can subscribe to so Your calendar stays up to date.

Uploaded documents

Who: anyone who can see the instrument. Where: the instrument's page.

What You get: each file, downloaded on its own, in the format it was uploaded in.

The API

Who: workspaces on the Professional plan or a higher plan, with an API key an administrator creates. Where: the public API, described on Our developer pages.

What You get: instruments, calibration records, sites, due dates, attachments and certificates, as JSON over HTTPS.

What We do not export

These items are left out. Most of them exist only to keep the Service secure.

  • Sign-in and delivery secrets: password hashes, API keys, one-time codes, two-factor secrets and recovery codes, trusted device tokens, push notification tokens, calendar feed and QR code tokens, and the signing secrets of webhooks and single sign-on.
  • Short-lived sign-in state, the links between a user and a Google, Microsoft or single sign-on account, and the token that proves the workspace controls an email domain.
  • Records of the Axiospec partner program, including the sign-up source and referral records in the workspace settings.
  • For activity by Axiospec staff, or with no recorded person, the IP address and the staff member's email address.
  • Copies of recent API responses, kept for 7 days so that a repeated request is not applied twice.
  • Data held outside Our database: server logs, which Our hosting provider keeps for 30 days, and what Stripe and Our email service keep.

Help with switching

If You want to move to another provider, email support@axiospec.com. The section on switching and exporting data in Our Terms and Conditions sets out the notice period, the transition period and when We erase the data.

Translation Interpretation

This page may have been translated if We have made it available to You on our Service. You agree that the original English text shall prevail in the case of a dispute.

There is one exception. For customers in Quebec, the French version of this page governs. It is published in Canadian French at axiospec.com/fr-CA/data-export-formats.