Dacid99 Eonvelope API

Name: Eonvelope API
Brand: Eonvelope API
Availability: InStock

✓ Official Vendor SpecProductivityNote Takingbearer8 EndpointsREST

For Agents

List, search, and retrieve archived emails and attachments from a self-hosted Eonvelope archive for compliance and research workflows.

Install Jentic One Beta

Connect the Eonvelope API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Eonvelope API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Eonvelope API.

List archived emails with pagination across the Eonvelope store

Retrieve a specific archived email by email_id with structured metadata

Download the raw EML source of an archived email for forensic or evidentiary use

GET STARTED

Start building with Eonvelope API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Eonvelope API for, with concrete tasks.

★ Compliance Search and Export

When a compliance request requires extracting all archived mail relating to a customer or legal matter, an operator runs GET /search with the relevant query, walks the results to GET /emails/{email_id}/raw, and stores each EML file as evidence. The agent automates the export, which would otherwise take hours of manual work in a webmail UI.

Call GET /search?q=customer@example.com, then loop the result IDs through GET /emails/{email_id}/raw and write each response to disk.

Attachment Recovery Workflow

Users who need to recover an attachment from an archived email use GET /emails/{email_id}/attachments to enumerate attachments, then GET /emails/{email_id}/attachments/{attachment_id} to download the file. This makes Eonvelope a useful self-hosted alternative to enterprise archiving products for small teams.

Given email_id 'abc123', call GET /emails/abc123/attachments, pick the first attachment, and GET /emails/abc123/attachments/{attachment_id}.

Archive Capacity Reporting

Operators of self-hosted Eonvelope instances need periodic visibility into how many emails are stored and how the archive is growing. GET /stats returns counts and storage figures that can be piped into a Grafana dashboard, replacing manual SSH checks against the underlying database.

Call GET /stats once a day and write the email_count and storage_bytes fields to a Prometheus pushgateway for Grafana.

Agent-Assisted Mail Research

An AI research assistant indexes a project mailbox by listing emails through GET /emails, retrieving relevant ones with GET /emails/{email_id}, and answering questions over the archive. The Bearer token is stored in Jentic so the agent never sees the raw secret, which matters when the archive contains confidential correspondence.

Call GET /search?q=project-name, retrieve the top 20 emails via GET /emails/{email_id}, and summarise key decisions.

Key Endpoints

8 endpoints — eonvelope is a self-hostable email archiving application with a web interface and integrations for grafana, paperless-ngx, and searxng.

METHOD

PATH

DESCRIPTION

GET

/emails

List archived emails

GET

/emails/{email_id}

Get a specific archived email

GET

/emails/{email_id}/raw

Download raw EML source

GET

/emails/{email_id}/attachments

List attachments for an email

GET

/emails/{email_id}/attachments/{attachment_id}

Download a single attachment

GET

/search

Full-text search across archived emails

GET

/stats

Get archive statistics

DELETE

/emails/{email_id}

Delete an archived email

GET

/emails

List archived emails

GET

/emails/{email_id}

Get a specific archived email

GET

/emails/{email_id}/raw

Download raw EML source

GET

/emails/{email_id}/attachments

List attachments for an email

GET

/emails/{email_id}/attachments/{attachment_id}

Download a single attachment

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Eonvelope Bearer token and the deployment's server_url are stored encrypted in the Jentic vault. Agents receive a scoped runtime credential when they execute /emails or /search operations, so the raw token and the internal hostname never enter the model context.

Intent-based discovery

Agents search Jentic for 'search archived emails' or 'download raw EML for an archived email' and Jentic returns the matching Eonvelope operation with its input schema, so the agent can call GET /search or GET /emails/{email_id}/raw directly.

Time to first call

Direct Eonvelope integration: a few hours to read the spec, handle the {server_url} variable, and chain search to retrieval. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using Eonvelope API through Jentic.

What authentication does the Eonvelope API use?

Eonvelope uses HTTP Bearer authentication. You generate a token in the self-hosted instance and pass it as Authorization: Bearer <token> on every request to {server_url}/api. Through Jentic the token is stored encrypted in the vault and the agent receives a scoped runtime credential, so the raw token never lands in chat or logs.

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.

Dacid99 Eonvelope API

Connect the Eonvelope API to your agent

Capabilities

Start building with Eonvelope API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs