Mock sample for your project: Image Moderation API
Integrate with "Image Moderation API" from moderatecontent.com in no time with Mockoon's ready to use mock sample
Image Moderation
Version: 1.0.0
Speed up your application development by using "Image Moderation API" ready-to-use mock sample. Mocking this API will allow you to start working in no time. No more accounts to create, API keys to provision, accesses to configure, unplanned downtime, just work.
It also improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
Description
Our FREE API blocks images with nudity. Build from the ground up, accurate models, best in class support, great price.
Other APIs in the same category
Service Consumer Management API
Manages the service consumers of a Service Infrastructure service.
Medium.com - Unofficial API Spec
Medium’s unofficial API documentation using OpenAPI specification.
Official API
Official API document can also be viewed for most up to date API spec at https://github.com/Medium/medium-api-docs.
Developer Blog - Welcome to the Medium API
Official API
Official API document can also be viewed for most up to date API spec at https://github.com/Medium/medium-api-docs.
Developer Blog - Welcome to the Medium API
setlist.fm API
setlist.fm
The setlist.fm API has been designed to give you easy access to setlist data in order to build fancy websites and
other applications. Before starting to use the API, be sure to ...
... understand how setlist.fm works (the FAQ and the
Guidelines are a good starting point), ... read this documentation carefully and ... apply for an API key (link for logged in users only) - if
you're no registered user yet, then register first (it's free).
If this documentation isn't enough or if you've got other things you'd like to tell us about the API, visit the
API Forum.
Note that the setlist.fm API is, according to the API terms of
service, only free for non-commercial projects. If you're interested in using the API for commercial purposes,
contact us.
About this Service
This service provides methods to get both setlists and components of setlists such as artists, cities, countries or
venues.
Supported Content Types
The REST service currently supports XML (default) and JSON content.
To receive a JSON response, set the Accept
header to application/json.
Internationalization
(Please note that this is an experimental feature and does not work for all cities!)
Most of the featured methods honor the Accept-Language
header. This header is used for
localizing cities and countries. The default language is English (en), but you can provide any of the languages
Spanish (es), French (fr), German (de), Portuguese (pt), Turkish (tr), Italian (it) or Polish (pl).
E.g. if you search a setlist for a concert that took place in Vienna and you pass "de" as header, you'll
get"Wien, Österreich" instead of"Vienna, Austria".
This also works if you use a different language than the country's native language.
E.g. for a concert in New York, you'll get"Nueva York, Estados Unidos" instead of"New
York, United States" if you pass "es" as language.
API Keys
API keys ( application form) must be included in the request with
the x-api-key header.
Version History
Version
Docs
End of Service
1.0
Docs
0.1
December 31, 2017
other applications. Before starting to use the API, be sure to ...
... understand how setlist.fm works (the FAQ and the
Guidelines are a good starting point), ... read this documentation carefully and ... apply for an API key (link for logged in users only) - if
you're no registered user yet, then register first (it's free).
If this documentation isn't enough or if you've got other things you'd like to tell us about the API, visit the
API Forum.
Note that the setlist.fm API is, according to the API terms of
service, only free for non-commercial projects. If you're interested in using the API for commercial purposes,
contact us.
About this Service
This service provides methods to get both setlists and components of setlists such as artists, cities, countries or
venues.
Supported Content Types
The REST service currently supports XML (default) and JSON content.
To receive a JSON response, set the Accept
header to application/json.
Internationalization
(Please note that this is an experimental feature and does not work for all cities!)
Most of the featured methods honor the Accept-Language
header. This header is used for
localizing cities and countries. The default language is English (en), but you can provide any of the languages
Spanish (es), French (fr), German (de), Portuguese (pt), Turkish (tr), Italian (it) or Polish (pl).
E.g. if you search a setlist for a concert that took place in Vienna and you pass "de" as header, you'll
get"Wien, Österreich" instead of"Vienna, Austria".
This also works if you use a different language than the country's native language.
E.g. for a concert in New York, you'll get"Nueva York, Estados Unidos" instead of"New
York, United States" if you pass "es" as language.
API Keys
API keys ( application form) must be included in the request with
the x-api-key header.
Version History
Version
Docs
End of Service
1.0
Docs
0.1
December 31, 2017
Wowza Streaming Cloud REST API Reference Documentation
About the REST API
The Wowza Streaming Cloud TM REST API (application programming interface) offers complete programmatic control over live streams, transcoders, stream sources, and stream targets. Anything you can do in the Wowza Streaming Cloud UI can also be achieved by making HTTP-based requests to cloud-based servers through the REST API.
The Wowza Streaming Cloud REST API features cross-origin resource sharing, or CORS.
CORS is a W3C specification that provides headers in HTTP requests to enable a web server to safely make a network request to another domain.
In order to protect shared resources, the Wowza Streaming Cloud REST API is subject to limits. For details, see Wowza Streaming Cloud REST API limits.
About this documentation
This reference documentation is based on the open-source Swagger framework.
It allows you to view the operations, parameters, and request and reponse schemas for every resource. Request samples are presented in cURL (Shell) and JavaScript; some samples also include just the JSON object. Response samples are all JSON.
For more information and examples on using the Wowza Streaming Cloud REST API, see our library of Wowza Streaming Cloud REST API technical articles.
Query requirements
The Wowza Streaming Cloud REST API uses HTTP requests to retrieve data from cloud-based servers. Requests must contain proper JSON, two authentication keys, and the correct version number in the base path.
JSON
The Wowza Streaming Cloud REST API uses the JSON API specification to request and return data. This means requests must include the header Content-Type: application/json and must include a single resource object in JSON format as primary data.
Responses include HTTP status codes that indicate whether the query was successful. If there was an error, a description explains the problem so that you can fix it and try again.
Authentication
Requests to the Wowza Streaming Cloud REST API must be authenticated with two keys: an API key and an access key. Each key is a 64-character alphanumeric string that you can find on the API Access page in Wowza Streaming Cloud.
Use the wsc-api-key and wsc-access-key headers to authenticate requests, like this (in cURL):
The Wowza Streaming Cloud TM REST API (application programming interface) offers complete programmatic control over live streams, transcoders, stream sources, and stream targets. Anything you can do in the Wowza Streaming Cloud UI can also be achieved by making HTTP-based requests to cloud-based servers through the REST API.
The Wowza Streaming Cloud REST API features cross-origin resource sharing, or CORS.
CORS is a W3C specification that provides headers in HTTP requests to enable a web server to safely make a network request to another domain.
In order to protect shared resources, the Wowza Streaming Cloud REST API is subject to limits. For details, see Wowza Streaming Cloud REST API limits.
About this documentation
This reference documentation is based on the open-source Swagger framework.
It allows you to view the operations, parameters, and request and reponse schemas for every resource. Request samples are presented in cURL (Shell) and JavaScript; some samples also include just the JSON object. Response samples are all JSON.
For more information and examples on using the Wowza Streaming Cloud REST API, see our library of Wowza Streaming Cloud REST API technical articles.
Query requirements
The Wowza Streaming Cloud REST API uses HTTP requests to retrieve data from cloud-based servers. Requests must contain proper JSON, two authentication keys, and the correct version number in the base path.
JSON
The Wowza Streaming Cloud REST API uses the JSON API specification to request and return data. This means requests must include the header Content-Type: application/json and must include a single resource object in JSON format as primary data.
Responses include HTTP status codes that indicate whether the query was successful. If there was an error, a description explains the problem so that you can fix it and try again.
Authentication
Requests to the Wowza Streaming Cloud REST API must be authenticated with two keys: an API key and an access key. Each key is a 64-character alphanumeric string that you can find on the API Access page in Wowza Streaming Cloud.
Use the wsc-api-key and wsc-access-key headers to authenticate requests, like this (in cURL):
Geographic API
The Geographic API extends the Semantic API, using a linked data approach to enhance location concepts used in The New York Times' controlled vocabulary and data resources which combine them with the GeoNames database, an authoritative and free to use database of global geographical places, names and features.
Wikimedia
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.
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.
Image Moderation
Our FREE API blocks images with nudity. Build from the ground up, accurate models, best in class support, great price.
Jellyfin API
jellyfin.local
Zappiti Player API
zappiti.com
Move your app forward with the Zappiti Player API. Use http://your-player-ip:8990/ as base URL for your requests.
Spinitron v2 API
spinitron.com
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.
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.
Community API
Get access to comments from registered users on New York Times articles. NOTE: This API is deprecated.