Media Inspector API

The Media Inspector API enables users to analyze and examine multimedia files comprising images, videos, and audio. With this API, developers can easily identify and inspect the contents of these files, allowing for efficient processing and retrieval of media-related information.

About the API:

The Media Inspector API is a powerful tool designed to facilitate the identification and inspection of files that contain various forms of media, including images, videos, and audio. With its robust functionality and ease of integration, this API provides developers with the means to efficiently analyze and extract valuable information from multimedia files.

One of the key features of the Media Inspector API is its ability to identify the presence of different types of media within a file. By leveraging advanced algorithms and techniques, the API can accurately detect and categorize images, videos, and audio tracks, even within complex file structures. This allows developers to automate the identification process, saving valuable time and effort.

In addition to identification, the Media Inspector API offers comprehensive inspection capabilities. It provides detailed metadata extraction, enabling developers to access essential information about media files, such as resolution, duration, format, and codec details. This information can be crucial for various applications, ranging from media management systems to content recommendation engines.

The API also supports content analysis for images and videos. It can analyze images to extract features like dominant colors, object recognition, and facial detection. For videos, it can extract keyframes, detect scenes, and perform video analysis tasks like object tracking or activity recognition. These features open up possibilities for applications such as content moderation, visual search, or video content indexing.

Moreover, the Media Inspector API supports audio analysis. It can extract metadata from audio files, including information about the format, bitrate, and duration. Additionally, it offers capabilities for speech recognition, audio transcription, and audio fingerprinting, allowing developers to build applications that process and understand audio content.

The Media Inspector API is designed with developer-friendliness in mind. It provides a straightforward integration process, with clear documentation and code examples. Developers can easily incorporate the API into their applications, regardless of the programming language or environment they are working with.

In conclusion, the Media Inspector API is a versatile solution for identifying and inspecting files containing images, videos, and audio. By leveraging its powerful features, developers can automate the processing of multimedia files, extract valuable metadata, and perform advanced content analysis. This API opens up a wide range of possibilities for applications in fields such as media management, content recommendation, content moderation, and more.

 

What your API receives and what your API provides (input/output)?

Pass any file URL and receive its metadata. 

 

What are the most common uses cases of this API?

  1. Content Moderation: The Media Inspector API can be used for content moderation purposes. By analyzing images and videos, developers can automatically detect and flag inappropriate or offensive content, ensuring a safer user experience on platforms that rely on user-generated content.

  2. Media Management Systems: Media Inspector API can assist in media management systems by automatically categorizing and tagging files based on their content. This enables efficient organization and retrieval of media assets, making it easier for users to search and navigate through large collections of images, videos, and audio files.

  3. Visual Search: By extracting features such as dominant colors, object recognition, and facial detection from images, the Media Inspector API can power visual search functionality. Users can search for similar images or products by uploading an image, enabling enhanced search experiences in e-commerce platforms or image-based search engines.

  4. Video Content Indexing: The API's capabilities for scene detection and keyframe extraction make it valuable for video content indexing. By automatically generating metadata about different scenes or key moments within a video, developers can enable more efficient video browsing, navigation, and content recommendation.

  5. Audio Transcription and Analysis: The Media Inspector API's audio analysis features, including speech recognition and audio transcription, can be utilized in applications that deal with audio content. This can be particularly useful for transcription services, voice assistants, or applications that require extracting text from audio recordings, such as podcast platforms or call center analytics tools.

  6. Digital Asset Management: Organizations that handle a large volume of media assets can benefit from the Media Inspector API for digital asset management. By automatically extracting metadata and analyzing media files, it becomes easier to organize, search, and distribute media assets efficiently within the organization, streamlining workflows and reducing manual effort.

 

Are there any limitations to your plans?

Besides the number of API calls, there are no other limitations.

API Documentation

Endpoints


Inspects provided URL to identify media file. If a media file is identified, the media file's metadata as resolution, bit rate and duration will be returned.

 


                                                                            
POST https://zylalabs.com/api/2072/media+inspector+api/1854/get+media+information
                                                                            
                                                                        

Get Media Information - Endpoint Features

Object Description
Request Body [Required] Json
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"url":"https://beamcast.s3.amazonaws.com/example.mp4","status":"ok","timestamp":"2024-08-10T21:10:52.358984009Z","format":"mov,mp4,m4a,3gp,3g2,mj2","isMedia":true,"hasVideo":true,"hasAudio":false,"duration":"634.584","startTime":"0.000","size":"81920912","bitRate":1032751,"streams":[{"codecType":"video","codec":"h264","index":0,"width":640,"height":360,"frameRate":"24","frameRateRational":"24/1","displayAspectRatio":"16:9","sampleAspectRatio":"1:1","pixelFormat":"yuv420p","duration":"634.583","startTime":"0.000"}]}
                                                                                                                                                                                                                    
                                                                                                    

Get Media Information - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/2072/media+inspector+api/1854/get+media+information' --header 'Authorization: Bearer YOUR_API_KEY' 

--data-raw '{
    "url": "https://beamcast.s3.amazonaws.com/example.mp4"
}'

    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Media Inspector API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Custom Rate Limit
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

Media Inspector API FAQs

The Media Inspector API supports a wide range of file formats for images, videos, and audio, including popular formats such as JPEG, PNG, MP4, AVI, WAV, and MP3. For a comprehensive list of supported formats, please refer to the API documentation.

The Media Inspector API is primarily designed for batch processing and offline analysis of media files. While it provides fast and efficient processing, it may not be suitable for real-time applications that require immediate analysis or processing of media content. For real-time scenarios, alternative solutions or custom implementations may be more appropriate.

No, the Media Inspector API cannot extract metadata or analyze the contents of encrypted or DRM-protected media files. The API can only process and analyze media files that are in a readable and accessible format.

The Media Inspector API returns detailed metadata about the media file, including information such as format, resolution, duration, bit rate, and codec details. It also indicates whether the file contains video or audio streams.

Key fields in the response include "url" (media file URL), "status" (processing status), "format" (supported formats), "duration" (length of the media), "bitRate" (data rate), and "streams" (detailed stream information).

The response data is structured in JSON format, with a top-level object containing metadata fields. The "streams" field is an array that provides detailed information about each media stream, such as codec type and dimensions.

The endpoint provides information on media file characteristics, including whether it contains video or audio, its resolution, duration, bit rate, and codec details. It also identifies the media format and any streams present.

The primary parameter for the endpoint is the media file URL, which must be accessible for the API to analyze. Users can customize their requests by providing different media file URLs to retrieve specific metadata.

Users can leverage the returned metadata for various applications, such as organizing media files, implementing content moderation, or enhancing search functionalities. For example, the "duration" and "bitRate" fields can help optimize streaming quality.

Typical use cases include content moderation to detect inappropriate media, media management for organizing assets, visual search for finding similar images, and audio transcription for converting speech to text in applications like podcasts.

The Media Inspector API employs advanced algorithms for media analysis, ensuring high accuracy in identifying and extracting metadata. Regular updates and quality checks are implemented to maintain the reliability of the data provided.

General FAQs

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.


Related APIs


You might also like