Mock sample for your project: Contribly API

API for GNU Social-compatible microblogging server

What is the Bandsintown API?
The Bandsintown API is designed for artists and enterprises representing artists.
It offers read-only access to artist info and artist events:
artist info: returns the link to the Bandsintown artist page, the link to the artist photo, the current number of trackers and more
artist events: returns the list of events including their date and time, venue name and location, ticket links, lineup, description and the link to the Bandsintown event page
Note you can specify if you only want to return upcoming events, past events, all events, or events within a given date range.
Getting Started
In order to use the Bandsintown API, you must read and accept our Terms and Conditions below and you must have written consent from Bandsintown Inc. Any other use of the Bandsintown API is prohibited. Contact Bandsintown to tell us what you plan to do and request your personal application ID.
Find out about the API methods available and the format of the API responses below. Select the method you wish to use and try it out online with the app ID provided to you.
Call our Bandsintown API with the app ID provided straight from your website or back-end platform and choose which element of the API response you wish to display. Scroll to the bottom of this page to find out about the Models used.

Social media management for marketers and agencies

Description of Instagram RESTful API.
Current limitations:
Instagram service does not support cross origin headers
for security reasons, therefore it is not possible to use Swagger UI and make API calls directly from browser.
Modification API requests (POST, DELETE) require additional security scopes
that are available for Apps created on or after Nov 17, 2015 and
started in Sandbox Mode.
Consider the Instagram limitations for API calls that depends on App Mode.
Warning: For Apps created on or after Nov 17, 2015 API responses
containing media objects no longer return the data field in comments and likes nodes.
Last update: 2015-11-28

RiteKit API is based on REST principles.
Authentication uses standard OAuth 2.0 process
##Getting started
Sign up for RiteKit
Go to developer dashboard
Click "Create a token" button to get your Client ID and Client secret
When you reach your free limit of calls per month, upgrade to paid tiers
Options for authorizing API Calls
Using Client ID directly
You can directly connect to our API using your client ID by sending it as a GET query parameter. This option is simple (no need for oAuth) but it should be used only in case the Client ID is not exposed publicly.
GET https://api.ritekit.com/v1/stats/multiple-hashtags?tags=php&client_id=292c6912e7710c838347ae178b4a

The spoonacular Nutrition, Recipe, and Food API allows you to access over 380,000 recipes, thousands of ingredients, 80,000 food products, and 100,000 menu items. Our food ontology and semantic recipe search engine makes it possible to search for recipes using natural language queries, such as "gluten free brownies without sugar" or "low fat vegan cupcakes." You can automatically calculate the nutritional information for any recipe, analyze recipe costs, visualize ingredient lists, find recipes for what's in your fridge, find recipes based on special diets, nutritional requirements, or favorite ingredients, classify recipes into types and cuisines, convert ingredient amounts, or even compute an entire meal plan. With our powerful API, you can create many kinds of food and especially nutrition apps.
Special diets/dietary requirements currently available include: vegan, vegetarian, pescetarian, gluten free, grain free, dairy free, high protein, whole 30, low sodium, low carb, Paleo, ketogenic, FODMAP, and Primal.

Clubhouse API

This is the REST API for trashnothing.com.
To learn more about the API or to register your app for use with the API
visit the trash nothing Developer page.
NOTE: All date-time values are UTC
and are in ISO 8601 format (eg. 2019-02-03T01:23:53).

API Reference: The StatSocial API is organized around REST. Our API is designed to have predictable, resource-oriented URLs and to use HTTP response codes to indicate API errors. We use built-in HTTP features, like HTTP authentication and HTTP verbs, which can be understood by off-the-shelf HTTP clients, and we support cross-origin resource sharing to allow you to interact securely with our API from a client-side web application (remember that you should never expose your secret API key in any public website's client-side code). JSON will be returned in all responses from the API, including errors (though if you're using API bindings, we will convert the response to the appropriate language-specific object). Contact [email protected] to obtain a test API key