API archive entry · source-reported
Musixmatch API
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: ``` https://api.musixmatch.com/ws/v1.1/track.get?apikey=YOUR_API_KEY ``` #### 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’
Documentation & source
Use the provider’s reference for current endpoints, setup, limits and terms.
No separate documentation URL has been confirmed for this record.
Provider content retains its own terms. This listing does not grant reuse or training rights.
Access at a glance
These are reported access facts. Check the current documentation before integrating.
- Authentication: Unknown.
- HTTPS: not confirmed.
- Browser access (CORS): Unknown.
Pricing and limits
Current plans, quotas, and rate limits have not been reviewed for this listing. Check the provider’s current terms; no authentication does not necessarily mean free usage.
Documentation and sources
Imported from APIs.guru OpenAPI Directory. A detailed editorial review has not been published yet.
APIs.guru OpenAPI Directory · CC0 contributed definitions; upstream provider terms may differ
More Media APIs
Aggregators API Service
Aggregators API
Unknown · HTTPS unconfirmed · CORS Unknown
API docs | logoraisr.com
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
Unknown · HTTPS unconfirmed · CORS Unknown
api.video
api.video is an API that encodes on the go to facilitate immediate playback, enhancing viewer streaming experiences across multiple devices and platforms. You can stream live or on-demand online videos within minutes.
Unknown · HTTPS unconfirmed · CORS Unknown
APOD
This endpoint structures the APOD imagery and associated metadata so that it can be repurposed for other applications. In addition, if the concept_tags parameter is set to True, then keywords derived from the image explanation are returned. These keywords could be used as auto-generated hashtags for twitter or instagram feeds; but generally help with discoverability of relevant imagery
Unknown · HTTPS unconfirmed · CORS Unknown
Archive API
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.
Unknown · HTTPS unconfirmed · CORS Unknown
ART19 Content API Documentation
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 adjus
Unknown · HTTPS unconfirmed · CORS Unknown
Source reference
This page separates source-reported facts from questions that need live provider verification.