◾Reverse integration: messaging

The Smartico platform can notify your system whenever it sends an asset (such as an email, SMS, or push notification) to a user via HTTP call.

For example, Smartico can trigger an HTTP request (typically a POST) to your API each time an asset is sent. This enables you to track user communications in real time. Possible Parameters Included in the Request

• Time – Timestamp in epoch milliseconds

• Campaign Name – The name of the campaign that triggered the asset

• Asset Type – Communication channel (e.g., Email, SMS, Push)

• External User ID – The user ID in your system

• View URL – A link to view the content of the sent asset

This setup is handled by the Smartico team based on the information you provide. You’ll need to share:

• HTTP URL of your API endpoint

• Preferred HTTP method – POST is recommended, but GET is also supported

• Content type – "application/json" is suggested

• Body template – For POST requests, a JSON payload structure must be defined

Example of setup

Note: The following is a sample request body. It is fully configurable and can be adapted to match your existing API. In 99% of cases, we can integrate with your current structure without requiring changes on your end.

• URL - https://mysite.com/users/communications

• Method POST

• Content-Type: "application/json"

• Body template

{
  "login": "123123",
  "time": 1664115803000,
  "view_url": "<URL which shows the content of the asset>",
  "channel": "SMS",
  "campaign_name": "RND Flow"
}

If you already have an API that handles similar notifications, in most of the cases we can reuse it with minimal to no modification.

Contact your Success Manager or log a JIRA ticket to set up the reverse integration