https://oss-api.thingpark.com/tpw/7.3/Core-Network/#token-verification-details

According to this documentation, the <query-parameters> for an uplink frame contain a timestamp looking like this: "2022-01-04T10:43:49.185+01:00", whereas in fact the "+" is URL-encoded (%2B) since it's a reserved char, resulting in a different sha256 hash than expected.

The rest of the query-params (including the rest of the timestamp) are not URL-encoded, which seems kind of arbitrary.

I'm aware that the other special-chars (like "-" and ".") aren't reserved by RFC 3986, but it should be at least mentioned/fixed in the docs then.