Mock sample for your project: The Jira Cloud platform REST API

RESTful API 4 Unipacker

The REST API for LGTM provides data so that you can customize how you integrate LGTM analysis into your workflow. It includes the following resources:
/ (API root)—get version information or download the specification in OpenAPI format.
/projects (Projects)—list projects, get a summary of the current status for a project, or add new projects.
/analyses (Analyses)—get a summary of results, download all the alerts, or trigger analysis for a specific commit.
/codereviews (Code reviews)—trigger code review for a patch, and view the results.
/operations (Operations)—get information about long-running tasks, for example, analyses or code reviews that you've requested.
/snapshots (Snapshots)—download and upload databases representing a snapshot of a codebase.
/queryjobs (Query jobs)—submit queries to evaluate against existing projects, and download their results.
/system (System)—get information on the health or usage of the system.
For an overview and getting started topics, see API for LGTM.

Build custom integrations with the LaunchDarkly REST API

Catalog Inventory

This API enables you to convert an amount of one currency into another currency using current foreign exchange rates.

This API provides a similarity key used to match with other similar city name data, including for purposes of deduplication, fuzzy matching, or merging of datasets. A much higher match rate will be achieved by matching on the algorithmically generated similarity key rather than the data itself.

A client for https://webscraping.ai API. It provides a web scaping automation API with Chrome JS rendering, rotating proxies and builtin HTML parsing.

Airbyte Configuration API
https://airbyte.io.
This API is a collection of HTTP RPC-style methods. While it is not a REST API, those familiar with REST should find the conventions of this API recognizable.
Here are some conventions that this API follows:
All endpoints are http POST methods.
All endpoints accept data via application/json request bodies. The API does not accept any data via query params.
The naming convention for endpoints is: localhost:8000/{VERSION}/{METHODFAMILY}/{METHODNAME} e.g. localhost:8000/v1/connections/create.
For all update methods, the whole object must be passed in, even the fields that did not change.
Change Management:
The major version of the API endpoint can be determined / specified in the URL localhost:8080/v1/connections/create
Minor version bumps will be invisible to the end user. The user cannot specify minor versions in requests.
All backwards incompatible changes will happen in major version bumps. We will not make backwards incompatible changes in minor version bumps. Examples of non-breaking changes (includes but not limited to...):
Adding fields to request or response bodies.
Adding new HTTP endpoints.

This is an online swagger codegen server. You can find out more at https://github.com/swagger-api/swagger-codegen or on irc.freenode.net, #swagger.

The News Search API lets you send a search query to Bing and get back a list of news that are relevant to the search query. This section provides technical details about the query parameters and headers that you use to request news and the JSON response objects that contain them. For examples that show how to make requests, see Searching the web for news.