Skip to main content

Getting Started

Cambrionix Connect is our browser based application designed to manage your Cambrionix hubs. It can be accessed across mobile devices, tablets, and computers running macOS, iOS, Windows, and some Linux distributions. To access the application's features, users must first sign in through any web browser at the address below.

https://connect.cambrionix.com

Once signed in, the platform allows you to manage hubs, view connected devices, and access both local and remote systems. With Cambrionix Connect, you can:

  • Monitor hub temperatures, power usage, port status, and error flags
  • Manage firmware updates and switch port modes
  • Run Cambrionix CLI scripts, Python, or JSON commands
  • View and manage all hubs and devices from anywhere with built-in remote access
  • Instantly see the status of offline hubs and devices, including last known state
  • View detailed device information including OS, model, serial, battery health, and usage history
  • Track hub and device presence to monitor activity and detect unauthorised removal
  • Group hubs and devices by use, team, rack, or location using custom hardware groups
  • Add custom fields such as purchase date, lab name, or location for improved fleet organisation
  • Invite multiple users to your organisation and assign roles Cambrionix Connect is available for both new and existing devices with no additional setup or configuration required.

Overview​

Cambrionix Connect provides APIs for managing Cambrionix hardware and services.

Quick Start​

  1. Review the Authentication guide
  2. Explore the API Reference
  3. Check out the Guides for best practices

Next Steps​

Architecture​

Cambrionix Connect is built as a microservices architecture, with each API service handling a specific domain.

API Design Principles​

Our APIs follow RESTful principles:

  • Resource-based URLs: URLs represent resources, not actions
  • HTTP Methods: Use standard HTTP methods (GET, POST, PUT, DELETE, PATCH)
  • JSON: Request and response bodies use JSON format
  • Status Codes: Standard HTTP status codes indicate success or failure
  • Versioning: APIs are versioned to ensure backward compatibility

Common Patterns​

Pagination​

List endpoints support pagination using query parameters.

Filtering​

Many endpoints support filtering.

Sorting​

Sort results using the sort parameter.

Error Responses​

All errors follow a consistent format.