...

Universal Controller supports the following RESTful-based web service for Universal Events.

• Universal Event Web Services#Universal Publish Universal Event
• Push Universal Event 

Formatting specifications for the web service, including details about parameter requirements, are provided.

Anchor
Universal Event Publishing Universal Event Publishing

Publish Universal Event 

The Universal Event Publishing web service is allowed only for users with the ops_admin role.

...

...

...

Anchor
Universal Event Publishing Examples Universal Event Publishing Examples

...

Publish Universal Event

...

: XML and JSON Examples

Universal Event Publishing: Example Request

<?xml version="1.0" encoding="UTF-8" ?>
<universalEvent>
  <name>ExampleEvent</name>
  <businessServices>
    <businessService>BusinessServiceName1</businessService>
    <businessService>BusinessServiceName2</businessService>
  </businessServices>
  <ttl>60</ttl>
  <attributes>
    <attribute>
      <name>example_attribute1</name>
      <value>Value1</value>
    </attribute>
    <attribute>
      <name>example_attribute2</name>
      <value>Value2</value>
    </attribute>
  </attributes>
</universalEvent>

{
   "name": "ExampleEvent",
   "businessServices": [
      "BusinessServiceName1",
      "BusinessServiceName2"
    ],
    "ttl": 60,
    "attributes": [
       {
          "name": "example_attribute1",
          "value": "Value1"
       },
       {
          "name": "example_attribute2",
          "value": "Value2"
       }
    ]
}

Push Universal Event 

The push endpoint provides an Inbound Webhook endpoint for third party Webhook integration with Universal Events.

• The request body is captured as the payload attribute.

• ttl and businessService (multi-value) query parameters specify the Universal Event TTL and Member of Business Services, respectively.

• All other query parameters are captured as attributes with the exception of an access_tokenquery parameter.

  • Any character in a query parameter name that is not a letter or digit is converted to an underscore (_).

• All headers are captured as attributes with the exception of authorization and connection.

  • Any character in a header name that is not a letter or digit is converted to an underscore (_).