This repository contains all the information you need to integrate OpenPAYGO Metrics into your device or PAYGO software.
This open-source project was fully funded and developped by Solaris Offgrid, the developers of PaygOps™ and is free to use by all.
A Python implementation is available, implementing OpenPAYGO Metrics as well as OpenPAYGO Token for use either on server side or on device side.
An Arduino library for the device side is currently being worked on. More information will be posted here once a working version is available. If you would like to contribute or sponsor this project, or if you would like to be added to the registry of current user, open an issue in the issue tracker to let us know.
OpenPAYGO Metrics provide a standardized way for PAYGO devices to send usage metrics to a server and get back information about their activation status in a low cost and secure way. The specification is designed so that the payload is very lightweight while additional information about the data format can be provided to allow servers to display and process the data with a lot of details. It is currently in active use by multiple software providers and manufacturers.
To get started implementing, check out that document that describes the detailed specification of the OpenPAYGO Metrics payload and API.
- Added "Recursive Data Auth" as a memory efficient authentication option
- Added clarification about data formatting for auth signature generation
- Properly specified code block type for examples
- Add link to OpenPAYGO Python library for handling metrics
- Improved the "Variable Type" object structure documentation
- Added information about the aggregation of temporal data
- Added details about asynchronous flow
- Documentation coherence improvements
- Added definition of the security schemes
- Added clarifications about the request and responses flow
- Migrated the documentation to Markdown
- Added clarifications about the order of tokens in the response
- First version published on Github
- Clarified the headers needed for JSON and CBOR content