Mock sample for your project: Airbyte Configuration API

User Recommendation Engine and Chat Network

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

Admin API of the Otoroshi reverse proxy

Stack Exchange is a network of 130+ Q&A communities including Stack Overflow.

Containers are virtual software objects that include all the elements that an app needs to run. A container has the benefits of resource isolation and allocation but is more portable and efficient than, for example, a virtual machine.
This documentation describes the IBM Containers API, which is based on the Docker Remote API. The API provides endpoints that you can use to create and manage your single containers and container groups in Bluemix. Endpoints are summarized under the following tags:
Authentication: Retrieve and refresh your TLS certificates.
Private Docker images registry: Create your own private Docker images registry in Bluemix by setting a namespace for your organization.
Images: View, build, and push your images to your private Bluemix registry so you can use them with IBM Containers. You can also scan your container images with the Vulnerability Advisor against standard policies set by the organization manager and a database of known Ubuntu issues.
Single Containers: Create and manage single containers in Bluemix. Use a single container to implement short-lived processes or to run simple tests as you develop an app or service. To make your single container available from the internet, review the Public IP addresses endpoints.
Container Groups: Create and manage your container groups in Bluemix. A container group consists of multiple single containers that are all created from the same container image and as a consequence are configured in the same way. Container groups offer further options at no cost to make your app highly available. These options include in-built load balancing, auto-recovery of unhealthy container instances, and auto-scaling of container instances based on CPU and memory usage. Map a public route to your container group to make your app accessible from the internet.
Public IP addresses: Use these endpoints to request public IP addresses for your space. You can bind this IP address to your container to make your container accessible from the internet.
File shares: Create, list and delete file shares in a space. A file share is a NFS storage system that hosts Docker volumes.
Volumes: Create and manage container volumes in your space to persist the data of your containers.
Each API request requires an HTTP header that includes the 'X-Auth-Token’ and 'X-Auth-Project-Id’ parameter.
X-Auth-Token: The JSON web token (JWT) that you receive when logging into the Bluemix platform. It allows you to use the IBM Containers REST API, access services, and resources. Run cf oauth-token to retrieve your access token information.
X-Auth-Project-Id: The unique ID of your organization space where you want to create or work with your containers. Run cf space --guid, where is the name of your space, to retrieve your space ID.
For further information about how containers work in the IBM Containers service, review the documentation under https://new-console.ng.bluemix.net/docs/containers/container_index.html.

The API to manage the GameSparks game details

This API provides area code information for a given telephone number.

A simple HTTP Request & Response Service. Run locally: $ docker run -p 80:80 kennethreitz/httpbin

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.

This API provides a standard for US and international cities for the purposes of standardizing city name data, improving query results, analytics, and data merging.

API of the Patch application on cloud.redhat.com
Syntax of the filtername] query parameters is described in [Filters documentation

Introduction
The Shorten.rest API allows you to programmatically create short URLs (an 'alias') for longer URL (a 'destination').
Each alias you create can be used to redirect the end user (person clicking on the link) to one or more destination URLs
A default destination is always set and specific destinations can be set to redirect the end user to preferred destinations based on the user's geographical location (country) and device Operating System.
In order to use the Shorten.Rest URL Shortening API you can choose to bind your own branded domain, sub-domain or to use our default domain - Short.FYI
Destination Matching
When creating or editing a short URL ('alias') you can choose to specify a destination for each country and OS (Supported OSes list) combination.
When a user clicks on the short link, Shorten.rest will examine the end user's country (determined by User's IP) and OS (User agent) and match the most suitable destination for each user.
(*) If no destination is set for a specific request combination Shorten.rest will use the default destination that exists within each short URL
(**) BRANDED DOMAINS: If the requested alias does not exist in our database - Shorten.rest will redirect the user to the default fallback you set within your dashboard under the ‘Alias Not Found Page Url’ value for a custom domain.
(*) Operating System (OS) destinations are stronger than a country destination!
For example - if you have a custom landing page that is targeting people in the USA and a second landing page that is hyper focused for people who use iOS devices - a person clicking on your link in the USA that is on an iPhone will be redirected to the iOS landing page, while all other devices will be redirected to the USA landing page.
| OS | Country | Destination |
| :------------: |:---------------:| -----|
| iOS | | YourDestination.com/ios |
| | US | YourDestination.com/usa |
Shorten.rest will choose the YourDestination.com/ios url as the most suitable destination.
Branded Domain Attributes
When setting up your custom domain you can include optional metatags and snippets (Supported snippets list). These parameters (such as retargeting, tracking and conversion pixels) are populated and fired on click - at the time of the redirect.
By default the parameters you set in the domain setting will be included in all Short URLs associated with that domain.
You can always override the domain defaults for each URL by passing the appropriate variables when creating or updating a short URL
Setting a Custom string for an Alias (short.fyi/alias)
While creating a short URL you can specify which domain to use. You can choose to use your own branded domain or our default domain - Short.fyi.
Each Alias is unique within a domain they are related to. This means that if multiple accounts use you the same domain (for example short.fyi), if an alias is already taken you may not create a new destination for it.
That said - If you would like to use a specific alias which is already taken - the only way to do so is to create it on a new domain you own and have attached to your Shorten.rest account.
Random Aliases
By default - unless you specify a vanity URI for your alias each URL that is shortened on our platform will have a random string generated by the API. This means that if the 'alias' attribute of a /aliases POST request is not provided, or is an empty string, a random string of seven characters will be generated and returned as part of the POST response.
You can also place the @rnd macro within the alias field when you create a new alias, for example /vanity/@rnd, which might return an alias like /vanity/ZMAefRt, or /vanity@rnd, which might produce something like /vanityMRtvxadf. Only the first @rnd in an alias attribute will be replaced.
NOTES
( * ) All methods of the Shorten.REST API require that your API key be provided in x-api-key header.
(**) All API parameters are case sensitive