Problem with permission in Pricing API

Matheus

Hi team,

When I started using the bond pricing API with the request below, I was advised to add "RRPS" to the end of every RIC that did not already have it at the end.

However, in some cases, adding "RRPS" is causing a permission denial, while removing it allows me to retrieve the price successfully. Attached is an example.

Could you please clarify whether adding "RRPS" is still required for all RICs, or if there are specific scenarios where it should or shouldn’t be included? This would help ensure consistent integration and avoid permission issues.

evidences_bonds_price_api.txt

Jirapongse

@Matheus

Thank you for reaching out to us.

I found the How do I differentiate bond suffixes such as =, =R, =RR, and =RRPS? FAQ on MyAccount. If you don't have permission to accss =RRPS RICs, please contact your LSEG account team or Sales team directly to verify the permission.

This forum is dedicated to software developers using LSEG APIs. The moderators on this forum do not have deep expertise in every bit of content available through LSEG products, which is required to answer content questions such as this one.

The best resource for content questions is the Helpdesk support team, which can be reached by submitting queries through MyAccount. The support team will either have the required content expertise ready available or can reach out to relevant content experts to get the answer for you