Easily extract contact details (e.g., full name, phone numbers, title, address, etc.) from email signatures, headers, and messages in emails.
Our stateless API accept email files in MIME, JSON, or MSG format and then responds with parsed contact details in JSON format. It's that easy.
Developers can utilize our hosted APIs or install our application on their own servers to parse emails.
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
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.
Send the raw content of an email 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
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.
{
"from_address": "john@example.com",
"from_displayname": "John Smith",
"job_title": "Vice President",
"phones": [
{
"type": "Mobile",
"phone_number": "818-334-3433",
"match_type": "Signature",
"line": "Mobile 818-334-3433"
}
],
"address": "999 Grand Ave, San Diego, CA, United States",
"address_parts": {
"street": "999 Grand Ave",
"city": "San Diego",
"state": "CA",
"postal_code": "99999",
"country": "United States"
},
"links": [
{
"url": "https://twitter.com/personxyz",
"social_handle": "personxyz",
"type": "twitter"
}
],
"signature": "John Smith\r\nVice President\r\nMobile 818-334-3433\r\n999 Grand Ave, San Diego, CA, United States\r\nOur mission is to deliver customer satisfaction!",
"errors": [
"string"
],
"duration": 100
}
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.
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.
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.
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.