@NishaRana - Are you talking about responding from the Pega Customer Service application, or from a different application? CSRs using Pega CS can respond to tweets from the CS Interaction Portal. Public Twitter APIs are used by this portal to send responses to Twitter (either public tweets or private DMs). I don't know which specific API calls are used, and it really shouldn't matter, since it's handled seamlessly by the CS application. (The set-up for these responses, including entering the appropriate Twitter tokens for authorization, are explained in the Customer Service Implementation Guide.)
I don't know how to guide you, however, if you're talking about posting to Twitter from Pega separately from the Customer Service application.
My understanding is that, based on recent changes in the Twitter APIs, there are currently issues with the Twitter data set in the Pega platform, which is impacting the harvesting of tweets. Are you currently able to harvest Twitter content? If so, what platform version are you using?
Yes, I am talking about posting to Twitter from Pega separately from the Customer Service application.
I can confirm that I am able to fetch tweets into my application using twitter api by executing a GET method in a connect Rest. However when I try to post to twitter using the POST method API, I am getting an exception - "220- Your credentials do not allow access to this resource" and "403-the HTTP response code of 403 indicated a client error. The response data may contain a reason". Can you guide me for this?
@NishaRana - I'm a product manager for the Customer Service application, so that's the Pega application I'm most familiar with, particularly regarding social channels. I'll try to find an engineer who has more familiarity with the APIs. Twitter APIs are definitely a moving target, and they have made a variety of changes in recent months and are shoring up security and authorization of their apps.
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query.
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s at the top of this screen and also on our Pega Support Community homepage. Once created, please reply back here with the URL of the new post.
We have also sent you a private message opening up a communication channel in case you have any further questions.
Posted: 2 years ago
Posted: 29 Apr 2019 4:38 EDT
Abhinav Gupta (Abhinav7)
Principal Technical Solutions Engineer