Faster document processing
Automate extraction for invoices, forms and receipts.
Azure AI Document Intelligence Connector
Build in-app document processing features—OCR, table and field extraction, invoice and ID parsing—so customers automate document workflows, validate extracted data and surface structured results inside your SaaS application.
Reduce manual data entry
Turn documents into structured data for downstream apps.
Customizable workflows
Orchestrate multi-step validation, enrichment and routing.
Embedded experience
Deliver customer-facing workflows natively inside your SaaS product.
CONNECTOR OVERVIEW
Overview
Azure AI Document Intelligence is Microsoft’s cloud document processing API for extracting text, key-value pairs, tables and structured data from images and PDFs. Use Cyclr to embed those capabilities into your multi-tenant SaaS product, orchestrate validation and routing, and expose document-analysis features to end users.
PRODUCT USE CASES
Top Use Cases for Azure AI Document Intelligence Integrations
Create integrations to extract invoices, IDs, contracts and unstructured documents. Publish white-label integrations through Cyclr’s embedded marketplace so customers run document analysis without leaving your product.
Automated invoice ingestion
Extract line items, totals and vendor fields from invoices, validate amounts and push structured data into accounting or ERP systems for multi-tenant customers.
Customer identity and document verification
Parse and validate ID documents and proof-of-address files during user onboarding to speed verification for each tenant.
Contract data extraction
Extract key clauses, dates and parties from contracts to populate CRM records, reminders and approval workflows for customers.
ORCHESTRATION
How Azure AI Document Intelligence works with Cyclr
Cyclr sits between your SaaS product and Azure AI Document Intelligence to handle authentication, govern access and orchestrate every API call per customer, at scale.
- 1
Your SaaS product
Your app requests an action for a specific customer.
- 2
Cyclr orchestration
Cyclr authenticates, applies policies and routes the request.
- 3
Azure AI Document Intelligence
Azure AI Document Intelligence processes the request and returns a response to your app.
Customer-specific authentication · Governed data movement · Centralized visibility and audit
CONNECTOR COVERAGE
Available connector capabilities
Explore Azure AI Document Intelligence methods you can orchestrate through Cyclr.
Analyze3
Get Classifier Analyze Result
ActionGet a document classifier result.
Classify Document By URL
ActionClassify a document with the document classifier using a source URL.
Classify Document
ActionClassify a document with the document classifier.
Operations1
Get Operation
ActionGet an operation.
TECHNICAL DETAILS
Azure AI Document Intelligence integration and API details
Review the sourced authentication and API behaviour used when configuring customer-facing Azure AI Document Intelligence integrations in Cyclr.
API and authentication
- API host
https://.cognitiveservices.azure.com- Authentication
- API key (Cognitive Services) or Microsoft Entra ID (Azure AD) token
- Credentials
Endpoint URL and API key, or Azure AD client ID, tenant ID and client secret / managed identity
- Method categories
Analyze documents, manage and train document models, retrieve analyze results, prebuilt model inference
Pagination and rate limits
Pagination
Analyze is asynchronous: POST returns 202 with an Operation-Location header. Poll the provided URL to retrieve results.
Rate limits
The service may return 429 throttling responses with Retry-After. Implement retries, backoff and request quota increases for sustained throughput.
IMPLEMENTATION
Authentication at a glance
Use a Document Intelligence resource endpoint with either an apiKey header or Azure AD token. Managed identities are recommended for cloud-hosted backends.
- Authentication method
- API key (Cognitive Services) or Microsoft Entra ID (Azure AD) token
- Credential required
Endpoint URL and API key, or Azure AD client ID, tenant ID and client secret / managed identity
Before you begin:
View setup guideRequires an Azure Document Intelligence resource; endpoints and keys differ by region and API version.
COMMON QUESTIONS
Frequently asked questions
It lets your app call Azure AI Document Intelligence to extract text, tables and key-value pairs from documents and return structured results.
Authenticate using the Document Intelligence resource endpoint with an API key header or with Azure AD tokens and managed identities.
Yes. Use Azure AD service principals or managed identities to avoid long-lived keys in your backend.
POST analyze requests return 202 and an Operation-Location header. Poll that URL to get status and final results.
KEEP EXPLORING
Related resources and connectors
Documentation
What is iPaaS?
Read more →ProductData Consolidation through Data Integration
Read more →ProductNative Embedded iPaaS
Read more →Related connectorChatGPT
Related AI agents connector for customer-facing integration workflows.
Related connectorClaude
Related AI agents connector for customer-facing integration workflows.
Related connectorNew Connector Request
Related AI agents connector for customer-facing integration workflows.