I am trying to build a bot for answering (only) my mentions and it seems I can't easily do that.
Is it possible to get something like application's own https://www.flowdock.com/rest/notifications/mentions call using the official REST API of Flowdock?
I couldn't find any easy way, just going through all my flows and searching for mentions via tags (tag being my username), which is pretty unoptimal and hard to do.
I've handled this as follows via UNOFFICIAL APIs:
mentions via https://www.flowdock.com/rest/notifications/mentions?limit=%d
private messages via https://www.flowdock.com/rest/notifications/unreads
Related
My aim is to select some text from a web page, start a google chrome extension and give the text to a google cloud api (Natural Language API) in my case.
I want to do some sentimental analysis and then get back the result to mark/ highlight positive sentences in green and negative ones in red.
I am new to this and do not know how to start.
The extension consists of manifest, popup etc. How should I call an API from there that does Natural Language Processing?
Should I create a Google Cloud Application with an API_KEY to call? In that case I would have to upload my credentials right?
Sorry sounds a bit confusing I know but I just don't know how I can bring this 2 things together an would be more than happy about any help
The best way to authenticate your app will depend on the specific needs and use cases of your application. You can see an overview of all the different methods here.
If you are not planning on identifying users nor on using a back end server that handles authenticating (as I assume to be your case), the best option would indeed be to use API keys. They do not identify the user, but are enough for the Natural Language APIs.
To do this you will need to create an API key for the services you want and add the necessary restrictions to make the key as secure as possible. Detailed instructions on how to do this and how to use the key in a url can be found here.
The API call could be made from within the Chrome extension with any JavaScript method capable of performing POST requests. For example using XMLHttpRequest or the Fetch API. You can find an example of the parameters that need to be included in the request here.
You may run into CORS issues when making the request directly from the extension. I recommend reading this answer, where a couple of workarounds for these issues are suggested.
I have been tasked with creating an internal app that interfaces the Rally API to do various 'legwork' for a speedier day around the office.
I am frustrated because I cannot find documentation on exactly what is available and how to use it. I am scraping and scraping away on different sites, google, etc just to find stuff like 'hierarchicalrequirement' is actually UserStory. so, it seems to me that Rally really doesn't WANT anyone to use their API... quite frustrating.
Their documentation says things like toCreate["Workspace"] = ('1234567')
where it's actually toCreate["Workspace"] = /workspace/1234567
I need an enumeration of what's available and what they're actually named.
It looks like you are trying to use one of their SDKs. Their documentation for their REST API can be found here.
https://rally1.rallydev.com/slm/doc/webservice/
Also, here is the link to their app API,
https://help.rallydev.com/apps/2.0/doc/#
And their lookback API
https://rally1.rallydev.com/analytics/doc/#/manual
And if you want documentation to a specific language SDK, you can look at Github.
when i'm using the google-translate website like this
https://translate.google.de/#de/en/schnell
i have the possibility to click on the suggested translation, and i can see alternatives (for example quick, fast etc.)
Is there any possiblity to get these alternatives via the API ? Or does anybody know a reliable API to get a translation for a single word with alternatives?
At the moment there is no such feature. I've filed a Feature Request to get this implemented, although there is no ETA.
I'm working on a cloud project and I have to use Contrail it provides a RESTful API to use, but it is documentation is too small. I would like to know how to perform rest requests, especially post requests on "project" resource.
Each Contrail config node provides supported API details(searchable) at http://:8082/documentation/index.html
You could also check here which is a bit old but should serve your project API needs.
Your question is old, but as there are no other answers I thought I would contribute one. Were you interested in an answer or just wanted to share the documentation you'd written? I agree with you that Contrail documentation is very scarce, and every attempt to contribute to it should be appreciated. I had to integrate with Contrail API a while ago, and found out that in some cases I had to call OpenStack APIs to get the job done (Contrail is built on top of OpenStack). Project and user management were some of them.
I wrote a documentation about Contrail api, For each resource I mention the allowed methods and which parameters to integrate on the request body and I test it until I get it to work finally I put an example. I haven't finished the documentation, I stopped working on Open Contrail. The documentation is my personal try maybe it would be useful and maybe it contains some mistakes, Thus, I would like to share it. You can find it here.
I would like to use the twitter site-streams but I can't find a way to use them. There is no API-docs online and how to access site-streams.
Does someon have an example in php or better c#?
Are there any API-samples or a full API-doc?
Thanks
Matthias
I called oAuth before doing something similar to Shannon Whitley's user streams example. Use the curl commands generated for you at dev.twitter.com to double check your C# generate urls.
The site stream url is buried in the top middle of the doc (/2b/site.json?follow=1,2,3,4,5) # dev.twitter.com
I'd also follow #sitestreams as well to get heads up on site stream restarts.
The API looks to still be in beta, I found this. It's not a lot of detail, but the post was only a few weeks ago so it is something pretty new. It uses the same REST API that all of twitter uses so if you are familiar with that you should be able to use what it gives you.
If you need a tutorial on REST with twitter here is a decent tutorial. It is using basic authentication so I do strongly recommend that you use OAuth instead.