A Client can mix in one or more AccessLevels to enable API calls for
read, write, and master operations.
The intention of this approach is to make it a compile-time error to call an
API method requiring a write key if you haven't statically declared that the
client should be a writer, for example.
This also means that runtime checks for presence of optional settings (keys
for access levels you don't need) are pushed up to the time of client
instantiation: if you've forgotten to provide a write key in your deployment
environment, we won't wait to throw a runtime exception at the point that you
make a write call, perhaps long after your app has started and you've gone
home for the weekend.
A Client can mix in one or more
AccessLevels to enable API calls for read, write, and master operations.The intention of this approach is to make it a compile-time error to call an API method requiring a write key if you haven't statically declared that the client should be a writer, for example.
This also means that runtime checks for presence of optional settings (keys for access levels you don't need) are pushed up to the time of client instantiation: if you've forgotten to provide a write key in your deployment environment, we won't wait to throw a runtime exception at the point that you make a write call, perhaps long after your app has started and you've gone home for the weekend.
Client with read and write access:
https://keen.io/docs/security/