DigiParser can process documents from URLs—you send links to documents (e.g. PDFs on a server or cloud storage) instead of uploading files. The system downloads each file from the URL and processes it like a normal upload.

This is done through the Process API, not from the Document Inbox UI. It’s useful when:

• Documents are already hosted online (your server, S3, Google Drive, etc.).
• You use Zapier, Make, or other automation tools that work with URLs.
• You have scripts or integrations that call the API.

1. You have document URLs that point directly to files (PDF, images, Office docs, etc.). The URLs must be publicly accessible so DigiParser can fetch them.
2. You call the Process API with your parser ID and API key, and pass an array of URLs in the request body.
3. DigiParser downloads each file, processes it with your parser’s Fields & Tables, and adds the resulting documents to your Document Inbox.

Processed documents show up in the same inbox as uploads and email. You can filter, edit, and export them as usual.

• API – Use the Process API (/api/v1/process/{parserId}/urls) with a urls array. See the API Reference for authentication and request format.
• Zapier – If your Zapier integration supports “Process from URL,” you can send document URLs there instead of file uploads.
• Custom integrations – Any tool that can send HTTP requests can use the API to process documents from URLs.

The same file types as uploads are supported (PDF, PNG, JPEG, Word, Excel, etc.). The parser’s document types setting (if configured) still applies. Split behavior follows your parser’s split settings when the document is a PDF.

• Ensure URLs are publicly accessible and return the actual file (not a login page).
• Use HTTPS when possible. Unreachable or invalid URLs will cause those items to fail.

• API Reference – Process API details and authentication
• Uploading Documents – Upload from the app
• Processing via Email – Send documents by email