SigParser 2.0.0

Parse email bodies, split email chains chains and email signatures from either HTML or plain text emails. Multiple languages supported.

Signup for a free API key at https://sigparser.com to get an API key and use the API with up to 1500 emails parses per month.

Code Example

var client = new SigParser.Client(ApiKey);
var result = client.ParseRawRequestAsync(new SigParser.EmailParseRequest
            {
                date = new DateTime(2017, 1, 1),
                plainbody = @"
Hi Sally,
Thanks for the meeting the other day. It was greating seeing you. We should catchup sometime soon.

My phone number is 888-333-4233.

Thanks,
Jim Johnson
Senior Software Developer
SigParser Inc.
Cell 777-333-4233
333 Grand Ave, San Diego, CA 93233
https://sigparser.com

",
                from_name = "Jim Johnson",
                from_address = "jim.johnson@sigparser.com",
                subject = "Here is a subject",
                to = new SigParser.Recipient[] { new SigParser.Recipient { name = "Johnny To", emailAddress = "johnny.to@example.com" } },
                cc = new SigParser.Recipient[] { new SigParser.Recipient { name = "Cathy Carbon", emailAddress = "cathy.carbon@example.com" } }
            }).Result;

FAQ

What can it find?

SigParser tries to parse raw emails and pull out everything interesting.

• Split the emails on the email headers generated by various email clients
  • Multiple languages supported
• Converts emails to plain text if originally HTML
• Converts each HTML section to HTML
• Capture email signatures from each email in an email body.
• Capture inline phone numbers (ie My phone is...)
• Capture job titles, addresses, Twitter, LinkedIn handles

How do I use this?

Create an instance of SigParser.Client class and pass it the API key or set the API key property. Then call the Parse(email) async method. For the email object, you need to provide either the HTML or Plain text body or both. If you provide both SigParser will prefer HTML first and if blank then plaintext. For signature parsing it is important to provide the display name “from_name” (first and last name) of the sender which you almost always get for emails. The from_address is also good to provide. See below for a code example.

Why use an API vs just embedding the parsing logic in the library?

Over time email signature patterns change and email clients change their headers. For example, in 2014 Gmail started using a massively different header for about two months. Instead of making you update your code every week or month, calling an API lets you get the latest algorithm changes without having to update your code. We update the underlying API and algorithms weekly but the API contract shouldn't change and if it does, we're only adding functionality to it.

Can I run SigParser API in my data center?

Yes, but you need to contact us to discuss how to use it onsite and licensing requirements.

To set the URL of your local installation, set the SigParser.Client.BaseUrl to your URL before making any API requests.

Is SigParser storing my emails?

No, SigParser doesn’t store emails you send to it via this package. We receive the payload, process it and return the response. Behind the scenes we use a Lambda function to drive the API so everything is ephemeral.

How do I pull the emails from the email server?

We have a variety of articles at our website on how to do this. It is too long to explain here. Checkout our website.