Soracom Harvest

Soracom Harvest collects and stores data sent from IoT devices, providing built-in visualization without requiring external infrastructure. It supports both structured telemetry (Data) and binary files (Files).

What it does

Data Store eliminates the need to set up your own data pipeline during prototyping and early production. Devices send data through the platform, and Data Store stores it with automatic timestamping and device identification.

Key capabilities:

• Zero-config ingestion — Devices send data to a well-known endpoint; no server setup required
• Structured telemetry — Time-series storage for JSON payloads with built-in charting
• Binary file storage — Object storage for images, firmware, logs, and other files
• API access — Query stored data via REST API for integration with external systems
• Retention control — Configure data retention periods per group
• Free tier — First 2,000 requests/day and 5 MB storage included at no cost

How it works

1. Enable Data Store on a device group in the Console
2. Send data from devices using HTTP POST, TCP, or UDP to the platform endpoint
3. View data in the Console's data explorer with time-range filtering
4. Export or query via the API for downstream processing

Structured telemetry

Accepts JSON payloads. Each entry is indexed by device ID, timestamp, and content type. The Console provides line charts, bar charts, and raw data views.

Endpoint: http://uni.soracom.io (from connected devices — no authentication needed, device identity is implicit)

Supported protocols:

• HTTP/HTTPS — POST JSON to the endpoint
• TCP — Send raw JSON to uni.soracom.io:8514
• UDP — Send raw JSON to uni.soracom.io:8514

Binary file storage

Accepts any binary content. Files are stored with metadata (device ID, timestamp, content type, filename). Useful for device logs, images, and firmware artifacts.

Endpoint: http://harvest-files.soracom.io (from connected devices)

Supported operations:

• PUT — Upload a file to a specified path
• GET — Retrieve a previously uploaded file
• DELETE — Remove a file

Common configurations

Basic telemetry collection

1. Create a group in the Console
2. Enable Structured Telemetry in the group settings
3. Assign your devices to the group
4. From a connected device:

curl -X POST http://uni.soracom.io \
  -H "Content-Type: application/json" \
  -d '{"temp": 23.5, "humidity": 60}'

1. View the data in Console under device details or the data explorer

Image capture and upload

1. Enable File Storage on the group
2. From a connected device:

curl -X PUT http://harvest-files.soracom.io/images/photo.jpg \
  -H "Content-Type: image/jpeg" \
  --data-binary @photo.jpg

1. Browse files in Console under File Storage

Querying data via API

Retrieve stored data for external processing:

curl -X GET "https://api.soracom.io/v1/devices/{id}/data?from={timestamp}&to={timestamp}" \
  -H "X-API-Key: {api_key}" \
  -H "X-Token: {token}"

The API returns JSON arrays of timestamped entries, suitable for feeding into analytics pipelines or custom dashboards.

Pricing

Component	Free tier	Paid
Telemetry requests	2,000/day	$0.0044 per request
Telemetry storage	5 MB	$0.22 per MB/month
File storage	5 MB	$0.22 per MB/month

See the Pricing page for current rates by region.

Limits

Resource	Limit
Max payload size (telemetry)	4 KB
Max file size	5 MB
Data retention (default)	731 days
API query rate	10 requests/sec per account
Max entries per API query	1,000

Data format guidelines

Data Store works best with flat or shallow JSON structures:

{
  "temperature": 23.5,
  "humidity": 60,
  "battery_voltage": 3.7,
  "status": "active"
}

The Console charting feature can visualize numeric fields as time-series. String and boolean fields appear in the raw data view but cannot be charted directly.

When to use Data Store vs. external storage

Scenario	Recommendation
Prototyping and validation	Data Store — fastest path to seeing device data
Production dashboards	Data Store + Dashboard Service
Large-scale data pipeline	Forwarding service to your cloud data store
Binary file storage at scale	File Storage for small volumes; forwarding to S3 for production
Real-time stream processing	Cloud delivery to Kinesis or Pub/Sub

What to scale to next

Harvest is often the first data destination. As usage grows, teams commonly scale with:

• Soracom Lagoon — Use when you need richer dashboards, cross-device views, and broader stakeholder reporting.
• Soracom Query — Use when teams want self-serve analytics using natural-language questions over IoT data.
• Direct Cloud Delivery — Use when data volumes, downstream integrations, or retention requirements favor dedicated cloud pipelines.

Related

• Soracom Air — Connectivity for devices sending data
• Quick Start — Connect a device and send your first data
• Platform Overview — Architecture overview
• Pricing — Detailed pricing tables