Inbound destinations

You manage inbound destinations from the Inbound Destinations subtab under the Destinations tab.

An inbound destination is an ActiveMQ connection between the platform and the app. The connection uses API key accounts for read and write access. The inbound destination is primarily used with the QRadar plug-in.

To add an inbound destination, click Create Inbound Destination. To view, edit or delete a destination, click the destination name in the table. You can also delete an inbound destination from the table by clicking the menu icon.

Each inbound destination has the following properties.
  • Display Name. Name of the inbound destination. Use a name that describes the purpose of the message destination.
  • API Name. Generated by the system and based on the Name field. App developers use this programmatic name in their external scripts to connect to the destination. It is displayed for informational purposes.
  • Write API Keys (optional). If the app needs to write messages to the inbound destination, select one or more existing API key accounts.
  • Read API Keys (optional). If the app needs to read messages from the inbound destination, select one or more existing API key accounts.

If the app using the inbound destination has an existing API key account, you can use that account for the read API key, write API key or both. You can use more than one key when multiple apps access the same inbound destination.