Does linkedin API support webhooks or any other mechanism to deliver notifications to the API consumer? We have a client that require an app to monitor they several accounts and they require some way to get notifications of events like when some profile get liked or viewed
There is presently no webhook support for any LinkedIn APIs.
Related
I want send notifications to mobile app. For that I need JWT tokens.
In all Google's documentation says that I should use Admin SDK for obtaion tokens, but i can't do it.
How to obtain access and refresh tokens without Google's libraries?
I need URL, HTTP method and request payload.
After 3 days of searching, I found a solution in the documentation:
https://developers.google.com/identity/protocols/oauth2/service-account#jwt-auth
I am writing a server in a language (Rust) that hasn't an official driver from the Firebase team. I am doing Rest-API calls to Firebase Cloud Messaging which also works fine.
I am interested in subscribing clients to topics in my server. I don't see Rest-API as a supported way of adding/removing subscribtions from topics server-side: https://firebase.google.com/docs/cloud-messaging/manage-topics.
The Firebase Admin SDK allows you to perform basic topic management
tasks from the server side.
Is Rest-API supported, or not at all?
subscribing to FCM through restapi is not possible: https://firebase.google.com/docs/cloud-messaging/manage-topics only admin sdk makes this possible
I am developing an application of managing users personally owned companies comments, replies & messages. I am doing this via API. But Linkedin API v1 has very limited access. So I have two questions
Can i get the access of notifications, messages and replies via linkedin API v2?
How can i get the access of linkedin API v2?
for the V2 API you need a linkedin partnership:
https://developer.linkedin.com/partner-programs
without the partnership you cannot access the data.
and on the message/replies api:
no its currently not possible
it will be possible in the near future, see here.
https://developer.linkedin.com/docs/guide/v2/communications/messages
Utilize Messages API to retrieve and send messages to your connections and more! API is coming soon.
Our goal is sending notifications to groups of devices from our backend, and only from server side is possible to know which device should receive the notification.
We've done some attempts with AppCenter because we mostly work with Xamarin iOS/Android/Forms, but now we have the doubt that it's probably better to use directly Firebase API because wider and more powerful.
I see that with new version of API (HTTP V1) is not possible to send a notification to a list of tokens, feature that was available in legacy API using registration_ids parameter (https://firebase.google.com/docs/cloud-messaging/send-message).
Device group name (legacy protocols only)
I cannot use topics because when it's time to send the communication is a server's responsibility to prepare the "mailing list" for notifications.
I was thinking to use device group messaging (https://firebase.google.com/docs/cloud-messaging/android/device-group) but these are part of the legacy api, and I'm not sure if it makes sense/it's possible to use them with new version of API.
Is an option to send a batch of 100-200-500 push notifications each one to only one token? In theory there isn't a limit to notifications which is possible to send, but I'm worried that sending too many of them I could risk to be banned.
Is it better to use legacy API? Also AppCenter (Microsoft) uses legacy API, it's evident because of how the setup works and because from AppCenter's console it's possible to send notifications to a list of tokens, feature unavailable on Firebase's console.
Another person just asked something similar but the answer was to use topics (How to send firebase notification for all user at a time?).
Got here from the link in your comment in my answer here. And just to reiterate my response there, when sending messages to multiple tokens with v1, the suggested approach now is to use Topics Messaging, since registration_ids is not supported.
Is it better to use legacy API?
v1 was described as the more secure, cross platform, future proof way of sending messages to FCM clients. More secure since it uses OAuth2 security model.
However, if your use-case is better with using the legacy API, then I suggest you go ahead with using it.
This page suggests that you should stay with the legacy API if you want to continue to use the multicast feature: https://firebase.google.com/docs/cloud-messaging/migrate-v1
Any apps that use device group messaging or multicast messaging, however, may prefer to wait for future versions of the API. HTTP v1 does not support these features of the legacy API.
I am novice in notification sending.
I have read some materials and I encountered with the words like
pushwoosh
and
google cloud messaging
For me it(and pushwoosh and GCM) looks like a resource for sending notification.
Also I understand that these words are related but I don't understand this relation(hierarchy)
Please clarify this relation.
Google Cloud Messaging, or GCM, is a free service by Google that can deliver messages from your server to your Android app. The app can choose to handle such messages by displaying notifications to the user.
PushWoosh is a 3rd party service (one of several, such as UrbanAirship and Parse) that has an API for sending push notifications for multiple platforms, including Android and iOS.
PushWoosh uses Google Cloud Messaging under the hood to send the messages to Android devices.
Your server can interface directly with Google's GCM server or interface with a 3rd party provider, which can cost you money, but can be easier to implement.