MRZ Scanner API

The MRZ Scanner API enables efficient scanning of Machine Readable Zones (MRZ) from various travel documents such as passports, visas, and ID cards. With the PresentID MRZ Detection API, developers can easily locate and extract MRZ information from a single input image, streamlining document processing and verification workflows.

About the API:

The MRZ Scanner API, powered by PresentID, offers a powerful solution for scanning Machine Readable Zones (MRZ) from various travel documents such as passports, visas, and ID cards. With the ability to localize and recognize the MRZ or Machine Readable Travel Document (MRTD) from a single input image, this API simplifies the process of extracting crucial information from travel documents.

Gone are the days of manually typing in lengthy passport or ID card details. The MRZ Scanner API automates the data extraction process, saving valuable time and minimizing errors. By providing an input image of the travel document, developers can seamlessly integrate this API into their applications, enabling efficient and accurate MRZ scanning.

The core functionality of the MRZ Scanner API lies in its ability to localize and identify the MRZ within the document image. The Machine Readable Zone, located at the bottom of the document, contains important information such as the holder's name, passport or ID card number, nationality, and expiration date. By precisely detecting and recognizing this zone, the API can extract the relevant data, making it easily accessible for further processing and verification.

The MRZ Scanner API supports a wide range of document types, including passports, visas, and ID cards from various countries. It is designed to handle different MRZ formats and variations, ensuring compatibility with diverse travel documents across the globe. Whether it's a standard 2-line MRZ or a more complex 3-line MRZ, this API is equipped to accurately capture the required information.

The integration process is straightforward, thanks to the well-documented API endpoints and developer-friendly interface. With a simple API call, developers can send the document image and receive structured data containing the extracted MRZ information. This enables seamless integration into existing systems, such as identity verification platforms, e-gate solutions, or travel document management systems.

The MRZ Scanner API offers a wide range of use cases across industries. It can be utilized in border control and immigration systems for efficient traveler identification and verification. Additionally, it can assist in identity verification processes for customer onboarding in financial institutions, e-commerce platforms, or sharing economy applications. It can also enhance document management systems, facilitating streamlined data entry and reducing manual effort.

In conclusion, the MRZ Scanner API, powered by PresentID, provides a robust and efficient solution for scanning Machine Readable Zones from passports, visas, and ID cards. With its accurate localization and recognition capabilities, seamless integration, and compatibility with various document types, this API simplifies the extraction of MRZ information, enabling faster and more reliable document processing and identity verification workflows.

 

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

Pass the passport photo and receive the data extracted from the MRZ. 

 

What are the most common uses cases of this API?

  1. Border Control and Immigration: The MRZ Scanner API is invaluable for border control and immigration systems. It enables quick and accurate scanning of MRZ information from passports, visas, and ID cards, facilitating efficient traveler identification and verification processes at airports, land borders, and other entry points.

  2. Identity Verification: The API can be integrated into identity verification platforms, enabling seamless extraction of MRZ data for customer onboarding in financial institutions, fintech companies, sharing economy platforms, and other industries. It streamlines the verification process, reducing manual data entry and improving the overall user experience.

  3. Document Management Systems: Incorporating the MRZ Scanner API into document management systems simplifies data entry and improves accuracy. By automatically extracting MRZ information from scanned travel documents, it eliminates the need for manual typing, reducing errors and saving time for administrative tasks.

  4. Travel and Hospitality: The API finds utility in travel and hospitality industries, where efficient guest registration and check-in processes are essential. By swiftly scanning MRZ data from passports, the API streamlines the registration process, allowing hotels, airlines, and rental services to provide a seamless experience to their customers.

  5. Mobile Apps and Digital Services: Mobile applications and digital services that require MRZ scanning functionality can integrate the API to enhance their offerings. This includes travel apps, banking apps, and e-commerce platforms, where users can conveniently scan their travel documents using their mobile devices to facilitate transactions, verify identities, or access specialized services.

  6. Document Authentication: The MRZ Scanner API can aid in document authentication processes. By extracting and analyzing MRZ information, it enables organizations, such as law enforcement agencies, financial institutions, and notaries, to verify the authenticity of travel documents and detect potential fraud attempts.

 

Are there any limitations to your plans?

Besides API call limitations per month, there are no other limitations.

API Documentation

Endpoints


To use this endpoint you must specify the URL of an image in the parameter.



                                                                            
GET https://zylalabs.com/api/2095/mrz+scanner+api/6195/image+data+by+url
                                                                            
                                                                        

Image Data by URL - Endpoint Features

Object Description
url [Required]
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {
    "status": false,
    "errorCode": 404,
    "errorMessage": "There is no text in the image."
}
                                                                                                                                                                                                                    
                                                                                                    

Image Data by URL - CODE SNIPPETS


curl --location --request GET 'https://zylalabs.com/api/2095/mrz+scanner+api/6195/image+data+by+url?url=https://upload.wikimedia.org/wikipedia/commons/f/fa/Passport_card.jpg' --header 'Authorization: Bearer YOUR_API_KEY' 


    

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 MRZ Scanner 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 commitments. One click upgrade/downgrade or cancellation. No questions asked.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • 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

Each endpoint returns structured JSON data containing extracted MRZ information, including key details like the holder's name, passport or ID card number, nationality, and expiration date.

Key fields in the response data typically include "statusCode," "statusMessage," "hasError," and "data," where "data" contains the extracted MRZ details if successful.

The response data is organized in a JSON format, with a top-level object containing status indicators and a nested "data" object that holds the extracted MRZ information.

The primary parameter for the endpoints is the image input, either as a file upload or an image URL. Users must ensure the image meets size and dimension requirements.

Each endpoint provides access to MRZ data from travel documents, including personal identification details like name, document number, nationality, and validity dates.

Users can utilize the returned data for various applications, such as identity verification, document management, and automated data entry, enhancing efficiency and accuracy in processing.

Data accuracy is maintained through advanced image processing algorithms that detect and extract MRZ information, ensuring reliable results across various document types and formats.

Typical use cases include border control for traveler verification, identity checks in financial services, and streamlining guest registration in the travel and hospitality sectors.

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