Publishing Messages

This topic describes how to publish messages  directly using the Notifications service. You can manually enter the message content or allow a service or app to programmatically define the message content.

Each message is broadcast to all subscriptions  in the specified topic . Every message sent out as email contains a link to unsubscribe from the related topic.

Message delivery rate limits per endpoint: 60 messages per minute for HTTP-based protocols. (HTTP-based protocols use URL endpoints that begin with "http:" or "https:".) 10 messages per minute for Email protocol.


  • IAM policies: To use Notifications, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you get a response that you don’t have permission or are unauthorized, check with your administrator. You may not have the required type of access in the current compartment . For more information on user authorizations, see Authentication and Authorization.
  • Before you can publish a message, you need a topic with at least one subscription. See Managing Topics and Subscriptions.

Creating Automation with Functions and Events

You can create automation by publishing messages to function subscriptions. For an example of a function subscription, see Scenario A: Automatically Resize VMs.

You can create also automation based on state changes of your topics and subscriptions (Notifications resources) by using event types, rules, and actions. For more information, see Overview of Events.

Using the Console

To publish a message
  1. Open the navigation menu and click Developer Services. Under Application Integration, click Notifications.
  2. On the Topics page, for the topic you want, click the Actions menu, and then click Publish Message.
  3. In the Publish Message dialog box, fill in the fields:
    • Message: Enter the content you want to send.


      Message size limit per request: 64KB .
    • Title: Enter the title you want to send.

      Rendering of the title by protocol
      Protocol Rendering of the title
      Email Subject line of the email message.
      HTTPS (Custom URL) Not rendered.
      PagerDuty Title field of the published message.
      Slack Not rendered.
      SMS Not rendered.
  4. Click Publish.

    For troubleshooting information related to published messages, see Message not received.