To publish an individual event, make a POST call to the v1/event API. Specify a channel, one or more identifiers, and describe the event.
Publish events individually when you expect interactions with your business solution to occur in relatively low volumes and at random times. The mobile application installation event (application/installed) is an example of an event that happens occasionally and randomly. Individuals register your mobile app one at a time, and they can do so at any time.
You might also consider sending events individually if the event is time critical and any delay to accumulate multiple events might cause a problem. For example, it is likely that you want to publish opt-out requests as soon as possible. To publish an event individually, build the JSON payload in the POST request that defines the channel, an array of identifiers, and a single event description.
The diagram illustrates the general structure of the JSON payload that is required to publish individual events.
Acoustic Exchange originally introduced event publication as individual events as the only way to publish events. Although the v1/event API now supports sending events in a batch, event publishers do not need to change their existing implementation of v1/event. The v1/event API is fully compatible with existing implementations for sending individual events.
- Call POST <base URL>/v1/event.
See POST /v1/event for call details, including an example of how to build the JSON payload.