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).
For a thorough tutorial of the use of the Sky Event API with the Pico Engine read the Events and Queries Lesson.
The event schema includes the following components:
- channel identifier (
<eci>) - a token that is used by the system to identify the entity and channel for whom the event is being raised.
- event domain - the namespace for any given event
- event type - the individual events within the namespace. The word name is often used interchangably with type in this documentation and elsewhere.
- attributes - any given event may include attributes that further define the event
- event ID (
<eid>) - a unique identifier assigned by the event generator for correlation purposes. The event generator is free to make the
<eid> any value so long as it is URL encoded.
Event Signal URL (ESL)
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.