Mock sample for your project: Giphy API

Icons for Everything

The destination for current and historic NBA statistics.

API v3 targets v2 functionality with a few minor additions. The API is accessible via https://api.thetvdb.com and provides the following REST endpoints in JSON format.
How to use this API documentation
You may browse the API routes without authentication, but if you wish to send requests to the API and see response data, then you must authenticate.
Obtain a JWT token by POSTing to the /login route in the Authentication section with your API key and credentials.
Paste the JWT token from the response into the "JWT Token" field at the top of the page and click the 'Add Token' button.
You will now be able to use the remaining routes to send requests to the API and get a response.
Language Selection
Language selection is done via the Accept-Language header. At the moment, you may only pass one language abbreviation in the header at a time. Valid language abbreviations can be found at the /languages route..
Authentication
Authentication to use the API is similar to the How-to section above. Users must POST to the /login route with their API key and credentials in the following format in order to obtain a JWT token.
{"apikey":"APIKEY","username":"USERNAME","userkey":"USERKEY"}
Note that the username and key are ONLY required for the /user routes. The user's key is labled Account Identifier in the account section of the main site.
The token is then used in all subsequent requests by providing it in the Authorization header. The header will look like: Authorization: Bearer . Currently, the token expires after 24 hours. You can GET the /refresh_token route to extend that expiration date.
Versioning
You may request a different version of the API by including an Accept header in your request with the following format: Accept:application/vnd.thetvdb.v$VERSION. This documentation automatically uses the version seen at the top and bottom of the page.

Notes
Tutorial demo using this API is at https://spinitron.com/v2-api-demo/. For web integration using iframes and/or JavaScript instead of an API, see https://spinitron.github.io/v2-web-integration/.
Your API key is found in the Spinitron web app. Log in to Spinitron and go to Automation & API in the Admin menu.
Authenticate by presenting your API key using either HTTP Bearer Authorization
(preferred)
curl -H 'Authorization: Bearer YOURAPIKEY' 'https://spinitron.com/api/spins'
or in the query parameter access-token (less secure owing to webserver
log files)
curl 'https://spinitron.com/api/spins?access-token=YOURAPIKEY'
Limit per page of results is 20 by default and miximally 200.
Try it out below works to
generate example cURL requests but not to get responses from Spinitron. We
do not accept queries sent from web browsers. Copy-paste the cURL commands
and run them from your computer.
Cache the data you get from the API if you are using it in web or mobile integration. It's not ok to query the API on every page request you serve. The demo shows how easy it can be to implement a file cache.
An extension to this API with access to all stations for partner applications is available. Contact us.

The Books API provides information about book reviews and The New York Times bestsellers lists.

This API provides cacheable and straightforward access to Wikimedia content and data, in machine-readable formats.
Global Rules
Limit your clients to no more than 200 requests/s to this API.
Each API endpoint's documentation may detail more specific usage limits.
Set a unique User-Agent or Api-User-Agent header that
allows us to contact you quickly. Email addresses or URLs
of contact pages work well.
By using this API, you agree to Wikimedia's Terms of Use and Privacy Policy. Unless otherwise specified in the endpoint documentation below, content accessed via this API is licensed under the CC-BY-SA 3.0 and GFDL licenses, and you irrevocably agree to release modifications or additions made through this API under these licenses. See https://www.mediawiki.org/wiki/REST_API for background and details.
Endpoint documentation
Please consult each endpoint's documentation for details on:
Licensing information for the specific type of content
and data served via the endpoint.
Stability markers to inform you about development status and
change policy, according to
our API version policy.
Endpoint specific usage limits.

The Semantic API complements the Articles API. With the Semantic API, you get access to the long list of people, places, organizations and other locations, entities and descriptors that make up the controlled vocabulary used as metadata by The New York Times (sometimes referred to as Times Tags and used for Times Topics pages).
The Semantic API uses concepts which are, by definition, terms in The New York Times controlled vocabulary. Like the way facets are used in the Articles API, concepts are a good way to uncover articles of interest in The New York Times archive, and at the same time, limit the scope and number of those articles. The Semantic API maps to external semantic data resources, in a fashion consistent with the idea of linked data. The Semantic API also provides combination and relationship information to other, similar concepts in The New York Times controlled vocabulary.

Shotstack is a video, image and audio editing service that allows for the automated generation of videos, images and audio using JSON and a RESTful API.
You arrange and configure an edit and POST it to the API which will render your media and provide a file location when complete.
For more details visit shotstack.io or checkout our getting started documentation.
There are two main API's, one for editing and generating assets (Edit API) and one for managing hosted assets (Serve API).
The Edit API base URL is: https://api.shotstack.io/{version}
The Serve API base URL is: https://api.shotstack.io/serve/{version}

The Archive API provides lists of NYT articles by month going back to 1851. You can use it to build your own local database of NYT article metadata.

Dig into our logoraisr API reference documentation. We also offer an OpenAPI specification to allow easy integration into your systems. You can download the json file by clicking on the download button. OpenAPI 2.0 Validation Status