10Duke Event API allows you to collect event data from 10Duke Enterprise, for example, for business intelligence or audit purposes.
If needed, you can also store your own events over the Event API. You could, for example, track end user logins and the use of your client applications.
By default, an event is stored in 10Duke Enterprise for 90 days. If you want to extend the storage time, consider the effect on the storage size needed.
Data schema of events
The data schema of events stored by 10Duke Enterprise is available in the 10Duke GitHub repository.
10Duke Enterprise may write some additional fields in events, for example, if your deployment uses custom extensions.
The API reference is available in this documentation.
The way you authorize requests to the Event API depends on the type of request:
For reading events, you create a JSON Web Token (JWT).
For storing events, you create a JSON Web Signature (JWS) that contains the event data in the payload.
For more information on JWT and JWS, see jwt.io and RFC 7515.
10Duke Enterprise must have the public key corresponding to the private key that you use to sign the JWT tokens and the JWS. Contact the 10Duke Integration Support team about the key exchange.