The path is encoded as follows:
<eid> is not given, the engine will generate a random EID.
Endpoints raise events to KRE by making an HTTP call to the ESL. The HTTP call may be either a
POST or a
POST is preferred.
If an ESL is encoded this way, and also specified the domain and type in the attributes (i.e. in the body of the POST), the attribute specification will override the path specification.
If you choose to not provide an
<eid> in this form, you can supply
none as the EID to force the engine to generate a unique EID for the event.