Product
Orbis IoT Api
Orbis IoT API and backend services.
- 3.3.17Orbis IoT ApiImprovement
A currency was added to the planner's tariff module
A new currency was incorporated into the planner's tariff module. This adjustment expands the available options for tariff calculation or configuration.
- 3.3.16Orbis IoT ApiImprovement
No notable changes
This version does not include enough public information to communicate new features to the end user.
- 3.2.2Orbis IoT ApiImprovement
Improved information returned by linked groups and users
The group query now includes more device data, and the linked users call also returns first and last name. This makes it easier to display more complete information without making additional calls.
- 3.2.1Orbis IoT ApiImprovement
More data in the group response
The endpoint for retrieving all groups now includes version, name, and activity status. This makes it easier to identify each group without relying on additional information.
- 2.2.11Orbis IoT ApiFix
Correction in the permission check for linking a charger
The permission validation when attempting to link a charger was adjusted. This helps avoid blocks or incorrect behavior during the process.
- 3.2.5Orbis IoT ApiImprovement
Orbis IoT Api 3.2.5
- 3.2.4Orbis IoT ApiImprovement
Optimization of the latest version query
The query used to obtain the latest version of a device has been improved. This helps make retrieval of that information more efficient.
- 3.2.6Orbis IoT ApiImprovement
Orbis IoT Api 3.2.6
- 3.2.0Orbis IoT ApiImprovement
Orbis IoT Api 3.2.0
- 3.1.0Orbis IoT ApiImprovement
Orbis IoT Api 3.1.0
- 2.4.4Orbis IoT ApiImprovement
Orbis IoT Api 2.4.4
- 2.4.3Orbis IoT ApiImprovement
Orbis IoT Api 2.4.3
- 2.4.2Orbis IoT ApiImprovement
Orbis IoT Api 2.4.2
- 2.4.1Orbis IoT ApiImprovement
Orbis IoT Api 2.4.1
- 2.4.0Orbis IoT ApiImprovement
Orbis IoT Api 2.4.0
- 3.2.9Orbis IoT ApiImprovement
Orbis IoT Api 3.2.9
- 3.2.8Orbis IoT ApiImprovement
Orbis IoT Api 3.2.8
- 3.2.10Orbis IoT ApiImprovement
Improvement in electricity module processing in multimodules
The processing of the “electricity” module in the multimodules endpoint was corrected so that it is handled properly. This improves response consistency when querying several modules at once.
- 3.2.7Orbis IoT ApiImprovement
Orbis IoT Api 3.2.7
- 2.3.1Orbis IoT ApiImprovement
Orbis IoT Api 2.3.1
- 2.3.0Orbis IoT ApiImprovement
Orbis IoT Api 2.3.0
- 2.2.16Orbis IoT ApiImprovement
Orbis IoT Api 2.2.16
- 2.2.14Orbis IoT ApiImprovement
Orbis IoT Api 2.2.14
- 2.2.12Orbis IoT ApiImprovement
Orbis IoT Api 2.2.12
- 2.2.10Orbis IoT ApiImprovement
Orbis IoT Api 2.2.10
- 2.2.13Orbis IoT ApiFix
Device registration query is fixed for existing serials
The query used when registering a device has been adjusted so it does not fail if the equipment already had an assigned owner previously. With this change, creation works again in those cases.
- 2.2.7Orbis IoT ApiImprovement
Improved login access and response
Permissions were adjusted to query linked users, and the user identifier was added in the login response. This makes validation with the charger owner easier.
- 3.3.0Orbis IoT ApiNew
Favorites in devices and improvements in the listing
Support was added to mark devices as favorites from a new endpoint. In addition, the devices listing now includes additional information about the user's role and whether they have a favorite team assigned.
- 2.2.8Orbis IoT ApiImprovement
User identifier added to the getUser query
The getUser call now includes the user id, making identification in the response easier. This adjustment improves the traceability of the returned information.
- 2.2.9Orbis IoT ApiImprovement
Orbis IoT Api 2.2.9
- 2.2.5Orbis IoT ApiImprovement
Orbis IoT Api 2.2.5
- 3.2.3Orbis IoT ApiImprovement
User subscriptions are added in the email query
The call to retrieve a user by email now also includes their subscriptions. This makes it easier to access all relevant information in a single query.
- 2.2.6Orbis IoT ApiNew
Added user role in app and charger owner in status
The API includes the user's role at app level in the same call and returns the charger owner's identifier in the device status. With this information, apps can more easily decide which menu to show.