I need some help with implementing a status board with a REST API. I've already found the two best options (in my opinion): Stashboard and Whiskerboard.
I have already tried Whiskerboard and I find it easy to install and deploy because it does not need Google App Engine's SDK to be used locally. However, I need something like Stashboard's REST API: http://readthedocs.org/docs/stashboard/en/latest/restapi.html
I know that Whiskerboard is based on Stashboard so probably they have the same REST API. But I cannot seem to find any documentation on Whiskerboard's REST API. Moreover, I looked into each status board's models and there are lots of differences, with Whiskerboard's being largely simpler compared with that of Stashboard's, so they must not have the same REST API.
I will appreciate it if anyone can provide me a link to Whiskerboard's REST API which should be much like Stashboard's. If there really is none, some other solutions could still be suggested. Thank you in advance!
No, it doesn't have the same REST API. You could find this out by reading the code. If you want a similar REST API you have the following options:
Code the feature yourself.
Ask the developer of Whiskerboard for the feature.
Ask someone else at your organization to code and contribute the feature.
Good luck.
You can check out this solution forked by sijis and myself, jvasallo, that we have been working on. He forked the repo for whiskerboard and added an API to it. Still uses Django, and recently I did some work porting it to 1.5.1. Initially, Whiskerboard is a 1.3 Django app.
https://github.com/sijis/whiskerboard
Related
I am trying to implement account aggregation solution and am confused right now as there are multiple API's available that do the same thing.
I came across new Yodlee API as well as RESTful Wrapper APIs'. Both of these API classifications do the same thing but provide different APIs sets.
Can someone please let me know which one should I use?
I am referring to this link
https://developer.yodlee.com/API_Resources/API_Reference
Please go with Yodlee APIs, which is our latest product.
This is purely REST and the API response is simple, informative and decluttered. Here Webhooks is also supported
Please refer- https://developer.yodlee.com/Yodlee_API
API Flow- https://developer.yodlee.com/Yodlee_API/API_Flow/Add_Account_With_ProviderAccount
Swagger tool( to test APIs)- https://developer.yodlee.com/apidocs/index.php#!/providerAccounts
Hope this helps you in getting started.
Regards,
Krithik
Your documentation(API Reference) mentions some fields/endpoints deprecated but they still work in the old style. I find document inconsistent.
Also i could not even find a support email where i could even mail about this problem.
I would appreciate if you consider these points.
Thanks
I built a web app in Laravel 5.2, and now, I would like to use Angular or Vue, so I am separating an API from my controllers.
Thing is actually, in my controllers, I use a lot :
Auth::user() to refer to the logged user.
What is the best way to deal with it???
Read books about API design. If the existing app isn't designed to be a RESTful API in the first place then you're in for a lot of learning. Laracasts has a great series called Incremental APIs.
Laracasts.com
Build APIs You Won't Hate
OK, I'm expanding my answer, despite this is not a great question, it is probably too broad. You need to look into Oauth 2.0 authentication for your API, you can still use a username and password, but OAuth 2.0 tokens over SSL is probably the best simple way to provide authentication for your API. If it is only used internally, or is read only then you may not really require authentication for the API at all. There's not enough information about your use case to even make a guess about that. Good luck!
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.
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'm working on a tool in C# that interfaces the JIRA SOAP API. I have read the documentation but I can't find what I'm looking for. Does anyone know if it is possible to link an issue to another one via this api?
PS : Actually, my real need is to convert an issue as a subtask of an issue...
Last time I looked, JIRA's web service wasn't really actively supported or encouraged by Atlassian. It's very much a second-class citizen compared to the web front end, with very basic operations.
Also, it's not a WSI-compliant web service (it's an old Axis-based RPC_encoded service), and so modern web service stacks won't even bind to it. You might want check that your client can perform basic query operations before diving into the depths of the API.
You can actually go pretty far with Jelly scripts, but converting an issue to a subtask then linking it as a subtask... I'm not positive that you can go that far.