The current version of the N2N-DL APIs is 3.
The previous production ready version is version 2 and this guide highlights the main differences between the 2 versions and how to migrate to version 3 painlessly.
The main differences between N2N-DL V2 and V3 are as follows
In N2N-DL V3 the main data entity is called
ParserReadings if a built in decoder OR a custom decoder is provided
N2N-DL V3 Core APIs support custom decoders on top of built in ones.
The main reading data structure (
ParserReading) is consistent across V2 and V3.
Migration from V2 to V3 requires the following changes:
Readings APIs, Push APIs and Network APIs have been replaced by 1 single API: Core V3.
The Core APIs V3 support direct device enrolment and unenrolment and multiple network servers
Devices, API keys, Users, Enterprise and Groups are automatically synchronised from V2 every 10 minutes.
Therefore there is no need to migrate any of these entities manually
Old readings and network metadata stored in the Readings APIs v2 and the Network APIs v2 are not automatically transferred because of a format mismatch.