sharing_message_token is missing from response body
According to the API documentation, sharing_message_token is returned for publish actions. And then we can use sharing_message_token to request analytics snapshots.
We have built our integration around this, and it has been working very well (including fetching the snapshots).
In the last couple of days the responses have STOPPED including the sharing_message_token element.
Is this a bug, or an undocumented change. And if it is a change, how are we to fetch analytics on published content.
We have a high-profile event launching tomorrow so it is urgent to us to solve this problem.
We have built our integration around this, and it has been working very well (including fetching the snapshots).
In the last couple of days the responses have STOPPED including the sharing_message_token element.
Is this a bug, or an undocumented change. And if it is a change, how are we to fetch analytics on published content.
We have a high-profile event launching tomorrow so it is urgent to us to solve this problem.
Best Answer
-
Claude_SchlesserAdministratorOneAll Team
You are using the following endpoint:
http://docs.oneall.com/api/resources/users/write-to-users-wall/
Results from this endpoint are not supposed to be used with our Analytics API.
You need to use the following endpoint:
http://docs.oneall.com/api/resources/social-sharing/publish-new-message/
Don't worry the JSON to send is almost identical.
Switching to the new endpoint should only take a few minutes.
Welcome!
Please sign in to your OneAll account to ask a new question or to contribute to the discussions.
Please click on the link below to connect to the forum with your OneAll account.
Information
Products & Services
Categories
- 2.2K All Categories
- 1.1K General
- 1.1K Questions
- 46 Suggestions
- 592 Implementation
- 10 Single Sign On
- 16 LoudVoice
- 658 Turnkey Plugins
- 42 Drupal
- 33 Joomla!
- 21 Magento
- 22 myBB
- 84 Opencart
- 125 phpBB
- 39 PrestaShop
- 31 Simple Machines Forum
- 9 Vanilla
- 17 vBulletin
- 8 WHMCS
- 221 WordPress
- 6 ZenCart
Answers
It's important to us to be able to get updates on API changes - even one like what seems to have happened here where an endpoint was changed to have the "correct" behavior, which has now broken some pieces of our integration.