Message Routing
If you already use the nRF Cloud Message Routing Service (MRS), no data migration is required. Destinations created in legacy nRF Cloud automatically appear in the new nRF Cloud experience with their existing configuration and state.
Message delivery continues without interruption. You do not need to recreate or reverify a destination simply because you start managing it in the new experience.
What stays the same
The Message Routing Service and your destination configurations do not change:
- Messages continue to be delivered to the same destination URLs.
- Enabled and verification states carry over.
- Data category filters carry over. FOTA and Cloud Messages filters are labeled as legacy because they apply only to messages from the legacy nRF Cloud experience.
- Notification email addresses carry over.
- Tokens, signing secrets, and SSL certificate settings carry over.
- Existing destination IDs remain the same.
What changes for you
The management interface, access model, and some action labels are different:
| Task or setting | Legacy nRF Cloud | New nRF Cloud experience |
|---|---|---|
| Open Message Routing | Device Management → Message Routing Service | Data Ingestion → Message Routing |
| Access | Team Owner or Admin | Organization Admin |
| Project | Team-level configuration | Managed from the organization's default project |
| Add a destination | Add Destination | Create Destination, then Create and Verify |
| Open destination details | Select actions from the destination list | Click the destination name |
| Edit or delete | Actions on the destination list | Actions on the list or destination detail page |
| Verify | Verification action on the destination | Verify in the list or on the destination detail page |
| Test | Test action on the destination | Send test in the list or on the destination detail page |
| Review delivery activity | Destination status and delivery errors | Estimated 24-hour volume and recent forwarding errors on the detail page |
| Manage programmatically | Message Routing Service API | Web app only; no public destination-management API is currently available |
Destinations are shared across the organization, but the Message Routing page is available only from its default project.
Start managing your existing destinations
- Select your organization's default project.
- Open Data Ingestion → Message Routing.
- Confirm that your existing destinations appear in the list.
- Click a destination name to review its configuration and delivery activity.
No save or confirmation action is required. Opening an existing destination does not change its configuration.
If a destination was verified in legacy nRF Cloud, it remains verified. Changing its URL sends a new verification request and pauses delivery until you verify the new URL.
Use existing Message Routing features
Create and verify a destination
Click Create Destination to configure a new endpoint. After you click
Create and Verify, complete verification automatically by echoing the
x-nrfcloud-team-id response header, or enter the six-digit PIN received by
your endpoint.
For the complete procedure, see Creating a destination.
Edit, enable, or disable a destination
Use the pencil icon in the destination list, or open the destination and click Edit. You can change its name, URL, notification emails, data categories, authentication settings, SSL certificate requirement, and enabled state.
Changing a destination URL requires verification of the new endpoint. Other edits do not affect its verification state.
Send a test message
Click Send test in the destination list or on its detail page. Testing works even when a destination is disabled or unverified, so you can confirm that an endpoint responds with a 2XX status before enabling it.
Review destination activity
Click a destination name to open its detail page:
- Estimated Messages Sent (24h) shows delivery volume by data category.
- Recent Forwarding Errors shows up to five recent errors from the last 30 days. Expand an error to inspect the response returned by your endpoint.
For a complete guide to the page and its settings, see Message Routing.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Message Routing is disabled in the menu | You selected a project other than the organization's default | Switch to the default project |
| You cannot open or manage destinations | Your account does not have Organization Admin access | Ask an Organization Admin to update your role |
| An existing destination is missing | You opened a different organization | Return to the organization that owned the destination |
| A destination became unverified | Its URL changed and the new endpoint has not been verified | Open the destination and click Verify |
| A test or verification request fails | The endpoint cannot be reached or does not return a 2XX status | Check the reported cause and your endpoint logs, then try again |
If an existing destination still does not appear, contact support.
Questions or Feedback?
Reach out to us on the DevZone community forum.