The Sky Event API is used to raise events to the pico engine. Because the Sky API has the concept of unique entity identity built into the API, each event raised using the Sky API is raised on behalf of a particular entity. This concept enables personal event networks. The Sky API follows the Evented API specification. The API implements event signal URLs (ESLs).
The event schema includes the following components:
<eci>) - a token that is used by the system to identify the entity and channel for whom the event is being raised.
<eid>) - a unique number assigned by the endpoint raising events to the event for correlation purposes. The endpoint is free to make the
<eid>any value so long as it is URL encoded.
The components of the event are encoded in an event signal URL as follows:
The schema is either
https. The HTTP call may be either a
POST or a
POST is preferred.
The path is encoded as follows:
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.