Hello @m.rodriguesdossantos ,

Consumer primarily consume data and Providers publish data. Posting is a feature of consumer where a consuming application can value-add the consumed data and post it back to system, for other applications to consume. The kind of posting that you are using with Refinitiv contributions channel is called off-stream posting. i.e. a consumer does not consume but rather post data on the login stream.

Please note that we also support RCC contributions using Websocket API which are easier to use, if you prefer. Here is the link to the tutorial. Start with the readymade sample in Python and then you can use any programming language with Websockets.

Hi @m.rodriguesdossantos

Traditionally speaking, contributions often came from the client-side e.g. a desktop-user consuming some data, modifying it and then contributing the data internally or to Refinitiv. Hence, the Posting functionality is included in the Consumer interface.

Providers are used for publishing data for internal use - usually in much larger volumes than contributions.

The above tutorial is probably the best guide - please work through it - assuming you are contributing to our RCC system over the internet and using C++ (if this is not the case please confirm)

In terms of connectivity - you should have received endpoints to connect to in an email from Refinitiv - if not please speak to your internal market data team or Refinitiv Account team.

They would look something like:

TEST: contrib1-emea1.uat.platform.refinitiv.com / contrib2-emea1.uat.platform.refinitiv.com

PROD: contrib1-emea1.platform.refinitiv.com / contrib2-emea1.platform.refinitiv.com

But these may not be the correct ones for your organisation - so please confirm as mentioned above.

The port should be 443 as described in the above tutorial.

You should also have been provided some TEST rics to contribute too as well - if not speak to your Refinitiv account team or internal Market Data team.