Mock sample for your project: Stoplight API
Integrate with "Stoplight API" from stoplight.io in no time with Mockoon's ready to use mock sample
Stoplight
stoplight.io
Version: api-v1
Start working with "Stoplight API" right away by using this ready-to-use mock sample. API mocking can greatly speed up your application development by removing all the tedious tasks or issues: API key provisioning, account creation, unplanned downtime, etc.
It also helps reduce your dependency on third-party APIs and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
Description
Other APIs in the same category
JIRA 7.6.1
jira.local
Airbyte Configuration API
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.
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.
Custom Vision Training Client
microsoft.com
nic.at Domainfinder API Documentation
nic.at
LGTM API specification
lgtm.com
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.
/ (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.
httpbin.org
A simple HTTP Request & Response Service. Run locally: $ docker run -p 80:80 kennethreitz/httpbin
Api2Pdf - PDF Generation, Powered by AWS Lambda
Introduction
Api2Pdf is a powerful PDF generation API with no rate limits or file size constraints. Api2Pdf runs on AWS Lambda, a serverless architecture powered by Amazon to scale to millions of requests while being up to 90% cheaper than alternatives. Supports wkhtmltopdf, Headless Chrome, LibreOffice, and PDF Merge. You can also generate barcodes with ZXING (Zebra Crossing).
SDKs & Client Libraries
We've made a number of open source libraries available for the API
Python: https://github.com/api2pdf/api2pdf.python
.NET: https://github.com/api2pdf/api2pdf.dotnet
Nodejs: https://github.com/api2pdf/api2pdf.node
PHP: https://github.com/Api2Pdf/api2pdf.php
Ruby: (Coming soon)
Authorization
Create an account at portal.api2pdf.com to get an API key.
Authorize your API calls
GET requests, include apikey=YOUR-API-KEY as a query string parameter
POST requests, add Authorization to your header.
For more advanced usage and settings, see the API specification below.
Api2Pdf is a powerful PDF generation API with no rate limits or file size constraints. Api2Pdf runs on AWS Lambda, a serverless architecture powered by Amazon to scale to millions of requests while being up to 90% cheaper than alternatives. Supports wkhtmltopdf, Headless Chrome, LibreOffice, and PDF Merge. You can also generate barcodes with ZXING (Zebra Crossing).
SDKs & Client Libraries
We've made a number of open source libraries available for the API
Python: https://github.com/api2pdf/api2pdf.python
.NET: https://github.com/api2pdf/api2pdf.dotnet
Nodejs: https://github.com/api2pdf/api2pdf.node
PHP: https://github.com/Api2Pdf/api2pdf.php
Ruby: (Coming soon)
Authorization
Create an account at portal.api2pdf.com to get an API key.
Authorize your API calls
GET requests, include apikey=YOUR-API-KEY as a query string parameter
POST requests, add Authorization to your header.
For more advanced usage and settings, see the API specification below.
Swagger2OpenAPI Converter
Converter and validator for Swagger 2.0 to OpenAPI 3.0.x definitions
Dataflow Kit Web Scraper
Render Javascript driven pages, while we internally manage Headless Chrome and proxies for you.
Build a custom web scraper with our Visual point-and-click toolkit.
Scrape the most popular Search engines result pages (SERP).
Convert web pages to PDF and capture screenshots.
Authentication
Dataflow Kit API require you to sign up for an API key in order to use the API.
The API key can be found in the DFK Dashboard after free registration.
Pass a secret API Key to all API requests to the server as the api_key query parameter.
Build a custom web scraper with our Visual point-and-click toolkit.
Scrape the most popular Search engines result pages (SERP).
Convert web pages to PDF and capture screenshots.
Authentication
Dataflow Kit API require you to sign up for an API key in order to use the API.
The API key can be found in the DFK Dashboard after free registration.
Pass a secret API Key to all API requests to the server as the api_key query parameter.