Cloud Document AI API logo

Cloud Document AI API

Cloud Document AI API

Google Document AI API processes documents with ML — OCR, form parsing, contract data extraction, invoice extraction — pre-trained + custom models.

Visit site ↗Health checked 9h ago
Use it when

Pre-trained processors cover common types: invoice, ID, receipt

Watch for

Per-page pricing — high-volume cost adds up

First check

Create a Document AI processor in GCP Console (pre-trained or custom). POST /v1/projects/{project}/locations/{location}/processors/{processor}:process with the document.

Auth
CORS
No
HTTPS
Yes
Signup
?
Latency
43 ms
Protocol
REST
Pricing

Uptime · 30-day window

Probes: 1Uptime: 100%Avg latency: 43ms
01

About this API

Document AI is GCP's Intelligent Document Processing (IDP) product, positioned as "smarter than generic OCR" — not just image-to-text but understanding document structure and semantics, extracting key-value pairs, tables, signature locations, field meanings. The product is structured as "processors" — each processor is an ML model for a specific document type: Invoice Parser, ID Document Parser, Form Parser, Contract Parser. Pre-trained processors work out of the box with high quality for common documents. For complex scenarios (industry-specific forms), train custom processors in Document AI Workbench — just label a few dozen samples in the UI. Compared to AWS Textract and Azure Form Recognizer, Document AI has industry-leading accuracy in some scenarios (e.g. invoice field extraction).

02

What you can build

  • 1Auto-extract invoice amount/account/due date
  • 2ID/passport OCR + field recognition
  • 3Extract key contract terms (amount, effective date)
  • 4Bank statement auto-ingestion
03

Strengths & limitations

Strengths

  • Pre-trained processors cover common types: invoice, ID, receipt
  • Workbench tool supports custom model training
  • Form Parser handles general forms well

Limitations

  • Per-page pricing — high-volume cost adds up
  • Specialty forms (e.g. health-insurance forms) require custom training
04

Example request

Generic template — replace <endpoint> with the real path from the docs.
curl https://google.com/<endpoint>
05

Getting started

Create a Document AI processor in GCP Console (pre-trained or custom). POST /v1/projects/{project}/locations/{location}/processors/{processor}:process with the document.

06

FAQ

How is Chinese document support?+

Generic OCR and Form Parser work well for Chinese. Some pre-trained processors (like Invoice Parser) target English primarily — train custom processors for Chinese scenarios.

Document AI vs. Cloud Vision OCR?+

Vision OCR is for "just text". Document AI is for "understand structure and field meaning". Vision OCR is 5-10x cheaper.

07

Technical details

CORS: NoHTTPS: YesSignup: ?Open source: No
Auth type
unknown
Pricing
unknown
Protocols
REST
SDKs
python, javascript, go, java
Response time
43 ms
Last health check
5/12/2026, 7:37:31 AM
08

Tags

09

More from Google