Atlassian rest api design guidelines

Dec 08, 2017 · Atlassian REST API design guidelines version 1. This document provides guidelines to Atlassian developers who are designing REST APIs for Atlassian applications. We are publishing these design principles and guidelines for viewing by the wider community for these reasons:

We'd like to create a REST API for JIRA. The main aim is to make it simpler for administrators and developers to retrieve issue and project information from JIRA, and update issue and project information on JIRA. Please add comments to this issue, letting us know the functionality you would find useful in a JIRA REST API. Background information: I’m writing a REST plugin module to handle an incoming webhook. The request does not carry an authorization header, so I annotated the method in the rest servlet with @anonymousAllowed as described in the atlassian-rest-api-design-guidelines docs. However, during testing I get a 401 unauthorized response.

May 25, 2017 · Hi Dave, we’d like to be good REST API citizens and rate limit our requests to JIRA instances. Can you give us any hints towards a sensible rate limit we should use until Atlassian implement one? Or how many concurrent requests our add-on should be making to any given Jira instance? The 2.0 REST API will rely on the Atlassian Cloud Admin API for user and group management, but those API endpoints are not yet available. Until the Atlassian platform services are fully available in Bitbucket we will continue to support these 1.0 REST endpoints: Nov 19, 2017 · API design guidelines may cover some of these topics but not all of them. Governance topics besides versioning are not really well represented in guidelines I have analyzed. They focus mainly on how to design API and less about the rest. But still, some guidelines talk about deprecation (Zalando or Atlassian) or API design validation process ... Jul 22, 2014 · For FishEye 3.5 we've applied the new Atlassian Design Guidelines to the file browser. Not only do you get a clearer overview of your files and directories, but the FishEye experience is now much more closely aligned with other Atlassian products, such as JIRA and Stash: New REST APIs for automating administration Note, there is feature parity between the whitelisted private resources and the new public REST resources. If you have a P2 add-on — Be aware that the private JIRA Agile REST API will remain experimental and may break at any time. You can continue to use the private API, but we recommend that you migrate to the new public REST API. What are the best practices for using credentials for jira access through the rest api. We want to. create issues (for any of our web users - they are not jira users) list issues (reports) provide way for people to search for issues; Should I create a usr just for the rest api. I'm uncomfortable having a real persons credentials in the php code ...

It was billed as a view library, not a framework. Ember and Angular’s popularity a year ago was impossible to ignore. I’ve built several Angular apps in the past including several Atlassian add-ons like the REST API Browser, Bob built HipChat video using Angular, and Clifton had some experience with Ember. Sep 05, 2019 · I am writing an application to communicate with BB Server via the REST API. The REST API documentation seems to be a bit incomplete and I’m having difficulty figuring out exactly how to download non-text files from a BB Server repository. The following curl command successfully downloads a pdf file from BB server. Feb 25, 2016 · Full documentation on Atlassian rest XSRF protection can be found in the Atlassian rest api design guidelines. To reproduce the XSRF example in the JIRA plugin: 1) Go to JIRA Administration and click the "Workflow Tab Settings" link in "Global Settings". 2) Enter a value into the imageUrl field such as "foo" and click Update. The REST API Browser is now a bundled plugin separate from the Developer Toolbox ... Minor update to follow the Atlassian Design Guidelines. Collapsed Expanded 2.0.2 ... App approval guidelines. After creating and testing your app, your next step is to submit it for approval. To uphold standards of quality and reliability that our customers expect, all publicly listed apps are subject to an approval process.