Note: This question is not about how to retrieve the list of webhook topics an app is subscribed to.
Shopify API Version: 2022-01 (Latest)
Shopify Admin Api: REST Admin Api
The Shopify Webhook Documentation lists several webhook topics by category.
Example:
Subscription Error
Most all of the topics listed in the documentation can be subscribed to. However, if I try to subscribe to any of the BillingAttempt topics, Shopify returns an error:
Invalid topic specified: subscription_billing_attempts\success.
Does it exist? Is there a missing access scope?
This particular webhook is for a custom app installed directly in the store. I have verified every available access scope has been enabled. As of today, there are a total of 62 available scopes and all are enabled.
What is the Actual Question?
This isn't about troubleshooting the above error.
The question is specifically: Where can I find the complete list of available topics?
Note: Shopify includes a full list of topics in their error message. But, none of them are for subscription_billing_xxx topics. Maybe this is just a case where the API error has the most update to date list? And the docs are out of date?
If I understood correctly this topics list is the one you are searching for: https://shopify.dev/api/admin-graphql/2023-01/enums/WebhookSubscriptionTopic
There is SUBSCRIPTION_BILLING_xxx topics:
SUBSCRIPTION_BILLING_ATTEMPTS_CHALLENGED
SUBSCRIPTION_BILLING_ATTEMPTS_FAILURE
SUBSCRIPTION_BILLING_ATTEMPTS_SUCCESS
SUBSCRIPTION_BILLING_CYCLE_EDITS_CREATE
SUBSCRIPTION_BILLING_CYCLE_EDITS_DELETE
SUBSCRIPTION_BILLING_CYCLE_EDITS_UPDATE
For the REST API: https://shopify.dev/api/admin-rest/2023-01/resources/webhook#event-topics
For the GraphQL API: https://shopify.dev/api/admin-graphql/2023-01/enums/WebhookSubscriptionTopic
Related
To clarify the title I am not thinking of the registering to a webhook through APIM, but to utilize APIM as my documentation for all API related information.
In our setup we wanted to also expose information about possible json objects from our webhooks and saw that this exists in OAS3.1. And azure APIM supports OAS3.1 for import. However importing a test webhook results in an error saying that it isn’t supported
This example was taken from OAS GitHub. So I know I can cheat and creat a dummy endpoint to allow people to view the documentation - but it is not ideal for our use case.
So the questions are:
how to expose the webhook documentation?
am I missing something in Microsoft documentation because I cannot see that it should not be allowed what I wanted to do?
I am trying to setup a webhook to my cloudrun and pubsub service.
Is there anyway in which i can get to see reactions and shares of my stories; The sample response does not seem to have a key value for the same.. Any suggestions ?
enter image description here
I don't think Instagram API has Reactions metric available yet. At least i could not find mentions to it on documentation.
I was able to find reactions info only on Facebook APIs. Maybe it still is a work in progress for Instagram.
( reactions are not event returned as metrics on story_insights ).
Unless reactions are considered on Instagram API as comments, there is no way to trigger Webhooks on reactions.
References:
https://developers.facebook.com/docs/instagram-api/guides/webhooks
https://developers.facebook.com/docs/graph-api/webhooks/reference/instagram/#story_insights
https://developers.facebook.com/docs/graph-api/webhooks/reference/instagram/#comments
We are using Chatbase for multiple clients that we identify with a different version number.
See my previous question here: Track multiple context for the same Bot
We have a dashboard for all those clients and would like to show them their own data. A bit like Google analytics allows it.
So:
Is an API in the pipeline (I couldn't find any existing resources)
If not, in what alternative way could we get the data to present it?
We have a .csv export that is currently limited to the first 500 rows of your message variations report. It is on our roadmap to increase the scope of this report, however there is no official timeline for release.
Our recommendation for deploying an integration like you described in your message is as follows:
Have the user create a Chatbase account in order to obtain the API key
Have the user integrate their analytics on your platform by providing the API key
Send the messages from their bot to their Chatbase API
Provide the user deeplinks to the Chatbase reports from within your UI
Alternatively, you could configure your bot to send a redundant message to an internal database, or bigquery table to have access to all of your logs.
If you would like access to data you have sent to Chatbase up to this point, please contact chatbase-support#google.com and provide your bot's name and/or api key and we can provide a one-time export.
I have a nodejs chat bot app which to listens to direct messages from twitter account. It was created with stream API of twitter. Now we are trying to migrate to new twitter Account Activity API.
We have used this package to do this. But we met with this issue "Webhook URL must be defined to create subscriptions". Actually we have set a Webhook URL and still we have this issue.
Is there anyone who have implemented Twitter Account Activity API successfully? I could use some help here.
if you haven't found an answer, here (account-activity-dashboard) is a web app that will help get started with Twitter's premium Account Activity API. The account-activity-dashboard will help you configure the webhook urls and the subscriptions.
You can also have a look at my forked repo which i used to create my twitter bot
I'm having differences with the responses to my questions (in Spanish language) performed against an Azure Web App Bot service that queries to an instance of QnAMaker and the queries directly performed against the specific QnAMaker service for that instance.
For this specific case I've performed the same questions on the Bot's Web Chat and on the QnAMaker Test Chat. In several responses retrieved by the Bot's Web Chat I get the default message (like if the question does not match an answer) while in the responses retrieved by the QnAMaker Test Chat I get an answer matched in the Knowledge Base.
Find below the screenshots with the results on both chats:
Bot's Web Chat responses:
Bot Chat Screenshot 01
Bot Chat Screenshot 02
QnAMaker Test Chat Responses:
QnAMaker Chat Screenshot 01
QnAMaker Chat Screenshot 01
The entire configuration to integrate the QnAMaker service with the Bot was checked and it looks OK. Even, the QnaThreshold used to perform the queries in Bot's App Settings was set to 0.04 (4% match) to ensure the results are not filtered.
I guess the problem is a configuration difference between the Bot's module that builds the POST request against the QnAMaker service.
Could anyone help me to fix this to ensure the request performed by the Bot is the same than the one performed by the QnAMaker Test Chat and get the same results through both chats.
Thanks
Alternate questions can improve the likelihood of a match with a user query. You can try to add that phrase as alternate question to an existing QnA pair.
the QnaThreshold used to perform the queries in Bot's App Settings was set to 0.04
To troubleshoot the issue, you can try to set the ScoreThreshold to 0, then override RespondFromQnAMakerResultAsync and check the actual QnAMakerResult returned by QnAMaker service.
I see the questions you ask are not exactly the same
"donde comprar entradas" <> "donde compro entradas", this could explain some of the differences.
Then, I think that QnA Maker test chat uses some kind of staging environment whereas Azure Bot Chat uses the last published version of the KB.
Are you sure you have published your last changes ?
The issue is already solved.
The problem was generated by the data type of the App Settings variables. These values are strings encoded in IBM852 into the process.env object and when Javascript convert them into float or integer types the generated values are not correct.
Applying the respective conversion functions like parseFloat() or parseInt() before using the app settings variables in app.js will solve the problem.
Thanks Tyrel Roesler, Web App Support Engineer from Microsoft, for helping me to discover the problem.