Managing subscriptions when using alerts delivery via AWS SQS

kostix
kostix Newcomer
in Refinitiv Data Platform

The reference manual we're using to implement a service to fetch news from RDP via AWS SQS, "News Service on Refinitiv Data Platform - User and Design Guide", v2.0, does not specify in any detail how to manage existing news subscriptions. It contains an example of how to create a new subscription and hints at that such a subscription can later be deleted (cancelled) using the ID returned in the response to a subscription request when/if it succeeds.

Hence we have the following questions:

  • Suppose we have created a subscription via a HTTP POST request to /data/news/v1/news-headlines-subscriptions; how exactly do we delete/cancel this subscription using its ID returned in the response?
  • Having an active subscription, is it possible to modify it? Like, say, updating the filter used for selecting which news to alert about? Or is the filter only applied once, when the subscription is created, and cannot be changed for that particular subscription afterwards?

Another related question is: what is the lifetime of an AWS SQS queue created for a news subscription? Does it exist until the subscription is explicitly deleted/cancelled or are there other cases when a queue may cease to exist?

Tagged:

Best Answer

Answers

  • zoya faberov
    zoya faberov ✭✭✭✭✭

    Hello @kostix,

    You may find helpful, in addition to the suggestions from @nick.zincone , to also review and run example newsAlerts.py that is part of Quickstart and Python tutorials source code, Python starter examples example deck.

  • kostix
    kostix Newcomer

    Hi!

    Both questions were helpful (so I wish to thank both their authors!) but sadly nether of them had provided a complete solution.

    This is mostly due to the fact the API playground consistently fails to work for us (I, for one, am having an endless authenticaton loop each time I try to open any resource there). Or, if we take this tutorial, for example, I simply cannot authenticate there at all: when I proceed with a sign-in, I am redirected to some page with 404 message.

    Anyway, I was expecting a piece of documentation or an updated documentation or something like this; referring to an example of using a Python library is not a substitution for a reference manual (I am Python-literate but we're not using Python for building our service). Hope you understand.

Categories