Skip to content

Balena ​

Reads balenaCloud: organizations, fleets and devices. Managed IoT devices are counted per customer.

Credentials (gear icon) ​

FieldMeaning
API URLhttps://api.balena-cloud.com
API keybalenaCloud API key (Dashboard → Preferences → Access tokens)

Customer mapping ​

Balena organizations carry no customer name — the mapping is handled by the "Mapping" dialog (the uniform merge-list mechanics): all organizations with device count and current customer, assign/edit/detach with a click, several organizations can point to the same customer. Unmapped organizations with devices are shown as a warning — their devices do not count.

Metrics ​

MetricCount
devicesdevices of all fleets of the mapped organizations

Specifics ​

  • Mappings count as a customer source and are automatically renamed along with merges.
  • Orphaned mappings (organization no longer exists) remain visible in the dialog and can be cleaned up there.
  • A mapping whose organization is no longer in balena's list (deleted there, or the API key lost its membership) cannot be counted. A customer that still has listed organizations is stored with what they count, and the snapshot carries a warning the invoice runs repeat until the mapping is fixed or deleted; a customer without any listed organization is recorded as not read and keeps the device count of its last snapshot.
  • A mapping taken over by display name is anchored to the organization's handle by the next snapshot, so renaming the organization in balena no longer loses it.