DataStream Cloud Access — Customer Guide

Overview

DataStream Cloud Access is a supplementary service to the existing DataStream callback processes.

With standard DataStreams, the platform sends event or usage data directly to the customer’s configured REST API endpoint using callbacks.

With DataStream Cloud Access, the same generated DataStream data is also stored securely in cloud storage for a limited period, allowing customers to retrieve it through APIs when needed.

This is especially useful when a customer’s callback endpoint was temporarily unavailable, when callback delivery failed, or when the customer wants to re-download specific DataStream records.

Pre-release notice: DataStream Cloud Access is currently available as a pre-release service and is still under testing. The official production release is expected to go live within May 2026.

How It Works

The platform generates DataStream data for supported processes such as Usage Events and Mobility Events.

Normally, this data is sent to the customer using the configured DataStream callback process.

With DataStream Cloud Access, the generated data is also stored in secure cloud storage. Customers can then use dedicated APIs to:

List available individual DataStream files.
List hourly zipped archives.
Request a secure download URL for a selected file.

The download URL is time-limited and allows the customer to securely retrieve the selected file.

Standard DataStreams vs DataStream Cloud Access

Capability	Standard DataStream Callback	DataStream Cloud Access
Delivery model	Platform pushes data to customer API	Customer retrieves data using APIs
Main purpose	Near real-time delivery	Recovery, replay, and controlled retrieval
Customer dependency	Customer endpoint must be available	Customer can retrieve data later
Failure handling	Failed callbacks may not be retried	Data can be retrieved from cloud storage
Data format	Callback payload	Individual files or hourly ZIP archives
Availability	Immediate callback delivery	Stored for 7 days

When Customers Should Use It

Customers should use DataStream Cloud Access when:

Their callback endpoint was unavailable.
They missed one or more callback messages.
They want to recover Usage or Mobility data for a specific date.
They need to download all files generated during a specific hour.
They want an additional resilience layer on top of callback delivery.

This service should not be seen as a replacement for DataStream callbacks. It is an additional recovery and access mechanism.

Available File Formats

DataStream Cloud Access stores data in two formats.

Individual DataStream Files

Individual files represent specific DataStream records.

Customers should use these when they need to retrieve one or a few specific records for a given date and DataStream process.

Hourly Zipped Archives

Hourly archives contain multiple DataStream files generated within the same hour.

Customers should use these when they need to recover a larger volume of data, for example after their callback endpoint was offline for a period of time.

Available APIs

1. DataStream File List

Use this API to retrieve the list of individual DataStream files available for a given date and process.

Typical use case:

“I want to see which individual files were generated for my Usage or Mobility DataStream on a specific date.”

2. DataStream Hourly File List

Use this API to retrieve the list of hourly zipped archives available for a given date and process.

Typical use case:

“My callback endpoint was down between 10:00 and 12:00, and I want to recover all files generated during that period.”

3. DataStream File Download

Use this API after identifying the file or ZIP archive to download.

The API returns a pre-signed, time-limited URL that allows the customer to securely download the selected file.

Typical use case:

“I found the file I need and now I want to download it securely.”

Recommended Customer Workflow

Scenario 1 — Recover one or a few missed records

Call DataStream File List for the required date and DataStream process.
Identify the required individual file.
Call DataStream File Download using the file identifier.
Download the file using the returned secure URL.

Scenario 2 — Recover data after callback endpoint downtime

Identify the date and approximate time window of the outage.
Call DataStream Hourly File List for the required date and process.
Identify the hourly ZIP archives covering the downtime period.
Call DataStream File Download for each required ZIP archive.
Download and unzip the archives.

Security and Retention

All DataStream files are stored in secure cloud storage.

Download URLs are pre-signed and time-limited. Anyone with access to the URL may be able to download the file while the URL is valid, so customers should treat these URLs as sensitive.

Files are available for 7 days from the time they are generated. After this period, they are automatically removed.

Important Notes

DataStream Cloud Access currently supports Usage and Mobility DataStream data only.
It is supplementary to the existing DataStream callback mechanism.
It does not replace the customer’s configured callback endpoint.
Customers should continue to process callback data as their primary near-real-time delivery method.
Customers should use DataStream Cloud Access for recovery, replay, or controlled retrieval scenarios.

Beta usage notice: DataStream Cloud Access is currently available as a beta service. During the beta period, customers may request file download links multiple times without a defined usage limit. In the future, limits may be introduced on how many files can be requested and how often download links can be generated.

Summary

DataStream callbacks provide near-real-time data delivery to the customer’s endpoint.

DataStream Cloud Access provides a secure retrieval layer on top of this, allowing customers to access stored Usage and Mobility DataStream files when needed.

Together, they provide a more reliable and flexible way for customers to receive and recover their