Mock sample for your project: Musixmatch API
Integrate with "Musixmatch API" from musixmatch.com in no time with Mockoon's ready to use mock sample
Musixmatch API
Version: 1.1.0
Integrate third-party APIs faster by using "Musixmatch API" ready-to-use mock sample. Mocking this API will help you accelerate your development lifecycles and improves your integration tests' quality and reliability by accounting for random failures, slow response time, etc.
It also helps reduce your dependency on third-party APIs: no more accounts to create, API keys to provision, accesses to configure, unplanned downtime, etc.
Description
Musixmatch lyrics API is a robust service that permits you to search and retrieve lyrics in the simplest possible way. It just works.
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
Other APIs in the same category
Medium.com - Unofficial API Spec
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
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
SoundCloud Public API Specification
Wowza Streaming Cloud REST API Reference Documentation
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):
Secret Manager API
Chrome Verified Access API
Service Consumer Management API
Cloud Document AI API
