The Japanese Driving License OCR API is a powerful tool designed to extract crucial information from Japanese driver's licenses. With its advanced optical character recognition (OCR) capabilities, this API enables the extraction of six critical fields: name, residence, birthday, delivery date, expiration date, and personal number. It offers support for various image formats, including jpg, png, BMP, pdf, tiff, and single frame gif, making it versatile and adaptable to different types of driver's license images.
The extraction of information from a Japanese driver's license can be a time-consuming and error-prone process when done manually. However, with the Japanese Driving License OCR API, this task becomes automated, accurate, and efficient. By passing a digital copy of a driver's license image to the API, developers can retrieve the essential fields quickly and reliably.
The API's OCR technology is trained specifically to handle Japanese driver's licenses, ensuring accurate recognition of characters and efficient extraction of information. It precisely identifies and extracts the name of the license holder, their residence address, date of birth, delivery date (the date the license was issued), expiration date (the date when the license expires), and personal number (a unique identifier associated with the license holder).
The flexibility of the Japanese Driving License OCR API is further enhanced by its support for various image formats and sizes. It can process images in popular formats such as jpg, png, BMP, pdf, tiff, and even single-frame gif files. Additionally, the API can handle images with a file size of up to 10MB, allowing for seamless integration with different systems and workflows.
Integrating the Japanese Driving License OCR API into applications, websites, or systems is straightforward. Developers can make HTTP requests to the API, passing the driver's license image as input. The API then performs the OCR analysis on the image, accurately extracting the six critical fields. The extracted information is returned in a structured format, such as JSON or XML, enabling easy integration and further processing.
The Japanese Driving License OCR API finds applications in various industries and scenarios. It can be used by car rental companies to streamline the process of collecting customer information by automatically extracting relevant data from driver's licenses. Additionally, government agencies or transportation services can utilize the API to automate data entry tasks, ensuring accuracy and efficiency in license verification processes.
Furthermore, the Japanese Driving License OCR API can be beneficial in data analysis and record-keeping tasks. By extracting key details from driver's licenses, organizations can maintain accurate and up-to-date databases, facilitate data analysis, and improve decision-making processes.
In conclusion, the Japanese Driving License OCR API provides a powerful solution for extracting critical information from Japanese driver's licenses. With support for multiple image formats and a maximum file size of 10MB, this API offers flexibility and convenience. Automating the extraction process saves time, reduces errors, and enhances efficiency in various industries and applications that deal with driver's license data.
Pass the image from the Japanese driving license and receive the structured data.
Car Rental Services: Car rental companies can utilize the Japanese Driving License OCR API to streamline their rental process. By automatically extracting essential information from driver's licenses, such as the customer's name, address, and license expiration date, rental companies can expedite the check-in process and ensure accurate customer data.
Identity Verification: The API can be integrated into identity verification systems, allowing businesses to validate the authenticity of Japanese driver's licenses. By extracting and comparing critical fields such as the name, address, and personal number, organizations can verify the identity of individuals during onboarding or account registration processes.
Government Agencies: Government agencies responsible for license verification or compliance checks can leverage the API to automate data extraction from driver's licenses. This helps streamline processes related to license renewal, traffic violation records, or other official procedures, improving accuracy and efficiency.
Transportation Services: Transportation services such as ride-hailing or delivery companies can use the API to verify driver's license information of their drivers. By automatically extracting key details like the driver's name, address, and license validity, these services can ensure that their drivers possess valid licenses and meet regulatory requirements.
Age Verification: Businesses that require age verification, such as establishments selling age-restricted products or services, can utilize the API to verify the age of individuals by extracting their birthdate from driver's licenses. This helps ensure compliance with age-related regulations and prevents underage access to restricted goods or services.
KYC (Know Your Customer) Compliance: Financial institutions and online platforms can employ the API to facilitate KYC processes. By automatically extracting customer information from driver's licenses, organizations can enhance their identity verification procedures, comply with regulatory requirements, and prevent fraudulent activities.
These use cases demonstrate the diverse applications of the Japanese Driving License OCR API across different industries and scenarios. By automating data extraction from driver's licenses, the API enables organizations to improve operational efficiency, enhance customer experiences, and ensure compliance with various regulations.
Besides the number of API calls, there are no other limitations.
To use this endpoint you must indicate the URL of an image in the parameter.
It will also have a parameter where you can indicate if you want to get the paragraphs (true or false).
Get Data - Endpoint Features
| Object | Description |
|---|---|
url |
[Required] |
paragraphs |
[Required] |
{
"status": true,
"text": "\u6c0f\u540d \u6b66\u7f8e\u7f8e\u7f8e\n\u662d\u548c40\u5e741\u670801\u65e5\u751f\n\u4f4f\u6240 \u5317\u6d77\u9053\u5ba4\u862d\u5e02\u8f2a\u897f\u753a1\u4e01\u76ee\n\u4ea4\u4ed8 \u5e73\u621020\u5e7401\u670801\u65e5 85548\n\u5e73\u621030\u5e7401\u670801\u65e5\u6709\u6548\n\u514d\u8a31\u306e\u773c\u93e1\u7b49\n\u6761\u4ef6\u7b49 \u4e2d\u578b\u8eca\u4e2d\u578b\u8eca(8)(\u9650\n\u904b\u8ee2\u514d\u8a31\u8a3c\n\u512a\u826f\n\u300c \u756a\u53f7 \u7b2c100022228888 \u53f7\n\u4e00\u5927\u7279\u4e8c\nI\n\u5927\u578b -\n\u7a2e\n\u985e\n\u4e8c\u5c0f \u5e73\u621000\u5e7400\u670800\u65e5\n\u5176\u4ed6 \u662d\u548c27\u5e7402\u670829\u65e5\n\u4e8c\u5e73\u621000\u5e7400\u670800\u65e5\n\u5343\u8449\u770c\n\u516c\u5b89\u59d4\u54e1\u4f1a",
"boxCoordinates": [
0.7516666666666667,
0.8366336633663366,
0.10666666666666667,
0.034653465346534656
],
"paragraphs": [
{
"text": "\u6c0f\u540d \u6b66\u7f8e\u7f8e\u7f8e",
"words": [
{
"text": "\u6c0f",
"boxCoordinates": [
0.1025,
0.12623762376237624,
0.021666666666666667,
0.0297029702970297
]
},
{
"text": "\u540d",
"boxCoordinates": [
0.12166666666666667,
0.12376237623762376,
0.02,
0.0297029702970297
]
},
{
"text": "\u6b66",
"boxCoordinates": [
0.21916666666666668,
0.12995049504950495,
0.035,
0.04702970297029703
]
},
{
"text": "\u7f8e",
"boxCoordinates": [
0.29,
0.12995049504950495,
0.03666666666666667,
0.04702970297029703
]
},
{
"text": "\u7f8e",
"boxCoordinates": [
0.3883333333333333,
0.12995049504950495,
0.03666666666666667,
0.04702970297029703
]
},
{
"text": "\u7f8e",
"boxCoordinates": [
0.4625,
0.12995049504950495,
0.035,
0.04702970297029703
]
}
],
"boxCoordinates": [
0.28583333333333333,
0.12995049504950495,
0.3883333333333333,
0.04702970297029703
]
},
{
"text": "\u662d\u548c40\u5e741\u670801\u65e5\u751f",
"words": [
{
"text": "\u662d\u548c",
"boxCoordinates": [
0.6675,
0.12871287128712872,
0.03833333333333333,
0.039603960396039604
]
},
{
"text": "40",
"boxCoordinates": [
0.7133333333333334,
0.12871287128712872,
0.03333333333333333,
0.039603960396039604
]
},
{
"text": "\u5e74",
"boxCoordinates": [
0.745,
0.12871287128712872,
0.02,
0.039603960396039604
]
},
{
"text": "1",
"boxCoordinates": [
0.7975,
0.12871287128712872,
0.008333333333333333,
0.039603960396039604
]
},
{
"text": "\u6708",
"boxCoordinates": [
0.82,
0.12871287128712872,
0.016666666666666666,
0.039603960396039604
]
},
{
"text": "01",
"boxCoordinates": [
0.8558333333333333,
0.12871287128712872,
0.028333333333333332,
0.039603960396039604
]
},
{
"text": "\u65e5",
"boxCoordinates": [
0.895,
0.12871287128712872,
0.013333333333333334,
0.039603960396039604
]
},
{
"text": "\u751f",
"boxCoordinates": [
0.9166666666666666,
0.12871287128712872,
0.016666666666666666,
0.039603960396039604
]
}
],
"boxCoordinates": [
0.7866666666666666,
0.12871287128712872,
0.27666666666666667,
0.039603960396039604
]
},
{
"text": "\u4f4f\u6240 \u5317\u6d77\u9053\u5ba4\u862d\u5e02\u8f2a\u897f\u753a1\u4e01\u76ee",
"words": [
{
"text": "\u4f4f\u6240",
"boxCoordinates": [
0.11166666666666666,
0.25742574257425743,
0.04666666666666667,
0.04950495049504951
]
},
{
"text": "\u5317\u6d77\u9053",
"boxCoordinates": [
0.20166666666666666,
0.25742574257425743,
0.08333333333333333,
0.04950495049504951
]
},
{
"text": "\u5ba4\u862d",
"boxCoordinates": [
0.2658333333333333,
0.25742574257425743,
0.04833333333333333,
0.04950495049504951
]
},
{
"text": "\u5e02",
"boxCoordinates": [
0.305,
0.25742574257425743,
0.023333333333333334,
0.04950495049504951
]
},
{
"text": "\u8f2a\u897f",
"boxCoordinates": [
0.3425,
0.2599009900990099,
0.051666666666666666,
0.04950495049504951
]
},
{
"text": "\u753a",
"boxCoordinates": [
0.38166666666666665,
0.2599009900990099,
0.023333333333333334,
0.04950495049504951
]
},
{
"text": "1",
"boxCoordinates": [
0.4058333333333333,
0.2599009900990099,
0.008333333333333333,
0.04950495049504951
]
},
{
"text": "\u4e01\u76ee",
"boxCoordinates": [
0.44416666666666665,
0.2599009900990099,
0.04833333333333333,
0.04950495049504951
]
}
],
"boxCoordinates": [
0.2783333333333333,
0.25866336633663367,
0.38,
0.05693069306930693
]
},
{
"text": "\u4ea4\u4ed8 \u5e73\u621020\u5e7401\u670801\u65e5 85548",
"words": [
{
"text": "\u4ea4\u4ed8",
"boxCoordinates": [
0.11166666666666666,
0.32054455445544555,
0.04,
0.027227722772277228
]
},
{
"text": "\u5e73",
"boxCoordinates": [
0.19916666666666666,
0.32301980198019803,
0.021666666666666667,
0.04702970297029703
]
},
{
"text": "\u6210",
"boxCoordinates": [
0.2225,
0.32054455445544555,
0.021666666666666667,
0.04702970297029703
]
},
{
"text": "20",
"boxCoordinates": [
0.26,
0.32054455445544555,
0.03666666666666667,
0.04702970297029703
]...
curl --location --request GET 'https://zylalabs.com/api/2026/japanese+driving+license+ocr+api/8393/get+data?url=Required¶graphs=Required' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime.
The Japanese Driving License OCR API returns structured data extracted from a driver's license image, including the license holder's name, residence, birthday, delivery date, expiration date, and personal number.
The key fields in the API response include "name," "residence," "birthday," "delivery_date," "expiration_date," and "personal_number," providing essential information about the driver's license holder.
The API returns data in a structured format, typically JSON or XML. The response includes key-value pairs for each extracted field, making it easy to parse and integrate into applications.
The endpoint accepts parameters such as the image URL of the driver's license and a boolean parameter to specify whether to retrieve paragraphs of text (true or false) from the image.
The response data is organized in a clear structure, with each key field representing a specific piece of information extracted from the driver's license. This allows for straightforward access to individual data points.
Typical use cases include identity verification for onboarding processes, age verification for restricted products, and automating data entry for car rental services, enhancing operational efficiency.
Data accuracy is maintained through advanced optical character recognition (OCR) technology specifically trained on Japanese driver's licenses, ensuring reliable extraction of information from images.
Users can utilize the returned data by integrating it into their applications for tasks such as customer verification, record-keeping, or compliance checks, enabling automated workflows and improved data management.
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.
Service Level:
100%
Response Time:
789ms
Service Level:
100%
Response Time:
1,064ms
Service Level:
97%
Response Time:
678ms
Service Level:
100%
Response Time:
941ms
Service Level:
100%
Response Time:
1,062ms
Service Level:
75%
Response Time:
5,400ms
Service Level:
100%
Response Time:
211ms
Service Level:
95%
Response Time:
3,625ms
Service Level:
97%
Response Time:
616ms
Service Level:
100%
Response Time:
1,062ms
Free Sign Up
