nRF Cloud REST API Billing & Usage limits

Hi,

we are building a backend that pulls device messages from nRF Cloud via the REST API instead of using the Message Routing Service. Before we finalize the polling logic, we want to make sure we understand the billing correctly.

Questions

  1. The pricing page lists "$0.00005 / message routed" and "$0.0001 / message stored". Do messages returned by ListMessages count as "messages routed", or towards any other billable or limited usage metric (e.g. the 3,000 messages/month of the Developer plan)? Or is "routed" billed only for deliveries by the Message Routing Service? Are REST API requests themselves metered or rate limited?

  2. With the transition to nRF Cloud powered by Memfault, will GET /v1/messages remain available long-term, or should new integrations use a different API?

Thanks in advance!

Best regards, 
Florian

Related