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.
Related
after reading this answer https://stackoverflow.com/a/51614256/15486192 from #Arsam, i am successfully sending data from nodeMcu esp8266 to firebase.
but i am using Database secrets Although it is deprecated.
and while searching for an alternative i came across firebase REST
Firebase Database REST API
API Usage
You can use any Firebase Realtime Database URL as a REST
endpoint. All you need to do is append .json to the end of the URL and
send a request from your favorite HTTPS client.
HTTPS is required. Firebase only responds to encrypted traffic so that your data remains safe.
after reading that, anyone conclude that you can send data to firebase using HTTPS request.
so my questions,
is REST API just an HTTP request?
i am just confused if it is, then why just not naming it HTTP API?
can i send my data to firebase Realtime-database using only https request from my client?if yes then how
REST or RESTful API design (Representational State Transfer) is designed to take advantage of existing protocols. While REST can be used over nearly any protocol, it usually takes advantage of HTTP when used for Web APIs.
Be carefull when using the REST API on the client side!
The REST API for the Firebase RTDB is usualy ment for development of code where you don't wand or can't use the official SDKs. For example when you code in a language that doesn't have a official Firebase SDK. Or also in usecases where you because of perfromacne reasons don't want to use the SDKs. In most cases landing pages.
BUT. The REST API is very handy for public data in your database. And I would only recommend to leave public data only the read access. Othervise anyone could fill up your database with knowing your REST API.
So if you plan to use the RTDB on your client side try to use official SDK because the handle the security for you.
David East even had a talk on the last Google IO on how to improve the loading time for laning pages by removing the Firebase SDKs and using the REST API. But that was also only for public data.
If you want to use it on a server from the backend you can use also the REST API. Here is the documentation for using the REST API and here for the authentication part of it.
I'am making a firebase PWA that shows a custom YouTube home. So, I want to list the videos of a user's YouTube home.
For that I'am using the Youtube Data API v3 and want to use the user's API key (coz if i use my API key, they will get my recommendations, right?).
The user will be logged into the site using Google Auth.
So, how can I use that information and
access their Google API console
get their API key
enable their Youtube data API
get their recommended results
(I can accept any wild method)
This is officially impossible. Hacks might exist, but not dependable. Sorry.
I'm trying to build a POC using QnA maker API, that can be integrated into my application.How can I get the list of KB's via API? I have voted for the this feature. Is this done or can be used now.?
It exists in the new QnAMaker API v4.0, and it's there: https://westus.dev.cognitive.microsoft.com/docs/services/5a93fcf85b4ccd136866eb37/operations/knowledgebases_getknowledgebasesforuser
But you will need an Ocp-Apim-Subscription-Key header where you place your subscription key, and I can't find a way to have this key.
For previous versions of the API, the key was:
Subscription key which provides access to this API. Found in your QnAMaker Service accounts.
For this v4:
Subscription key which provides access to this API. Found in your
Cognitive Services accounts.
I checked, it's not the keys located on https://qnamaker.ai/UserSettings and in my Azure portal, under AI + Cognitive Services, there is no QnA product like for LUIS API or other APIs.
Probably this v4 API is still not "official", we have to wait a bit.
EDIT April 23rd: QnAMaker API v4.0 is not more listed on Cognitive Services API services list...
EDIT May 3rd: QnAMaker API v4.0 is back on the list!
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.
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.