After a successful subscription to a webhook, a subscription ID is generated. Are these unique across all users?
The subscription ID is unique (it's using as GUID which are designed for that specific purpose)
Related
I have an Azure Logic App that consists in getting events info by a given Id. I use Office365 Get Event Connector but it doesn't retrieve iCalUId.
Remember that Outlook events have two "ids":
id: Unique identifier in resource calendar.
iCalUId: Unique identifier in ALL attendees calendar.
I need the last one.
Is there any way to obtain it?
Might be a little late for you, but for anyone else landing here iCalUid was added to the connector recently.
https://learn.microsoft.com/es-es/connectors/office365connector/#graphcalendareventclientreceive
Is there a way to subscribe to all NEW calendar entries create by all users in my organization? Basically, whenever anyone in my organization creates a meeting invite, my app needs to be notified.
Our app needs this to work for both Exchange Online and On-premise.
Is there a way to subscribe to all NEW calendar entries create by all users in my organization?
No Subscriptions and always in the context of a Mailbox or Mailbox Folder (you need to consider your mailboxes will be spread across different servers in different data-centers)
As a workaround you could create a Transport Rule that catches any Meeting invitations and redirect them to a particular mailbox. Then just subscribe to events on that mailbox.
I created a slack app with distribution (multiple clients)
and I subscribe to events several events like a message posted in a channel.
Beside the team_id field for identifying the client team - is there an ability to put my own key for a client?
Thank you.
No, Sack does not store any custom data for you. Its your job as an app developer to store all team related information for your app and link it to the Slack team_id. This is usually done with a database.
You can however include custom IDs with Slack requests, e.g. in the response you get from an interactive message. See this answer for more details on how this works.
I am currently using Twilio to send balance notifications for customers who have opted into SMS notifications, but have run into an issue in positively identifying accounts in the message logs. A number of customers have multiple accounts due to the nature of my industry, but naturally use the same phone number across all accounts. Is there any way to pass a parameter containing their internal account ID in the HTTP POST request without including it in the message body? I've searched extensively through Twilio's API docs and cannot find this addressed anywhere.
Twilio developer evangelist here.
As far as I know there is currently no way to store metadata, like your account ID, within an SMS sent via Twilio.
One idea could be that you purchase a number of Twilio numbers and tie together a user's phone number, a Twilio phone number and the specific account. That way, if you always send balance notifications for a specific account from a specific number then you can identify that message in the logs as belonging to that user phone number for that account.
Alternatively, I'd have thought it would be useful for users, if they have more than one account, to see to which account you are referring in a balance notification. Would it be possible to include the account id (or some other identifier that the user would recognise) and then parse that out of the message when reconciling messages and accounts?
Not exactly the question but if you are using twilio webhooks for status callbacks you can pass query string params through the status_callback parameter when making the call to send the SMS message and get it sent to your endpoint
We are using Google Checkout - google handled subscriptions. In our html form we are using merchant-item-id parameter to store the subscription plan id and user id, so when Google Checkout send us back the notification for the new orders (merchant-item-id is there) we know what user for what plan to charge. So far this works perfect.
But now, when a month is passed, and Google Checkout start creating the reoccurring orders, there is no merchant-item-id parameter in the notifications they send. So we don't know what user for what plan is charged.
What should we use as user identifier, so we can handle properly the subscription on our site?
Any ideas?
Btw. I know about the "buyer-id" parameter which is send with each new order notification, but that will not work for us, because it is possible that the same google buyer is paying for several of our users accounts.
I would try putting some unique info in "shopping-cart.items.item-1.merchant-private-item-data" to something unique that I can identify the subscription by.
Nikolaj