Close

Rest Overview

Omniata REST API allows to track user-generated events via HTTP. This API allows for building the custom data visualizations, engaging with users, and track user acquisition. The Event API is the same API that is used in the SDK calls.

Content:

Events

For details on the event resource check out the Custom Events reference.

Method HTTP Request Description
GET https://{orgname}.analyzer.omniata.com/event Stores event data for the organization.

All URIs are relative to the organization name, “{orgname}” is used as example.

Channels

For details on the channel resource check out the Channels reference.

Method HTTP Request Description
GET https://{orgname}.engager.omniata.com/channel Retrieves the channel content for the specified application and user. The content is a JSON structure.

All URIs are relative to the organization name, “{orgname}” is used as example.

User State

For details on the user state specification check out the User State reference.

Method HTTP Request Description
GET https://{orgname}.engager.omniata.com/user Retrieves the user state of the given parameters.

All URIs are relative to the organization name, “{orgname}” is used as example.

Delivery

For details on the push notification an email configuration check out Push Notifications and Email Delivery references.

Method HTTP Request Description
GET https://{orgname}.panel.omniata.com/deliver Delivers the specified content to the specified user. Useful for testing push notifications or email delivery.

All URIs are relative to the organization name, “{orgname}” is used as example.

Content

For details on the content resource check out the Content reference.

Method HTTP Request Description
GET https://{orgname}.panel.omniata.com/data_models/{applicationId}/content.json Lists the available content for the specified application.
POST https://{orgname}.panel.omniata.com/data_models/{applicationId}/ Creates new content in the specified application.
PUT https://{orgname}.panel.omniata.com/data_models/{applicationId}/content/ Updates a content Id with the new version specified.
DELETE https://{orgname}.panel.omniata.com/data_models/{applicationId}/content/ Deletes the content Id specified for the application in the request.

All URIs are relative to the organization name, “{orgname}” is used as example.

Message

For details on the message specification check out the Engagement Messages reference.

Method HTTP Request Description
GET https://{orgname}.panel.omniata.com/data_models/{applicationId}/channels/{channelId}/channel_messages.json Lists and shows the Message Ids associated with each content published in the selected channel.
POST https://{orgname}.panel.omniata.com/data_models/
{applicationId}/channels/{channelId}/channel_messages.json
Publishes messages in the specified Channel Id.
POST https://{orgname}.panel.omniata.com/data_models/{applicationId}/channels/{channelId}/channel_messages/bulk_operation_confirmed.json Allows bulk operations (enable, delete, disable) on channel messages.

All URIs are relative to the organization name, “{orgname}” is used as example.

Attribution

For details on the attribution process specification check out the User Attribution reference.

Method HTTP Request Description
GET https://{orgname}.acquirer.omniata.com/acquirer Stores attribution events for the specified parameters.
GET https://{orgname}.acquirer.omniata.com/event Stores relationship between the user’s application ID and the attribution partner ID.

All URIs are relative to the organization name, “{orgname}” is used as example.

This article was last updated on March 30, 2017 16:23. If you didn't find your answer here, search for another article or contact our support to get in touch.