Parse Email bodies

How Our Message Parsing API Works

We've developed algorithms which can break email messages into pieces using samples from hundreds of different email clients and thousands of signature examples in multiple languages. We are constantly improving our algoirthms as customers submit new edge cases.

STEP 1

Choose How to Use SigParser
(Hosted or On-Premise)

Developers can utilize our hosted APIs or install our application on their own servers to parse emails.

STEP 2

Post Raw Email or Calendar Content
(MIME, MSG, JSON)

Developers can post MIME, MSG, or JSON formatted email or calendar contents to the SigParser API endpoints.

For our cloud API endpoint you'd call https://ipaas.sigparser.com/api/Parse/Email/Message/JSON

‍Click here to view our API documentation

STEP 3

Receive Parsed Content
(Message Details)

SigParser will return a JSON payload with with parsed email message. It will include the cleaned email in differnt forms (cleaned, HTML, Plain Text) and a collection of emails for the reply chain.

Message Parsing API Response

Send the raw content of a single email or calendar meeting invite to our API endpoint and get a JSON response with contact details organized and ready to integrate into your database or application. It's that easy.

‍Click here to view our API documentation

{
    "Errors": [
        "string"
    ],
    "CleanedBodyPlain": "Top email in the reply chain without the signature or reply chain.",
    "CleanedBodyHtml": "Top email in the reply chain without the signature or reply chain.",
    "IsSpammyLookingEmailMessage": true,
    "IsSpammyLookingSender": true,
    "EmailTypes": [
        "NormalEmail"
    ],
    "Emails": [
        {
        "CleanedBodyPlain": "Email without the signature",
        "CleanedBodyHtml": "Email without the signature",
        "BodyPlain": "Plain text version of the email including the signature.",
        "BodyHtml": "HTML body of the email including the signature.",
        "Subject": "string",
        "Date": "2021-12-27T18:54:38.273Z",
        "FromEmailAddress": "string",
        "FromName": "string",
        "To": [
            {
            "Name": "string",
            "EmailAddress": "string"
            }
        ],
        "Cc": [
            {
            "Name": "string",
            "EmailAddress": "string"
            }
        ]
        }
    ],
    "Subject": "string",
    "Date": "2021-12-27T18:54:38.273Z",
    "Headers": {
        "additionalProp1": "string",
        "additionalProp2": "string",
        "additionalProp3": "string"
    },
    "FullPlainTextBody": "string",
    "FullHtmlBody": "string",
    "MsgType": "string"
}

Contact Parsing API Pricing

We offer a free trial of our Parsing APIs with 500 free API requests. After the free trial, our pricing is usage based with discounts for higher volumes.

We'll help with the math here...
100k API requests / mo costs $1,450
1M API requests / mo costs $5,950
10M API requests / mo costs $6,850

Message Parsing API Pricing

We offer a free trial of our Parsing APIs with 500 free API requests. After the free trial, our pricing is usage based with discounts for higher volumes.

We'll help with the math here...
100k API requests / mo costs $1,200
1M API requests / mo costs $2,100
10M API requests / mo costs $3,000

Frequently Asked Questions

FAQ: What languages are supported?

English is the strongest and most common language. But SigParser also has support for Chinese, Czech, Danish, Dutch, Finnish, French, Italian, Japanese, Korean, Norwegian, Portuguese, Russian, Spanish, Swedish and Turkish. Some languages have better support than others though and largely depend on customer submitting examples and edge cases to us.

FAQ: Where can I submit parsing errors?

There are two ways to submit parsing errors. First option is to forward the email or even a screenshot of the email to sigparser-error@sigparser.com. The second option is to POST the email to the endpoint https://ipaas.sigparser.com/api/Parse/Feedback.

FAQ: Can you handle this email format?

We find developers often don't know what format email they have. Schedule a technical call with one of our developers and we'll help you identify the format and which API to use.

FAQ: Why isn't the email parsing right?

There are a few common reasons we see. Incorrect format, incorrect decoding, incorrect mapping of parameters. Schedule a technical call with one of our developers and we'll help you correct the issue.

Parse Email Message Bodies