The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Cisco does not support the Postman tool, if you have a question about it, please contact the Postman support.
Step 1. In the Postman home page, select Create a request in order to create a new event stream, as shown in the image.
Step 2. Select POST and paste the URL needed to do the query, as shown in the image.
To type your 3rd Party API Client ID and API Key, select Basic Authorization.
Username= 3rd Party API Client ID
Password= API Key
Step 3. In the Body section, select form-data. KEY is filled with “name” word, VALUE is filled with the name of the event stream. Make sure that row is marked.
Step 4. At this point, you can click on the Send button to receive your event stream.
Note: Limit of 5 active resources across each organization
Use this section to confirm that your configuration works properly.
Once the event stream is generated, you can verify it with the command GET https://api.amp.cisco.com/v1/event_streamswhich displays the number of event streams created on the organization, as shown in the image.
In this section, you can find the event stream information as the ID, name and AMP credentials
In order to obtain information about the active event stream you can use GET https://api.amp.cisco.com/v1/event_streams/"id"
There is currently no specific troubleshooting information available for this configuration.