You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -233,7 +233,8 @@ try:
233
233
234
234
You can use the `MetricsResponseHandler` object to process your OpenPAYGO Metrics request from start to finish. It accepts the following initial inputs:
235
235
-`metrics_payload` (required): The OpenPAYGO Metrics payload, as a string containing the JSON payload.
236
-
-`secret_key` (optional): The secret key provided as a string containing 32 hexadecimal characters (e.g. `dac86b1a29ab82edc5fbbc41ec9530f6`)
236
+
-`secret_key` (optional): The secret key provided as a string containing 32 hexadecimal characters (e.g. `dac86b1a29ab82edc5fbbc41ec9530f6`). If the secret key is not set later using `set_device_parameters()`, then you will not be able to verify the auth of the request (it will throw an error if you try) and the response will not be signed.
237
+
-`skip_auth`
237
238
-`data_format` (optional): The data format, provided as dictionnary matching the data format object specifications.
238
239
-`last_request_count` (optional): The request count of the last valid request (used for avoiding request replay)
239
240
-`last_request_timestamp` (optional): The timestamp of the last valid request (used for avoiding request replay)
@@ -313,6 +314,10 @@ def device_data():
313
314
314
315
## Changelog
315
316
317
+
### 2023-10-12 - v0.5.2
318
+
- Clarification in the doc of the behaviour when `secret_key` is missing
319
+
- Implemented coherent behaviour when `secret_key` is missing
0 commit comments