Nutrient Document Web Services API connector for Okou
Connect Nutrient Document Web Services API to generate, convert, edit, secure, extract, and inspect documents through its Processor, Viewer, Accessibility, and Data Extraction APIs.
Docs & knowledge · Processor API Key · Viewer API Key · Accessibility API Key · Data Extraction API Key
Use Nutrient Document Web Services API in Okou
Use Nutrient Document Web Services API for PDF generation, conversion, editing, viewing, accessibility tagging, OCR, redaction, signatures, and structured data extraction.
Once connected, supported Nutrient Document Web Services API actions can become steps in a reusable workflow alongside the other services your team uses. Run the workflow once, on a schedule, or when an event starts it.
What you can do with Nutrient Document Web Services API
- Auto-tag PDF documents for PDF/UA accessibility. Processing may consume provider quota.
- Parse or extract structured content from documents. Processing may consume Nutrient credits or provider quota.
- List extraction runs, inspect run details and shares, or download run assets.
- Read Processor account information and product usage. The account-info operation is deprecated by Nutrient.
- Read the status or result of a Processor asynchronous job.
- Create PDF/UA-compliant output with Processor. Processing may consume Nutrient credits or provider quota.
- Analyze a Processor build request and calculate document-processing requirements.
- Build or process document templates with Processor. Processing may consume Nutrient credits or provider quota.
How the Nutrient Document Web Services API connector works
A connected service becomes one permissioned step in the work you hand off.
- 1
Connect Nutrient Document Web Services API
Choose Processor API Key or Viewer API Key or Accessibility API Key or Data Extraction API Key.
- 2
Choose the work
Use only the supported actions your workflow needs.
- 3
Run it your way
Start it once, schedule it, or attach an event trigger.
Connect Nutrient Document Web Services API securely
Use the connection method that fits your account and grant only the access the workflow needs.
- Processor API Key
- Viewer API Key
- Accessibility API Key
- Data Extraction API Key
Connector access is controlled per service and per action, so a workflow does not need broader access than the work you ask it to do.
Nutrient Document Web Services API connector questions
- What can Okou do with Nutrient Document Web Services API?
- Connect Nutrient Document Web Services API to generate, convert, edit, secure, extract, and inspect documents through its Processor, Viewer, Accessibility, and Data Extraction APIs. Documented actions include: Auto-tag PDF documents for PDF/UA accessibility. Processing may consume provider quota. Parse or extract structured content from documents. Processing may consume Nutrient credits or provider quota.
- How do I connect Nutrient Document Web Services API to Okou?
- Connect Nutrient Document Web Services API using Processor API Key or Viewer API Key or Accessibility API Key or Data Extraction API Key. The connection controls which supported actions a workflow can use.
- Can Nutrient Document Web Services API run in an automated workflow?
- Yes. After it is connected, supported Nutrient Document Web Services API actions can run in reusable Okou workflows on demand, on a schedule, or from an event trigger.
More docs & knowledge connectors
Explore other connectors in the same product category.
Oneflow
Connect Oneflow to inspect and manage contracts, templates, workspaces, contacts, contract data, and webhooks through the official public API.
Notion
Connect your Notion workspace to access pages and databases.
OneSecMail
Connect OneSecMail to generate disposable mailboxes, list available domains, inspect inboxes, read messages, and download message attachments through its public API.
