Mock sample for your project: ART19 Content API Documentation
Integrate with "ART19 Content API Documentation" from art19.com in no time with Mockoon's ready to use mock sample
ART19 Content API Documentation
art19.com
Version: 1.0.0
Speed up your application development by using "ART19 Content API Documentation" 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
The ART19 Content API conforms to the JSON:API specification.
API requests MUST use the HTTP Accept header:
Accept: application/vnd.api+json
API requests MUST be authenticated using the HTTP Authorization header:
Authorization: Token token="your-token", credential="your-credential"
General Notes
Some query parameters use unencoded [ and ] characters simply for readability. Defaults, examples, and
possible values are additionally rendered in double quotes for readability. In practice, query parameters should
not have quotes around the values (e.g., foo=bar is valid, not foo="bar"), and both query parameter keys
and values must be percent-encoded, per the requirements in RFC 3986 § 3.4.
Rate Limiting
In order to provide a fair distribution of available resources, all API calls are subject to rate limits.
If you exceed the number of API calls per minute granted to your credential, a 429 Too Many Requests
error response will be returned.
In that case, a Retry-After header MAY be included in the response, describing the number of seconds
after which a request can be retried.
If you run into a high number of 429 errors, please reach out to ART19 Support to adjust your rate limit.
Example
In the following example the request can be retried after waiting for 21 seconds:
HTTP/1.1 429 Too Many Requests
Content-Type: text/html
Retry-After: 21
Pagination
Requests to collection endpoints SHOULD provide pagination parameters.
Some endpoints REQUIRE pagination parameters to be provided.
Whenever pagination is provided, it MUST be valid.
Failing to provide pagination when it is required or providing wrong or incomplete pagination
always results in a 400 Bad Request error response.
The page numbering starts with 1 and the maximum page size (if not otherwise documented
on an endpoint) is 100. Pagination MUST NOT be specified if requesting a list of IDs (using an ids[] parameter).
Providing invalid values for page number or page size, as well as providing only a page number or only a page size,
is considered an error. Pagination is provided like this:
page[number]=1&page[size]=25
Responses conform to the JSON:API specification's pagination section
by including pagination links. Your requested page size will be carried into the pagination links.
Sorting
Requests to collection endpoints usually accept a sort parameter. Please refer to the
JSON:API Specification's sorting section for further details.
Relationship Linking
Currently, resources return all of their relationships, in no particular order, pursuant to how relationships
should be returned according to the JSON:API specification. Consumers of this API
MUST NOT make assumptions about the order of these collections. Even though this data is not currently paginated, consumers MUST support
paginating relationships per the JSON:API specification if this data is important for their application.
Other APIs in the same category
Books API
Movie Reviews API
Spotify Web API
Musixmatch API
Include millions of licensed lyrics on your website or in your application legally.
The fastest, most powerful and legal way to display lyrics on your website or in your application.
Read musixmatch API Terms & Conditions and the Privacy Policy:
Before getting started, you must take a look at the API Terms & Conditions and the Privacy Policy. We’ve worked hard to make this service completely legal so that we are all protected from any foreseeable liability. Take the time to read this stuff.
Register for an API key:
All you need to do is register in order to get your API key, a mandatory parameter for most of our API calls. It’s your personal identifier and should be kept secret:
Integrate the musixmatch service with your web site or application
In the most common scenario you only need to implement two API calls:
The first call is to match your catalog to ours using the track.search function and the second is to get the lyrics using the track.lyrics.get api. That’s it!
API Methods
What does the musiXmatch API do?
The musiXmatch API allows you to read objects from our huge 100% licensed lyrics database.
To make your life easier we are providing you with one or more examples to show you how it could work in the wild. You’ll find both the API request and API response in all the available output formats for each API call. Follow the links below for the details.
The current API version is 1.1, the root URL is located at https://api.musixmatch.com/ws/1.1/
Supported input parameters can be found on the page Input Parameters. Use UTF-8 to encode arguments when calling API methods.
Every response includes a status_code. A list of all status codes can be consulted at Status Codes.
Music meta data
The musiXmatch api is built around lyrics, but there are many other data we provide through the api that can be used to improve every existent music service.
Track
Inside the track object you can get the following extra information:
TRACK RATING
The track rating is a score 0-100 identifying how popular is a song in musixmatch.
You can use this information to sort search results, like the most popular songs of an artist, of a music genre, of a lyrics language.
INSTRUMENTAL AND EXPLICIT FLAGS
The instrumental flag identifies songs with music only, no lyrics.
The explicit flag identifies songs with explicit lyrics or explicit title. We're able to identify explicit words and set the flag for the most common languages.
FAVOURITES
How many users have this song in their list of favourites.
Can be used to sort tracks by num favourite to identify more popular tracks within a set.
MUSIC GENRE
The music genere of the song.
Can be used to group songs by genre, as input for similarity alghorithms, artist genre identification, navigate songs by genere, etc.
SONG TITLES TRANSLATIONS
The track title, as translated in different lanauages, can be used to display the right writing for a given user, example:
LIES (Bigbang) becomes 在光化門 in chinese
HALLELUJAH (Bigbang) becomes ハレルヤ in japanese
Artist
Inside the artist object you can get the following nice extra information:
COMMENTS AND COUNTRY
An artist comment is a short snippet of text which can be mainly used for disambiguation.
The artist country is the born country of the artist/group
There are two perfect search result if you search by artist with the keyword "U2". Indeed there are two distinct music groups with this same name, one is the most known irish group of Bono Vox, the other is a less popular (world wide speaking) group from Japan.
Here's how you can made use of the artist comment in your search result page:
U2 (Irish rock band)
U2 (あきやまうに)
You can also show the artist country for even better disambiguation:
U2 (Irish rock band) from Ireland
U2 (あきやまうに) from Japan
ARTIST TRANSLATIONS
When you create a world wide music related service you have to take into consideration to display the artist name in the user's local language. These translation are also used as aliases to improve the search results.
Let's use PSY for this example.
Western people know him as PSY but korean want to see the original name 싸이.
Using the name translations provided by our api you can show to every user the writing they expect to see.
Furthermore, when you search for "psy gangnam style" or "싸이 gangnam style" with our search/match api you will still be able to find the song.
ARTIST RATING
The artist rating is a score 0-100 identifying how popular is an artist in musixmatch.
You can use this information to build charts, for suggestions, to sort search results. In the example above about U2, we use the artist rating to show the irish band before the japanese one in our serp.
ARTIST MUSIC GENRE
We provide one or more main artist genre, this information can be used to calculate similar artist, suggestions, or the filter a search by artist genre.
Album
Inside the album object you can get the following nice extra information:
ALBUM RATING
The album rating is a score 0-100 identifying how popular is an album in musixmatch.
You can use this information to sort search results, like the most popular albums of an artist.
ALBUM RATING
The album rating is a score 0-100 identifying how popular is an album in musixmatch.
You can use this information to sort search results, like the most popular albums of an artist.
ALBUM COPYRIGHT AND LABEL
For most of our albums we can provide extra information like for example:
Label: Universal-Island Records Ltd.
Copyright: (P) 2013 Rubyworks, under license to Columbia Records, a Division of Sony Music Entertainment.
ALBUM TYPE AND RELEASE DATE
The album official release date can be used to sort an artist's albums view starting by the most recent one.
Album can also be filtered or grouped by type: Single, Album, Compilation, Remix, Live. This can help to build an artist page with a more organized structure.
ALBUM MUSIC GENRE
For most of the albums we provide two groups of music genres. Primary and secondary. This information can be used to help user navigate albums by genre.
An example could be:
Primary genere: POP
Secondary genre: K-POP or Mandopop
Peel Tune-in API
Books API
Times Newswire API
Wikimedia
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.
TheTVDB API v3
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.
Image Moderation
