If after reading the documentation you want to try the Subscription API, we have prepared a\ndemo environment that anyone can access. Authentication is required, but any token\nthat you pass should work, so no need to get a User or Application key in advance.
\nTo show how this environment works, we will use Postman, but you can use any other REST client.
\nThe URL where this API can be located is: https://16abf815-424c-413e-b92d-6c6f8fc633cd.remockly.com/intelligence/api. Keep in mind that\nfor real production environments, the URL typically ends with /intelligence/api and not /api.
Let's start this Tutorial by creating a new HTTP Request in Postman (File > New > HTTP Request). Make sure that you have\nselected a GET operation and paste the URL for the API next to it: https://16abf815-424c-413e-b92d-6c6f8fc633cd.remockly.com/intelligence/api.
\nAuthorization and select Bearer Token for the Type. For the token, paste the above key.
Now we should be ready to start getting some information such as the full list of Knowledge Models. For that,\nyou need to add '/knowledge-models' at the end of the URL. As we can see, there is one Knowledge Model with the id\nopen-purchase-requisition.purchase-requisition-km and named Purchase Requisition KM. As we can tell by the name, this\nKnowledge Model is giving us information about Purchases that happened in the company.
Once you know the id of the trigger you want to use to create a subscription, you can create a new subscription just adding the\ntrigger id abc-123-bad-123 to the previous URL. Ensure also the URL is requesting a new subscription appending subscriptions to the end of the URI.
Do not forget to give a name to the subscription, and a valid callback URI, and the system will return to you the id for that new\nsubscription.
\nOnce you created the subscription, you can get all the subscriptions in the system, it is useful for example to check the status of your\nsubscriptions, just in case any of them is failing, or it is paused or suspended.
\nAlso, the id of the subscription is something important to know, since that information is required for updating, pausing, resuming, unsubscribing and\nthe manual fetching of the data.
If you have the id of a subscription, you can perform an update to change its name or its callback URI. Just ensure you append the id abc-123-bad-123\nto the subscriptions URI, and define a valid name and a valid callback URI.
If you have the id of a subscription, you can pause it to stop receiving events. Just ensure you append the id abc-123-bad-123\nto the subscriptions URI, and also append to the command pause at the end
If you have the id of a paused subscription, you can resume it to start receiving events. Just ensure you append the id abc-123-bad-123\nto the subscriptions URI, and also append to the command resume at the end
In case of a failing subscription, it is possible to get the unsent events manually.
\nJust ensure that you have the id abc-123-bad-123 of the failing subscription, and include the events path to the subscriptions URI.