Package zap provides fast, structured, leveled logging. For applications that log in the hot path, reflection-based serialization and string formatting are prohibitively expensive - they're CPU-intensive and make many small allocations. Put differently, using json.Marshal and fmt.Fprintf to log tons of interface{} makes your application slow. Zap takes a different approach. It includes a reflection-free, zero-allocation JSON encoder, and the base Logger strives to avoid serialization overhead and allocations wherever possible. By building the high-level SugaredLogger on that foundation, zap lets users choose when they need to count every allocation and when they'd prefer a more familiar, loosely typed API. In contexts where performance is nice, but not critical, use the SugaredLogger. It's 4-10x faster than other structured logging packages and supports both structured and printf-style logging. Like log15 and go-kit, the SugaredLogger's structured logging APIs are loosely typed and accept a variadic number of key-value pairs. (For more advanced use cases, they also accept strongly typed fields - see the SugaredLogger.With documentation for details.) By default, loggers are unbuffered. However, since zap's low-level APIs allow buffering, calling Sync before letting your process exit is a good habit. In the rare contexts where every microsecond and every allocation matter, use the Logger. It's even faster than the SugaredLogger and allocates far less, but it only supports strongly-typed, structured logging. Choosing between the Logger and SugaredLogger doesn't need to be an application-wide decision: converting between the two is simple and inexpensive. The simplest way to build a Logger is to use zap's opinionated presets: NewExample, NewProduction, and NewDevelopment. These presets build a logger with a single function call: Presets are fine for small projects, but larger projects and organizations naturally require a bit more customization. For most users, zap's Config struct strikes the right balance between flexibility and convenience. See the package-level BasicConfiguration example for sample code. More unusual configurations (splitting output between files, sending logs to a message queue, etc.) are possible, but require direct use of go.uber.org/zap/zapcore. See the package-level AdvancedConfiguration example for sample code. The zap package itself is a relatively thin wrapper around the interfaces in go.uber.org/zap/zapcore. Extending zap to support a new encoding (e.g., BSON), a new log sink (e.g., Kafka), or something more exotic (perhaps an exception aggregation service, like Sentry or Rollbar) typically requires implementing the zapcore.Encoder, zapcore.WriteSyncer, or zapcore.Core interfaces. See the zapcore documentation for details. Similarly, package authors can use the high-performance Encoder and Core implementations in the zapcore package to build their own loggers. An FAQ covering everything from installation errors to design decisions is available at https://github.com/uber-go/zap/blob/master/FAQ.md.
Package tinylib provides small functions for aws api gateway with lambda Package tinylib provides small functions for aws api gateway with lambda
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 docker provides a client for the Docker remote API. See https://goo.gl/o2v3rk for more details on the remote API.
Package tgbotapi has functions and types used for interacting with the Telegram Bot API.
Package cos 腾讯云对象存储服务 COS(Cloud Object Storage) Go SDK。 封装了 V5 版本的 XML API 。 在项目的 examples 目录下有各个 API 的使用示例 。 默认所有 API 都是匿名访问. 如果想添加认证信息的话,可以通过自定义一个 http.Client 来添加认证信息. 比如, 使用内置的 AuthorizationTransport 来为请求增加 Authorization Header 签名信息:
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 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 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 codedeploy provides the client and types for making API requests to AWS CodeDeploy. AWS CodeDeploy is a deployment service that automates application deployments to Amazon EC2 instances or on-premises instances running in your own facility. You can deploy a nearly unlimited variety of application content, such as code, web and configuration files, executables, packages, scripts, multimedia files, and so on. AWS CodeDeploy can deploy application content stored in Amazon S3 buckets, GitHub repositories, or Bitbucket repositories. You do not need to make changes to your existing code before you can use AWS CodeDeploy. AWS CodeDeploy makes it easier for you to rapidly release new features, helps you avoid downtime during application deployment, and handles the complexity of updating your applications, without many of the risks associated with error-prone manual deployments. Use the information in this guide to help you work with the following AWS CodeDeploy components: Application: A name that uniquely identifies the application you want to deploy. AWS CodeDeploy uses this name, which functions as a container, to ensure the correct combination of revision, deployment configuration, and deployment group are referenced during a deployment. Deployment group: A set of individual instances. A deployment group contains individually tagged instances, Amazon EC2 instances in Auto Scaling groups, or both. Deployment configuration: A set of deployment rules and deployment success and failure conditions used by AWS CodeDeploy during a deployment. Deployment: The process, and the components involved in the process, of installing content on one or more instances. Application revisions: An archive file containing source content—source code, web pages, executable files, and deployment scripts—along with an application specification file (AppSpec file). Revisions are stored in Amazon S3 buckets or GitHub repositories. For Amazon S3, a revision is uniquely identified by its Amazon S3 object key and its ETag, version, or both. For GitHub, a revision is uniquely identified by its commit ID. This guide also contains information to help you get details about the instances in your deployments and to make on-premises instances available for AWS CodeDeploy deployments. AWS CodeDeploy Information Resources AWS CodeDeploy User Guide (http://docs.aws.amazon.com/codedeploy/latest/userguide) AWS CodeDeploy API Reference Guide (http://docs.aws.amazon.com/codedeploy/latest/APIReference/) AWS CLI Reference for AWS CodeDeploy (http://docs.aws.amazon.com/cli/latest/reference/deploy/index.html) AWS CodeDeploy Developer Forum (https://forums.aws.amazon.com/forum.jspa?forumID=179) See https://docs.aws.amazon.com/goto/WebAPI/codedeploy-2014-10-06 for more information on this service. See codedeploy package documentation for more information. https://docs.aws.amazon.com/sdk-for-go/api/service/codedeploy/ To AWS CodeDeploy with the SDK use the New function to create a new service client. With that client you can make API requests to the service. These clients are safe to use concurrently. See the SDK's documentation for more information on how to use the SDK. https://docs.aws.amazon.com/sdk-for-go/api/ See aws.Config documentation for more information on configuring SDK clients. https://docs.aws.amazon.com/sdk-for-go/api/aws/#Config See the AWS CodeDeploy client CodeDeploy for more information on creating client for this service. https://docs.aws.amazon.com/sdk-for-go/api/service/codedeploy/#New
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)