Can I full-text search archived emails through the API?

Yes. GET /search accepts a query parameter and returns matching email records. Combine it with GET /emails/{email_id} or GET /emails/{email_id}/raw to retrieve the full content for each hit.

What are the rate limits for the Eonvelope API?

Eonvelope is a self-hosted application, so any rate limits are determined by the deployment rather than a SaaS tier. Treat the underlying database as the bottleneck and pace bulk exports to keep the archive responsive for interactive users.

How do I export archived emails through Jentic?

Install pip install jentic and run an agent with the search query 'export archived emails as EML'. Jentic returns the GET /search and GET /emails/{email_id}/raw operations with their input schemas, so the agent can iterate the search results and stream the raw EML for each hit.

Can I delete an email from the Eonvelope archive via the API?

Yes. DELETE /emails/{email_id} removes the email and its attachments. Use this carefully because Eonvelope is intended as an archive of record; deletion should be gated on a retention policy review.

Is the Eonvelope API free?

Eonvelope itself is open source and self-hosted, so there is no per-call cost. Your costs are limited to the infrastructure you run it on; the API is included with any Eonvelope deployment.

Can I limit what my agent is allowed to do with the Eonvelope API?

Yes. Because you run Jentic One yourself, your own rules decide which Eonvelope operations and credentials the agent may use. Eonvelope puts the email id in the URL path, such as /emails/{email_id} and /emails/{email_id}/raw, so you can pin the agent to reading a single archived email, its raw EML, and its attachments while withholding the full listing or search. You choose the operations the agent may call, so a destructive DELETE /emails/{email_id} is excluded unless you explicitly allow it.