Send In-App Message

This endpoint can only be used with your Server credentials and allows you to send in-app messages directly to one or more customers.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…

Please note that using personalization attributes in messages sent via the OptiMobile API is not currently supported


📘

Using Templates and Push Notifications with the In-App Message API

When using the In-App Message API, you can specify a templateId to utilize a predefined in-app message template. If you want to send a push notification (also known as a tickle) alongside the in-app message to notify the user, you have two options:

  1. Activate "Send Push Notification" in the In-App Message Editor:
    • When creating your template, enable this option to define default tickle settings within the template.
  2. Include a notification Object in Your API Request:
    • Add a notification object to your request to define the tickle's push notification details or to override the template's default tickle settings.
Key Points:
  • notification Object: Represents the tickle's push notification. By including it in your API request, you can customize the tickle's title, message, and other notification details.
  • Fallback Behavior: If you do not provide a notification object but the template includes default tickle settings, the system will use those default settings.
  • Personalization Tags: If your template contains personalization tags but no user attributes are provided in the API request, the personalization tags will fall back to default or empty values, depending on how the template was set up.

Rate Limit

This endpoint is subject to the general API rate limit of 50 requests per 10 seconds. Learn more about handling rate limits.

Body Params
target
object
required
int32
required
Defaults to 1
json
Defaults to {"tag":"content"}

Object of dynamic content tags keyed by their respective title, required if template contains dynamic tags

string
enum
required
Defaults to next-open

Immediately: If the message syncs during the users current session it will display immediately. Next Open: Once synced the message will be displayed at the start of the user's next session. Never: The message will not be shown unless the user explicitly opens it from the inbox or push notification (if configured).

Allowed:
json
Defaults to {"key": "value"}

Optional object of additional key:values to be passed in the message payload for your app to consume

notification
object
schedule
object
inbox
object
json

Object keyed by customerID of meta-data for each recipient

json

Object of arbitrary meta-data about this notification

ttl
object
Responses

Language
Credentials
Basic
base64
:
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json