Choose the appropriate path
Browser uploads are the simplest starting point. Forward-to-parse is available on Starter or Pro; public API access requires Pro. A one-time pack enables manual processing but does not add forwarding or API entitlement.
Find your forwarding controls
Open Account → Forward-to-parse. Use your account's inbound address and Allowed sender controls. An inbound address is private; do not publish it in screenshots or shared instructions. Rotating the address changes where mail should be sent, so update your own forwarding setup afterward.
Test a small routine first
Send a non-confidential sample from an allowed sender and check Recent batches. Confirm the content, credits and output before connecting a larger stream. A successful email delivery is not the same thing as verified extracted data.
Use the documented API contract
For Pro automation, follow the API documentation for authentication, submission, status, downloads, limits and idempotency. Keep API keys outside browser code and public documents. Check the actual response and reuse the same request identity only for unchanged work.
Check your result
You're done when…
A controlled sample reaches the existing processing flow and produces an output you can inspect. You know how to stop or update the connection.
If something goes wrong
If an expected batch does not appear, check the selected account, plan, current inbound address and allowed sender. Do not expose private addresses or keys while asking for help. Existing Gmail/Outlook behavior and provider availability are not guaranteed by this guide.
Contact support ↗Guide reviewed 2026-10-25. For commercial terms, see Pricing and the Refund Policy. For data handling, see Privacy.