BitBucket API

Package pdfwriter provides a mid-level generator for PDF documents. The goal is to provide an API at the same level of abstraction as PDF documents themselves. The document structure can be defined, as well as adding pages with text, graphics, and annotations. The coordinate system used is based on the native format for PDF documents. Although scaling transforms are possible, all distances and dimensions are specified in points (1/72 inch). The origin for the coordinate system is in the bottom left corner. Low-level primitives (such as described in section 3 of the reference) will not be exposed. ISO 32000-1 Document management -- Portable document format -- Part 1: PDF 1.7

Package aetools helps writting, testing and analysing Google App Engine applications. The aetools package implements a simple API to export the entity data from Datastore as a JSON stream, as well as load a JSON stream back into the Datastore. This can be used as a simple way to express state into a unit test, to backup a development environment state that can be shared with team members, or to make quick batch changes to data offline, like setting up configuration entities via Remote API. The goal is to provide both an API and a set of executable tools that uses that API, allowing for maximum flexibility. The functions Load, LoadJSON, Dump and DumpJSON operate using JSON data that represents datastore entities. Each entity is mapped to a JSON Object, where each entity property name is an Object atribute, and each property value is the corresponding Object atribute value. The property value is encoded using a JSON primitive, when possible. When the primitives are not sufficient to represent the property value, a JSON Object with the attributes "type" and "value" is used. The "type" attribute is a Datastore type, and value is a json-primitive serialization of that value. For instance, Blobs are encoded as a base64 JSON string, and time.Time values are encoded using the time.RFC3339 layout, also as strings. Datastore Keys are aways encoded as a JSON Array that represents the Key Path, including ancestors, but without the application ID. This is done to allow the entity key to be more readable and to be application independent. Currently, they don't support namespaces. Multiple properties are represented as a JSON Array of values described above. Unindexed properties are aways JSON objects with the "indexed" attribute set to false. This format is intended to make use of the JSON types as much as possible, so an entity can be easily represented as a text file, suitable for read or SCM checkin. The exported data format can also be used as an alternative way to export from Datastore, and then load the results right into other service, such as Google BigQuery or MongoDB. The package aetools/bundle contains a sample webapp to help you manage and stream datastore entities into BigQuery. The bundle uses the aetools/bigquerysync functions to infer an usefull schema from datastore statistics, and sync your entity data into BigQuery. The command aetools/remote_api is a Remote API client that exposes the Load and Dump functions to make backup and restore of development environment state quick and easy. This tool can also help setting up Q.A. or Production apps, but should be used with care.

Package odbc3-go provides a thin wrapper around the ODBC API. The acronym ODBC refers to Open Database Connectivity, and the API provides a abstract and low-level interface to different types of database servers. Drivers exist for most major databases types, which means that the API can provide an agnostic interface to most databases. This package provide a thin wrapper around the ODBC API. This means that most functions exist with nearly the same parameters and return values as in the underlying C API. Therefore, documentation and tutorials for ODBC should also be useful in understanding this package. However, some modifications in the API are present. These modifications exist to ensure type-safety, whereas the C API frequently requires unsafe casts. On linux and other unix-like systems, this package uses cgo. To build this package, you will need to have the necessary development files (i.e. headers) installed on your system. You will also need a compiler. On windows, this package uses the syscall interface. No development files are required.

Package tcell provides a lower-level, portable API for building programs that interact with terminals or consoles. It works with both common (and many uncommon!) terminals or terminal emulators, and Windows console implementations. It provides support for up to 256 colors, text attributes, and box drawing elements. A database of terminals built from a real terminfo database is provided, along with code to generate new database entries. Tcell offers very rich support for mice, dependent upon the terminal of course. (Windows, XTerm, and iTerm 2 are known to work very well.) If the environment is not Unicode by default, such as an ISO8859 based locale or GB18030, Tcell can convert input and outupt, so that your terminal can operate in whatever locale is most convenient, while the application program can just assume "everything is UTF-8". Reasonable defaults are used for updating characters to something suitable for display. Unicode box drawing characters will be converted to use the alternate character set of your terminal, if native conversions are not available. If no ACS is available, then some ASCII fallbacks will be used. A rich set of keycodes is supported, with support for up to 65 function keys, and various other special keys.

Package adyen is Adyen API Library for GO

This package is a wrapper for JavaScriptCore, which is the JavaScript engine used by the WebKit web browser engine. In addition to providing access to the library, this wrapper allows callers to easily reflect native functions and objects from Go into the scripting environment. For a complete description of the library, and the purpose and use of the JavaScriptCore API, please refer to the WebKit documentation. As an example use of the library:

Package main Ignition Fuel Server RESET API This package provides a REST API to the Ignition Fuel server. Schemes: https Host: staging-api.ignitionfuel.org BasePath: /1.0 Version: 0.1.0 License: Apache 2.0 Contact: info@openrobotics.org swagger:meta go:generate swagger generate spec

Package easyreq provides support for creating requests easily for multipart form request or json API requests. Usage import "github.com/nexneo/easyreq" Form Example or Form will choose Content-Type based on any file added or not. Json Example or

Package main implements the CLI for transforming Cobertura XML coverage reports into JSON output, for consumption by the Bitbucket Server code coverage plugin API.

Package logrus is a structured logger for Go, completely API compatible with the standard library logger. The simplest way to use Logrus is simply the package-level exported logger: Output: For a full guide visit https://github.com/sirupsen/logrus

The goal of this package is to preload xsd files into memory and to validate xml (fast) using libxml2, like post bodys of xml service endpoints or api routers. At the time of writing, similar packages I found on github either didn't provide error details or got stuck under load. In addition to providing error strings it also exposes some fields of libxml2 return structs.

Package gatt provides a Bluetooth Low Energy gatt implementation. Gatt (Generic Attribute Profile) is the protocol used to write BLE peripherals (servers) and centrals (clients). This package is a work in progress. The API will change. As a peripheral, you can create services, characteristics, and descriptors, advertise, accept connections, and handle requests. As a central, you can scan, connect, discover services, and make requests. gatt supports both Linux and OS X. On Linux: To gain complete and exclusive control of the HCI device, gatt uses HCI_CHANNEL_USER (introduced in Linux v3.14) instead of HCI_CHANNEL_RAW. Those who must use an older kernel may patch in these relevant commits from Marcel Holtmann: Note that because gatt uses HCI_CHANNEL_USER, once gatt has opened the device no other program may access it. Before starting a gatt program, make sure that your BLE device is down: If you have BlueZ 5.14+ (or aren't sure), stop the built-in bluetooth server, which interferes with gatt, e.g.: Because gatt programs administer network devices, they must either be run as root, or be granted appropriate capabilities: USAGE See the server.go, discoverer.go, and explorer.go in the examples/ directory for writing server or client programs that run on Linux and OS X. Users, especially on Linux platforms, seeking finer-grained control over the devices can see the examples/server_lnx.go for the usage of Option, which are platform specific. See the rest of the docs for other options and finer-grained control. Note that some BLE central devices, particularly iOS, may aggressively cache results from previous connections. If you change your services or characteristics, you may need to reboot the other device to pick up the changes. This is a common source of confusion and apparent bugs. For an OS X central, see http://stackoverflow.com/questions/20553957. gatt started life as a port of bleno, to which it is indebted: https://github.com/sandeepmistry/bleno. If you are having problems with gatt, particularly around installation, issues filed with bleno might also be helpful references. To try out your GATT server, it is useful to experiment with a generic BLE client. LightBlue is a good choice. It is available free for both iOS and OS X.

Package binance is a Golang SDK for binance APIs.

Package sling is a Go HTTP client library for creating and sending API requests. Slings store HTTP Request properties to simplify sending requests and decoding responses. Check the examples to learn how to compose a Sling into your API client. Use a Sling to set path, method, header, query, or body properties and create an http.Request. Use Path to set or extend the URL for created Requests. Extension means the path will be resolved relative to the existing URL. Use Get, Post, Put, Patch, Delete, or Head which are exactly the same as Path except they set the HTTP method too. Add or Set headers for requests created by a Sling. Define url parameter structs (https://godoc.org/github.com/google/go-querystring/query). Use QueryStruct to encode a struct as query parameters on requests. Define JSON tagged structs (https://golang.org/pkg/encoding/json/). Use BodyJSON to JSON encode a struct as the Body on requests. Requests will include an "application/json" Content-Type header. Define url tagged structs (https://godoc.org/github.com/google/go-querystring/query). Use BodyForm to form url encode a struct as the Body on requests. Requests will include an "application/x-www-form-urlencoded" Content-Type header. Use Body to set a plain io.Reader on requests created by a Sling. Set a content type header, if desired (e.g. Set("Content-Type", "text/plain")). Each Sling generates an http.Request (say with some path and query params) each time Request() is called, based on its state. When creating different slings, you may wish to extend an existing Sling to minimize duplication (e.g. a common client). Each Sling instance provides a New() method which creates an independent copy, so setting properties on the child won't mutate the parent Sling. Without the calls to base.New(), tweetShowSling and tweetPostSling would reference the base Sling and POST to "https://api.twitter.com/1.1/statuses/show.json/statuses/update.json", which is undesired. Recap: If you wish to extend a Sling, create a new child copy with New(). Define a JSON struct to decode a type from 2XX success responses. Use ReceiveSuccess(successV interface{}) to send a new Request and decode the response body into successV if it succeeds. Most APIs return failure responses with JSON error details. To decode these, define success and failure JSON structs. Use Receive(successV, failureV interface{}) to send a new Request that will automatically decode the response into the successV for 2XX responses or into failureV for non-2XX responses. Pass a nil successV or failureV argument to skip JSON decoding into that value.

Package chanstream provides an API that is similar to that used for TCP and Unix Domain sockets (see net.TCP), for use in intra-process communication on top of Go channels. This makes it easy to swap it for another net.Conn interface. By using channels, we avoid exposing any interface to other processors, or involving the kernel to perform data copying.

Package excelize providing a set of functions that allow you to write to and read from XLAM / XLSM / XLSX / XLTM / XLTX files. Supports reading and writing spreadsheet documents generated by Microsoft Excel™ 2007 and later. Supports complex components by high compatibility, and provided streaming API for generating or reading data from a worksheet with huge amounts of data. This library needs Go version 1.15 or later. See https://xuri.me/excelize for more information about this package.

Package gojsonq provides a simple, elegant and fast ODM like API to access/query JSON document. JSON document can be read from file, string or io.Reader. Accessing the value of json property or querying document is simple as the example below: For more details, see the documentation and examples.

Package gojsonq provides a simple, elegant and fast ODM like API to access/query JSON document. JSON document can be read from file, string or io.Reader. Accessing the value of json property or querying document is simple as the example below: For more details, see the documentation and examples.

common.go defines common types used throughout the OpenAI API.

PixelPay's tool that simplifies integrations with APIs from the PixelPay platform. This documentation provides specific details about the Golang SDK. If you want to see general information about the functioning of this collection of SDKs, go to: https://docs.pixelpay.app/ Assets contains resources based on ISO that help the SDK function. Entities provide even more information about the type of response received from services. Exceptions contains what is necessary to format expected errors. Helpers contains useful functions used throughout the SDK. Models provides predefined structures to facilitate interaction with PixelPay entities. Requests are directives that take the required data from the models and convert it into a proper request that our system can interpret. Responses includes all the different types of Responses that can be obtained when making a query to the PixelPay services. Services are in charge of all the communication between your integration and the PixelPay system.

Package gofpdf implements a PDF document generator with high level support for text, drawing and images. - UTF-8 support - Choice of measurement unit, page format and margins - Page header and footer management - Automatic page breaks, line breaks, and text justification - Inclusion of JPEG, PNG, GIF, TIFF and basic path-only SVG images - Colors, gradients and alpha channel transparency - Outline bookmarks - Internal and external links - TrueType, Type1 and encoding support - Page compression - Lines, Bézier curves, arcs, and ellipses - Rotation, scaling, skewing, translation, and mirroring - Clipping - Document protection - Layers - Templates - Barcodes - Charting facility - Import PDFs as templates gofpdf has no dependencies other than the Go standard library. All tests pass on Linux, Mac and Windows platforms. gofpdf supports UTF-8 TrueType fonts and “right-to-left” languages. Note that Chinese, Japanese, and Korean characters may not be included in many general purpose fonts. For these languages, a specialized font (for example, NotoSansSC for simplified Chinese) can be used. Also, support is provided to automatically translate UTF-8 runes to code page encodings for languages that have fewer than 256 glyphs. To install the package on your system, run Later, to receive updates, run The following Go code generates a simple PDF file. See the functions in the fpdf_test.go file (shown as examples in this documentation) for more advanced PDF examples. If an error occurs in an Fpdf method, an internal error field is set. After this occurs, Fpdf method calls typically return without performing any operations and the error state is retained. This error management scheme facilitates PDF generation since individual method calls do not need to be examined for failure; it is generally sufficient to wait until after Output() is called. For the same reason, if an error occurs in the calling application during PDF generation, it may be desirable for the application to transfer the error to the Fpdf instance by calling the SetError() method or the SetErrorf() method. At any time during the life cycle of the Fpdf instance, the error state can be determined with a call to Ok() or Err(). The error itself can be retrieved with a call to Error(). This package is a relatively straightforward translation from the original FPDF library written in PHP (despite the caveat in the introduction to Effective Go). The API names have been retained even though the Go idiom would suggest otherwise (for example, pdf.GetX() is used rather than simply pdf.X()). The similarity of the two libraries makes the original FPDF website a good source of information. It includes a forum and FAQ. However, some internal changes have been made. Page content is built up using buffers (of type bytes.Buffer) rather than repeated string concatenation. Errors are handled as explained above rather than panicking. Output is generated through an interface of type io.Writer or io.WriteCloser. A number of the original PHP methods behave differently based on the type of the arguments that are passed to them; in these cases additional methods have been exported to provide similar functionality. Font definition files are produced in JSON rather than PHP. A side effect of running go test ./... is the production of a number of example PDFs. These can be found in the gofpdf/pdf directory after the tests complete. Please note that these examples run in the context of a test. In order run an example as a standalone application, you’ll need to examine fpdf_test.go for some helper routines, for example exampleFilename() and summary(). Example PDFs can be compared with reference copies in order to verify that they have been generated as expected. This comparison will be performed if a PDF with the same name as the example PDF is placed in the gofpdf/pdf/reference directory and if the third argument to ComparePDFFiles() in internal/example/example.go is true. (By default it is false.) The routine that summarizes an example will look for this file and, if found, will call ComparePDFFiles() to check the example PDF for equality with its reference PDF. If differences exist between the two files they will be printed to standard output and the test will fail. If the reference file is missing, the comparison is considered to succeed. In order to successfully compare two PDFs, the placement of internal resources must be consistent and the internal creation timestamps must be the same. To do this, the methods SetCatalogSort() and SetCreationDate() need to be called for both files. This is done automatically for all examples. Nothing special is required to use the standard PDF fonts (courier, helvetica, times, zapfdingbats) in your documents other than calling SetFont(). You should use AddUTF8Font() or AddUTF8FontFromBytes() to add a TrueType UTF-8 encoded font. Use RTL() and LTR() methods switch between “right-to-left” and “left-to-right” mode. In order to use a different non-UTF-8 TrueType or Type1 font, you will need to generate a font definition file and, if the font will be embedded into PDFs, a compressed version of the font file. This is done by calling the MakeFont function or using the included makefont command line utility. To create the utility, cd into the makefont subdirectory and run “go build”. This will produce a standalone executable named makefont. Select the appropriate encoding file from the font subdirectory and run the command as in the following example. In your PDF generation code, call AddFont() to load the font and, as with the standard fonts, SetFont() to begin using it. Most examples, including the package example, demonstrate this method. Good sources of free, open-source fonts include Google Fonts and DejaVu Fonts. The draw2d package is a two dimensional vector graphics library that can generate output in different forms. It uses gofpdf for its document production mode. gofpdf is a global community effort and you are invited to make it even better. If you have implemented a new feature or corrected a problem, please consider contributing your change to the project. A contribution that does not directly pertain to the core functionality of gofpdf should be placed in its own directory directly beneath the contrib directory. Here are guidelines for making submissions. Your change should - be compatible with the MIT License - be properly documented - be formatted with go fmt - include an example in fpdf_test.go if appropriate - conform to the standards of golint and go vet, that is, golint . and go vet . should not generate any warnings - not diminish test coverage Pull requests are the preferred means of accepting your changes. gofpdf is released under the MIT License. It is copyrighted by Kurt Jung and the contributors acknowledged below. This package’s code and documentation are closely derived from the FPDF library created by Olivier Plathey, and a number of font and image resources are copied directly from it. Bruno Michel has provided valuable assistance with the code. Drawing support is adapted from the FPDF geometric figures script by David Hernández Sanz. Transparency support is adapted from the FPDF transparency script by Martin Hall-May. Support for gradients and clipping is adapted from FPDF scripts by Andreas Würmser. Support for outline bookmarks is adapted from Olivier Plathey by Manuel Cornes. Layer support is adapted from Olivier Plathey. Support for transformations is adapted from the FPDF transformation script by Moritz Wagner and Andreas Würmser. PDF protection is adapted from the work of Klemen Vodopivec for the FPDF product. Lawrence Kesteloot provided code to allow an image’s extent to be determined prior to placement. Support for vertical alignment within a cell was provided by Stefan Schroeder. Ivan Daniluk generalized the font and image loading code to use the Reader interface while maintaining backward compatibility. Anthony Starks provided code for the Polygon function. Robert Lillack provided the Beziergon function and corrected some naming issues with the internal curve function. Claudio Felber provided implementations for dashed line drawing and generalized font loading. Stani Michiels provided support for multi-segment path drawing with smooth line joins, line join styles, enhanced fill modes, and has helped greatly with package presentation and tests. Templating is adapted by Marcus Downing from the FPDF_Tpl library created by Jan Slabon and Setasign. Jelmer Snoeck contributed packages that generate a variety of barcodes and help with registering images on the web. Jelmer Snoek and Guillermo Pascual augmented the basic HTML functionality with aligned text. Kent Quirk implemented backwards-compatible support for reading DPI from images that support it, and for setting DPI manually and then having it properly taken into account when calculating image size. Paulo Coutinho provided support for static embedded fonts. Dan Meyers added support for embedded JavaScript. David Fish added a generic alias-replacement function to enable, among other things, table of contents functionality. Andy Bakun identified and corrected a problem in which the internal catalogs were not sorted stably. Paul Montag added encoding and decoding functionality for templates, including images that are embedded in templates; this allows templates to be stored independently of gofpdf. Paul also added support for page boxes used in printing PDF documents. Wojciech Matusiak added supported for word spacing. Artem Korotkiy added support of UTF-8 fonts. Dave Barnes added support for imported objects and templates. Brigham Thompson added support for rounded rectangles. Joe Westcott added underline functionality and optimized image storage. Benoit KUGLER contributed support for rectangles with corners of unequal radius, modification times, and for file attachments and annotations. - Remove all legacy code page font support; use UTF-8 exclusively - Improve test coverage as reported by the coverage tool. Example demonstrates the generation of a simple PDF document. Note that since only core fonts are used (in this case Arial, a synonym for Helvetica), an empty string can be specified for the font directory in the call to New(). Note also that the example.Filename() and example.Summary() functions belong to a separate, internal package and are not part of the gofpdf library. If an error occurs at some point during the construction of the document, subsequent method calls exit immediately and the error is finally retrieved with the output call where it can be handled by the application.

* Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)

* Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git) * Bitbucket Server * * This is the reference document for the Atlassian Bitbucket REST API. The REST API is for developers who want to: - integrate Bitbucket with other applications; - create scripts that interact with Bitbucket; or - develop plugins that enhance the Bitbucket UI, using REST to interact with the backend. You can read more about developing Bitbucket plugins in the [Bitbucket Developer Documentation](https://developer.atlassian.com/bitbucket/server/docs/latest/). * * API version: 8.14 * Generated by: Swagger Codegen (https://github.com/swagger-api/swagger-codegen.git)