Search the documentation...

Search the documentation...

Start

Sharing data

Sharing data

Submitting data to Onesurance

Onesurance supports a variety of data delivery and exchange methods, so we can flexibly connect to your organization. Our clear preference is for structural, automated links, but we always offer an appropriate solution for your situation.

All methods feature strict security, logging and data validation. During onboarding, we agree together on what fits best.

One-time versus structural

A one-time upload (e.g., for a pilot) is possible, but we recommend working with periodic, structural data delivery as much as possible.

Data delivery options (from most to least common)

  1. Direct database linkage

    • Customer shall provide a secure, read-only database connection.

    • Onesurance retrieves the required data (periodically or on demand) through this connection.

    • Maximum automation and minimum manual operations.

    • Recommended for large volumes or frequent updates.

  2. File drop on Azure Storage

    • The client periodically provides structured files (CSV, Parquet).

    • Uploading is done to a protected storage container in Microsoft Azure.

    • Onesurance processes the files directly through an ingest pipeline.

    • Suitable for users with limited integration capabilities.

    • File exchange is as follows:

      • Use Microsoft Azure Storage Explorer or SFTP for a secure transfer.

      • You will receive a temporary SAS URL by email to access the upload location.

      • See our separate guide "Sharing Data via Azure Storage Explorer" for a detailed step-by-step instruction of the steps below:

        • Download Azure Storage Explorer from the official site.

        • Install and start the program.

        • Pair with the SAS URL you received.

        • Choose 'Upload', select the file and confirm.

        • After upload, the transfer is immediately visible in the storage.

  3. REST API

    • The client provides a REST API that Onesurance can access.

    • Suitable for partners who already provide data access through services.

  4. Alternatives

    • In consultation, alternatives are possible, such as a (temporary) SFTP connection or transfer via Microsoft Teams (for small data sets).

    • Such methods are mainly for pilots, incidents or exceptions.

Security and compliance

  • All data connections are secure (TLS/SSL, encryption at rest and on the go).

  • Access is restricted to the period or datasets needed ("least privilege").

  • Logging records every exchange, including timestamp and user.

  • Data is stored and processed only in the agreed region (standard within the EU).

  • Any credentials or SAS links are never shared with third parties.

Practical: what is required for successful onboarding?

  • Alignment on required data and formats(See: Required data)

  • Formal processor agreement signed

  • Privacy and requirements check

  • Test upload and validation of the structure

  • Documentation on security policy and contact during exchange

Overview of data delivery steps

  1. Agreement on purpose, dates and timeline

  2. Alignment on method (link, file drop or API)

  3. Receipt and establishment of credentials/SAS link

  4. Upload or link data (see manual)

  5. Validation by Onesurance

  6. Feedback and adjustment as needed

  7. Structural design and monitoring

Questions or specific needs?
Your Customer Success Manager will advise on the best method and guide the entire data submission process. For questions, always refer to the detailed explanation of data sharing or contact us directly.