PicToText Documentation

Master every step of the PicToText OCR workflow. These docs walk you through authentication, uploading images, receiving structured JSON, and managing document-specific nuances so you can ship production-ready identity verification features in days instead of weeks.

Whether you are building an onboarding flow, refreshing legacy OCR pipelines, or connecting PicToText to automated review tooling, you will find practical tutorials, exhaustive reference material, and troubleshooting advice below. Each article pairs high-level guidance with code snippets you can copy into your integration.

Get started with the core guides

Follow these step-by-step tutorials to generate API keys, send your first OCR request, and handle responses securely in production environments.

More implementation help

Identity document coverage by region

PicToText maintains dedicated schemas for passports, national IDs, driver's licences, and residency permits across dozens of jurisdictions. Each reference page outlines required request data, the fields we parse, and sample code in multiple languages so you can stay compliant with local formatting rules.

Asia

20 document types documented, including Bangladesh ID Card, Chinese ID Card, India Aadhaar Front, Indonesia KTP. Use these references to validate field expectations, understand issuance authority nuances, and map structured JSON into your CRM or KYC platform.

Europe

10 document types documented, including France National ID Card, Germany National ID Card, Italy Electronic ID Card, Netherlands National ID Card. Use these references to validate field expectations, understand issuance authority nuances, and map structured JSON into your CRM or KYC platform.

Africa

4 document types documented, including Egypt National ID Card, Ghana ID Card, Nigeria NIN Slip, South Africa Smart ID Card. Use these references to validate field expectations, understand issuance authority nuances, and map structured JSON into your CRM or KYC platform.

North America

3 document types documented, including Canada Provincial Driver's License, Mexican ID Card, US Driver's License. Use these references to validate field expectations, understand issuance authority nuances, and map structured JSON into your CRM or KYC platform.

Oceania

3 document types documented, including Australia State Driver's Licence, New Zealand Driver's Licence, New Zealand Kiwi Access Card. Use these references to validate field expectations, understand issuance authority nuances, and map structured JSON into your CRM or KYC platform.

South America

3 document types documented, including Argentina ID Card, Colombia ID Card, Peru ID Card. Use these references to validate field expectations, understand issuance authority nuances, and map structured JSON into your CRM or KYC platform.

International

1 document type documented, including Passport. Use these references to validate field expectations, understand issuance authority nuances, and map structured JSON into your CRM or KYC platform.

Developer resources

Keep the PicToText API running smoothly in production. These references cover rate limits, usage dashboards, error responses, and operational best practices for support teams.

FAQs and onboarding guidance

New to identity-document OCR? The answers below highlight the questions we hear most often from product teams and solution engineers.

How accurate is the PicToText OCR pipeline?

Accuracy varies by document class, but our ensemble models are tuned for government-issued IDs and passports. Every reference page specifies the fields we guarantee, and the error guide explains how to retry borderline scans with progressive enhancement. Quality improves further when you supply high-contrast images with clear MRZ lines.

Can I prototype without a production API key?

Yes. Generate a sandbox key, follow the quickstart to send your first request, and inspect the JSON payload. When you are ready to go live, swap the credential and keep the same request structureβ€”the API versions and response fields remain consistent.

What happens to uploaded images?

Images are encrypted at rest, processed in isolated workers, and deleted automatically after analysis. You can mirror the payload to your own storage if compliance rules require it; the limits guide covers retention options and audit recommendations.

How do I stay up to date with new document templates?

Subscribe to the release notes inside the dashboard or check the supported documents list regularly. We ship new templates every month and document the added fields, sample payloads, and change-management tips so you can update downstream systems without downtime.