> For the complete documentation index, see [llms.txt](https://help.delpha.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.delpha.io/delpha-api-and-mcp/api/email-insights.md).

# Email Insights

Advanced email content analysis and entity extraction capabilities. Delpha's Email Insight solution systematically analyzes email bodies to identify and extract critical contact information, professional details, and contextual insights that can transform how you understand and interact with your contacts.

This solution leverages advanced natural language processing and machine learning to extract structured data from unstructured email content, including contact information, professional details, and business context. The extracted insights enhance data quality, enable smarter interactions, and drive informed business decisions.

Perfect for CRM enrichment, lead generation, business intelligence applications, and any use case requiring automated extraction of valuable information from email communications.

## Get email insights from an email body

> Extract name, title, company, phone number, and more from an email body.

```json
{"openapi":"3.1.0","info":{"title":"Delpha Data Quality API","version":"1.0.0"},"tags":[{"name":"Email Insights","description":"Advanced email content analysis and entity extraction capabilities. Delpha's Email Insight solution systematically analyzes email bodies to identify and extract critical contact information, professional details, and contextual insights that can transform how you understand and interact with your contacts.\n\nThis solution leverages advanced natural language processing and machine learning to extract structured data from unstructured email content, including contact information, professional details, and business context. The extracted insights enhance data quality, enable smarter interactions, and drive informed business decisions.\n\nPerfect for CRM enrichment, lead generation, business intelligence applications, and any use case requiring automated extraction of valuable information from email communications."}],"servers":[{"url":"https://api.delpha.io","description":"Production API server"}],"security":[{"oauth2":["api/access"]}],"components":{"securitySchemes":{"oauth2":{"type":"oauth2","description":"OAuth2 client credentials flow for API access","flows":{"clientCredentials":{"tokenUrl":"https://secure.delpha.io/oauth2/token","scopes":{"api/access":"Access to the public API"}}}}},"schemas":{"EmailInsightsInput":{"properties":{"email_bodies":{"items":{"type":"string"},"type":"array","title":"Email Bodies","description":"The body text of the email to analyze for insights."}},"type":"object","required":["email_bodies"],"title":"EmailInsightsInput","description":"Input model for email insights extraction."},"EmailInsightsOutput":{"properties":{"results":{"anyOf":[{"items":{"$ref":"#/components/schemas/InsightsModel"},"type":"array"},{"type":"null"}],"title":"Results","description":"The extracted insights from the emails if successful, otherwise None."},"message":{"type":"string","title":"Message","description":"The message to return to the user."},"status":{"type":"string","enum":["SUCCESS","ERROR"],"title":"Status","description":"The status of the process"},"status_code":{"type":"integer","title":"Status Code","description":"The status code to return to the user."}},"type":"object","required":["message","status","status_code"],"title":"EmailInsightsOutput","description":"Output model for extracted email insights."},"InsightsModel":{"properties":{"name":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Name","description":"The extracted name of the sender of the email, if found."},"phone":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Phone","description":"The extracted landline phone number of the sender, if found (formatted as E.164 if possible)."},"mobile":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Mobile","description":"The extracted mobile phone number of the sender, if found (automatically normalized)."},"title":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Title","description":"The extracted title of the sender of the email, if found."},"company":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Company","description":"The extracted company of the sender of the email, if found."},"department":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Department","description":"The extracted department where the sender works, if found."},"address":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Address","description":"The extracted address or location of the sender, if found."},"social_media":{"anyOf":[{"items":{"$ref":"#/components/schemas/SocialMediaModel"},"type":"array"},{"type":"null"}],"title":"Social Media","description":"All the extracted social media profiles (sender or/and company), if found."},"out_of_office":{"anyOf":[{"$ref":"#/components/schemas/OutOfOfficeModel"},{"type":"null"}],"description":"The out-of-office status and period of the sender, if found."},"confidence":{"type":"number","title":"Confidence","description":"The confidence score of the extracted insights."}},"type":"object","required":["confidence"],"title":"InsightsModel","description":"Output model for extracted email insights."},"SocialMediaModel":{"properties":{"name":{"type":"string","title":"Name","description":"The name of the social media platform."},"url":{"type":"string","title":"Url","description":"The URL to the social media profile."},"owner":{"type":"string","enum":["sender","company"],"title":"Owner","description":"The owner of the social media profile."}},"type":"object","required":["name","url","owner"],"title":"SocialMediaModel","description":"Model representing a social media profile."},"OutOfOfficeModel":{"properties":{"status":{"type":"boolean","title":"Status","description":"Whether the sender is out of office."},"start_date":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"Start Date","description":"The start date of the out-of-office period, if available."},"end_date":{"anyOf":[{"type":"string"},{"type":"null"}],"title":"End Date","description":"The end date of the out-of-office period, if available."}},"type":"object","required":["status"],"title":"OutOfOfficeModel","description":"Model representing the out-of-office status and period."}}},"paths":{"/v1/email-insights":{"post":{"tags":["Email Insights"],"summary":"Get email insights from an email body","description":"Extract name, title, company, phone number, and more from an email body.","operationId":"getEmailInsights","requestBody":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/EmailInsightsInput"}}},"required":true},"responses":{"200":{"description":"Email insights extracted successfully for 2 emails.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/EmailInsightsOutput"}}}},"400":{"description":"Invalid email body provided.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/EmailInsightsOutput"}}}},"401":{"description":"Authentication failed - invalid or missing OAuth 2.0 token","content":{"application/json":{"schema":{"properties":{"message":{"type":"string"}},"type":"object"}}}},"500":{"description":"Failed to extract insights from emails.","content":{"application/json":{"schema":{"$ref":"#/components/schemas/EmailInsightsOutput"}}}}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.delpha.io/delpha-api-and-mcp/api/email-insights.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.