Acoustic Exchange requires that you define specific attributes for all published events. Acoustic Exchange might appoint more attribute requirements contingent on the event type or on a specific event.

Acoustic Exchange requires that you define the following attributes for all published events, including Acoustic Exchange recognized events and custom events.

• channel Where the event was observed.
• name Name of the type of identifier that is used to identify the individual or entity that initiated the event. For example, emailAddress.
• value The identifier value for the specific event that is being published by the endpoint.
• code The event code that Acoustic Exchange assigned to the event. Acoustic Exchange assigns a unique event code to recognized and custom events.
• Timestamp The date and time when the event was observed. The time must be submitted in ISO-8601 format.

For example, for social event publishers, unique user identifiers such as User ID, User Name (Facebook and Instagram), Twitter Handle, Twitter ID (Twitter), are required attributes that you define as identifiers during endpoint registration and include when you publish events from the endpoint.

The following example illustrates the structure of the JSON payload in the call to v1/event to publish an event.

POST v1/event
{  
  “channel” : “<string>”,

  “identifiers” :  
  [            
    {
    “name” : “<string>”,
    “value” : “<string>” 
    }
  ],

  “events” : 
  [
    { 
    “code” : “<string>”, 
    “timestamp” : “<time

    “attributes” : 
    [
      {
      “name” : “<string>”,            
      “value” : “<string>”,  
      “type” : “<string>” 
      }        
    ]
    }
  ] 
}