Route Device Data with the Unified Endpoint

Template scaffold for a core-service getting-started page. This page is intentionally non-production content and defines the expected structure for a Unified Endpoint routing guide.

Prerequisites

• Connected SIM or virtual SIM assigned to a test group
• Group-level service configuration permissions

Step 1: Prepare a test group

Document:

1. Baseline group setup
2. Initial service enablement target
3. SIM assignment expectations

Step 2: Send data to the Unified Endpoint

Include one canonical request example for validation:

curl -X POST http://uni.soracom.io \
  -H "Content-Type: application/json" \
  -d '{"device":"template-device-001","state":"baseline"}'

Step 3: Verify routed delivery

Document:

1. Verification surface in console or destination service
2. Expected payload shape
3. Expected timing and status indicators

Step 4: Change routing without device updates

Document:

1. Secondary route target enablement
2. No firmware change expectation
3. Re-test and compare destination behavior

Why this matters

This template establishes the “single ingress, configurable routing” authoring pattern for onboarding guides.

Next steps

• Data Entry Point
• Direct Cloud Delivery
• Serverless Triggers