The "Lookup ISRC" endpoint returns detailed metadata for a specific track, including the title, artist, duration, ISRC code, and associated media links. The "Text Search and Download" endpoint provides similar metadata but allows users to search for tracks by title or artist, returning a list of matching results with their respective ISRC codes and download links.

Key fields in the response include "id" (unique identifier), "title" (track name), "artist" (performer), "duration" (length in seconds), "isrc" (International Standard Recording Code), and "versions" (available audio formats and links). These fields help identify and manage music tracks effectively.

The response data is structured as a JSON array of objects. Each object contains fields like "id," "title," "artist," and "versions." The "versions" field is an array itself, detailing different audio formats, their properties, and download URLs, allowing for easy access to various media types.

The "Lookup ISRC" endpoint provides comprehensive track details, including ISRC codes, artist information, and media links. The "Text Search and Download" endpoint offers similar data but focuses on search functionality, enabling users to find tracks by keywords and retrieve their metadata and download options.

The "Lookup ISRC" endpoint typically requires an ISRC code as a parameter to retrieve specific track data. The "Text Search and Download" endpoint allows parameters such as "title" and "artist" to customize search queries, enabling users to filter results based on their input.

Typical use cases include music distribution, rights management, and cataloging for independent artists and record labels. Users can efficiently retrieve ISRCs for their tracks, ensuring proper identification and compliance with copyright regulations, facilitating smoother music distribution across platforms.

Data accuracy is maintained through regular updates and quality checks from reliable music industry sources. The API aggregates information from established databases, ensuring that the ISRC codes and associated metadata reflect the most current and correct details for each track.

Users can utilize the returned data by integrating it into their music management systems or applications. For example, they can automate the cataloging process, ensure accurate rights management, and streamline music distribution by leveraging the detailed metadata and download links provided in the API responses.

The Instant ISRC Download API primarily covers global music tracks, focusing on those registered with International Standard Recording Codes (ISRC). This includes a wide range of genres and artists, making it suitable for independent musicians, record labels, and distributors worldwide.

Users can customize their data requests by utilizing parameters such as "title" and "artist" in the "Text Search and Download" endpoint. This allows for targeted searches, enabling users to retrieve specific tracks or a list of tracks that match their criteria.

The "Lookup ISRC" endpoint accepts a valid ISRC code as a parameter. For the "Text Search and Download" endpoint, accepted values include strings for "title" and "artist," allowing for flexible search queries to find relevant tracks.

If the API returns partial or empty results, users should verify their search parameters for accuracy. Adjusting the search terms or using broader queries can help yield more results. Implementing error handling in the application can also improve user experience.

The API employs quality checks by aggregating data from reputable music industry sources, ensuring that ISRC codes and metadata are accurate and up-to-date. Regular audits and validation processes help maintain the integrity of the information provided.

Standard data patterns include consistent JSON structures with fields like "id," "title," "artist," and "isrc." Each track's metadata is organized in a predictable format, allowing developers to easily parse and utilize the information in their applications.

Key fields include "id" (unique track identifier), "title" (name of the track), "artist" (performer), "isrc" (International Standard Recording Code), and "versions" (available audio formats). Understanding these fields helps users effectively manage and catalog their music.

Users can utilize the download links in the "versions" field to access audio files in various formats. This enables seamless integration into music distribution platforms or applications, allowing for easy access to tracks for streaming or offline use.

The API supports various audio formats, including WebM with different bitrates. For example, the "versions" field in the response includes formats like "webm128" and "webm64," each with specific codec, bitrate, and size details, allowing users to choose the best format for their needs.

Users can access multiple ISRC codes for a track through the "isrc" field in the response. This field returns an array of ISRC codes, enabling users to manage different versions or releases of the same track efficiently.

Each track's response includes essential metadata such as "title," "artist," "duration," "isrc," and "versions." This comprehensive data allows users to identify tracks accurately and manage their music catalog effectively.

Users can refine their search results by using specific keywords in the "Text Search and Download" endpoint. By including the track's title or artist name, users can narrow down the results to find the exact tracks they need.

The "musicbrainz" field provides unique identifiers for various entities related to the track, such as album, artist, and recording. This information helps users link to additional metadata and enhances the track's cataloging and rights management.

The API provides detailed information about different versions of a track within the "versions" field. Each version includes format, codec, bitrate, and download URL, allowing users to access the most suitable audio quality for their applications.

Users should implement error handling in their applications to manage unexpected API responses. This includes checking for error codes or empty results and providing user-friendly messages or fallback options to enhance the user experience.

The "lyrics" field indicates whether lyrics are available for the track. Users can leverage this information to enhance their applications, such as displaying lyrics alongside audio playback, improving user engagement and experience.

Users can access different audio versions of a track through the "versions" field in the response. Each version includes details such as format, codec, bitrate, and a download URL, allowing users to select the best audio quality for their needs. For example, a track may have both "webm128" and "webm64" versions available.

The "musicbrainz" field contains unique identifiers for various entities related to the track, including album, artist, and recording IDs. This metadata allows users to link to more detailed information in the MusicBrainz database, enhancing cataloging and rights management.

The "lyrics" field in the response indicates whether lyrics are available for a track. If set to true, users can display the lyrics alongside audio playback in their applications, enhancing user engagement and providing a richer listening experience.

Users can combine search parameters in the "Text Search and Download" endpoint by including both "title" and "artist" in their queries. This allows for more refined searches, helping users find specific tracks that match both criteria effectively.

The Instant ISRC Download API aggregates data from reputable music industry sources, ensuring a wide range of tracks registered with ISRC codes are covered. This includes various genres and artists globally, making it suitable for diverse music distribution needs.

Users can choose from various audio formats listed in the "versions" field, such as "webm128" or "webm64." By selecting the appropriate format based on their application's requirements, users can ensure optimal playback quality and compatibility with their systems.

The "id" field serves as a unique identifier for each track, allowing users to reference specific recordings easily. This is particularly useful for tracking, cataloging, and managing music assets within applications or databases.

Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world's most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, refer to the 'X-Zyla-API-Calls-Monthly-Remaining' field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.

To see the maximum number of API requests your plan allows, check the 'X-Zyla-RateLimit-Limit' response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.

The 'X-Zyla-RateLimit-Reset' header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3,600, it means 3,600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it's important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.

Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.