API Documentation for ScopeMaster Plugin via Jira - plugins

I am new to the Jira environment and I am currently doing research for ScopeMaster which is needed to use in Jira. I installed the ScopeMaster plugin in Jira. I can see a story analyzer in the user story. But I wanted to know the API calls related to ScopeMaster via Jira. Is there any API documentation available for the ScopeMaster via Jira? Only I was able to find ScopeMaster related API as mentioned below not related to Jira.
ScopeMaster API - https://help.scopemaster.com/article/46-apps

https://developer.atlassian.com/server/framework/atlassian-sdk/using-the-rest-api-browser/ is the way I explore the REST APIs of plugins. Make sure to uncheck the Public checkbox. You can also use the Network tab in the Chrome Inspector to see what is called. And contact the plugin vendor to ask for any info they are willing to make public

You can use ScopeMaster without using the "Jira plugin". It's available as a SaaS from Scopemaster.com
Scopemaster has a REST API that can be use without Jira but you must first have a registered account to use the Saas.
The "Jira Plugin" aka Story Analyser for Jira (from Scopemaster) offers a subset of the functionality available from the Saas. It conforms to the Jira Connect App construction and security guidelines.
I hope that clarifies for you. Colin (Scopemaster author).

Related

APPDYNAMICS Public Rest APIs info

I'm new to APPDYNAMCS and looking for APPDYNAMICS Public Rest APIs for the below data. I'm able to find out a few of them but not all. Can someone help me with this? Thanks in Advance
Looking for REST APIs for the below data.
1.Configuration Items( Business Application, servers, business service, etc) and relationship among them.
2.Service Map data.
3.Raw Event.
4.Alert data.
5.Raw Metrics.
6.Raw Logs.
7.Raw Traces.
8.SLO/SLI data.
9.Real User Monitoring / Synthetic Monitoring data
10.User sessions data
All currently available AppDynamics APIs are documented here: https://docs.appdynamics.com/display/PRO21/AppDynamics+APIs
The main page includes a summary of what is available.
While ingmar is technically correct, the documentation doesnt cover all the APIs available. There are undocumented APIs that even that AppDynamics utilities on github use.
There is a utility called AppDynamics command line tool which does a good job at documenting the APIs. The commands are listed in its commands.yml file.
Another source of API knowledge is my own rapport for appdynamics project in which I use some of these undocumented APIs after having figured out how the controller uses them.
good luck!

How can I call the Wiki REST Api from an Azure DevOps extension?

The Add a dashboard widget tutorial explains how to call the work item REST API using a VSS.require("TFS/WorkItemTracking/RestClient")d rest client.
I want to do the same, but for the Wiki Rest API. There certainly is a scope for this: vso.wiki.
However, I cannot find the equivalent of "TFS/WorkItemTracking/RestClient" for wiki. Maybe it is as simple as "TFS/Wiki/RestClient", but even if it was, what are the names and parameters of the functions I can use? I don't find that documented anywhere, and I don't want to have to figure that out by trial-and-error, each time publishing a new extension and seeing if it works.
And looking at REST Clients, there does not even seem to be a Wiki Rest Client.
So how can I access the Wiki Rest API from an Azure DevOps extension? Is there perhaps an example somewhere, that google has been successful in hiding from me?
N.B. I do know about the REST API Specs, but the mapping to REST client is not self-evident and apparently.
I stumbled upon Azure DevOps Web API clients and contracts, however, a brief grep revealed it does not contain the latest and greatest (pre-release) "pagesBatch" feature, and I did not find a relevant branch / tag either.
The wiki rest api documents for azure-devops-extension-api can be found here
You can also check the restful api for wiki here.
Check here to discover the client libraries for azure devops service rest api in different coding languages.
Hope above helps.

Does Uber's api have features for UberDost?

I am working with UberDost, but the application lacks functionalities, for this reason I want to implement my own solution.
Thanks!
Today, we do not provide UberDost functionality via the API. We will add it to the features request backlog and follow up on this thread if it ever changes.

java api similar to JTAPI?

I am working on a project and I need to use this tow api; jtapi, gjtapi. The problem is
both gjtapi and jtapi project seem dead. Is there a new similar java api?
JTapi is a specification that is implemented by vendors, as CISCO or AVAYA. In my experience, there is no an generic API for JTapi, because each provider customizes their own implementation according at their telephony platform.
If you want a "generic" JTapi you should review this link, that refer to an Asterisk JTapi:
http://asterisk-jtapi.sourceforge.net/

Visual REST API playground

What are some web apps that allow me to play with any REST APIs visually (by clicking) and also get some code generated (in any language) that captures what I have described visually?
Similar to Swagger or Google API Playground but allows me to talk to anything that speaks REST (assuming I have the proper auth credentials and I know what messages it understands).
Bonus points for something that can also "discover" what messages are understood, given a URL endpoint.
Microsoft has 2 that I know of
OData API explorer
The data market service explorer (requires signing in, and then you can access free data sets)
Considering that REST API's are going to follow their own conventions, terms, and have their own documentation (hopefully), this is an impossible problem. If you restrict your quest to visualizing API's that follow a "standard" form of self-documentation (see REST web service WSDL? for some hopeful scenarios) you might be able to accomplish this.
Or you can use something like http://www.programmableweb.com/ to discover tutorials, tools, examples, and mashups of various existing APIs.
You could mock an API at http://apiary.io/.
You could explore and existing one through tools (e.g. REST Console for Chrome)
What you can't have, is one-size-fits-all explorer for "every possible REST API." Some APIs follow conventions that others don't.
apigee and apihub (now part of mulesoft) are two that I frequently visit. Of the two, apigee is my preferred provider.
One of the reasons that you're not going to see a lot of websites like this is because of the same-origin policy. This means that you can't access a RESTful API located at api.google.com from a web app running at, say, www.restfiddle.com without sending all the API traffic through restfiddle.com's servers. Sites like JSFiddle can exist (and are used widely) because all the processing is done on the client side.
Browser plugins, however, are exempt from the same-origin policy. If you're using Chrome, try Postman. If your REST client doesn't need to be web-based, check out SoapUI. IntelliJ IDEA has a nice REST client as well.
Try Restlet Studio, it's the only visual API designer I've found, and seems pretty good, it imports and exports swagger & RAML.
http://studio.restlet.com/