Mock sample for your project: httpbin.org API
Integrate with "httpbin.org API" from httpbin.org in no time with Mockoon's ready to use mock sample
httpbin.org
Version: 0.9.2
Speed up your application development by using "httpbin.org API" ready-to-use mock sample. Mocking this API will help you accelerate your development lifecycles and allow you to stop relying on an external API to get the job done. No more API keys to provision, accesses to configure or unplanned downtime, just work.
Enhance your development infrastructure by mocking third party APIs during integrating testing.
Description
A simple HTTP Request & Response Service. Run locally: $ docker run -p 80:80 kennethreitz/httpbin
Other APIs in the same category
Interzoid Get Area Code API
This API provides area code information for a given telephone area code.
Request Baskets API
RESTful API of Request Baskets service.
Request Baskets is an open source project of a service to collect HTTP requests and inspect them via RESTful
API or web UI.
Check out the project page for more detailed description.
Request Baskets is an open source project of a service to collect HTTP requests and inspect them via RESTful
API or web UI.
Check out the project page for more detailed description.
Swagger Generator
swagger.io
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.
Interzoid Get Global Phone Number Information API
This API provides geographic information for a global telephone number, including city and country information, primary languages spoken, and mobile device identification.
JIRA 7.6.1
jira.local
WebScraping.AI
A client for https://webscraping.ai API. It provides a web scaping automation API with Chrome JS rendering, rotating proxies and builtin HTML parsing.
Custom Vision Training Client
microsoft.com
Image Search Client
microsoft.com
The Image Search API lets you send a search query to Bing and get back a list of relevant images. This section provides technical details about the query parameters and headers that you use to request images and the JSON response objects that contain them. For examples that show how to make requests, see Searching the Web for Images.
vRealize Network Insight API Reference
vmware.local
vRealize Network Insight API Reference
News Search Client
microsoft.com
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.
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.