openapi: 3.0.0 info: title: Email Signature Extraction API version: 1.0.0 description: > AI-powered email signature parser using the DeepSeek LLM (`deepseek-chat`). Designed to sit inside **CRM automation pipelines** (Zapier, Make.com, n8n) that process inbound emails before pushing new contacts into Salesforce, HubSpot, or Pipedrive. Feed it the raw body of an inbound email — plain text, HTML, or mixed — and receive back a clean, fully-structured contact record in a single API call. ### What it does The API locates the sender's signature block, ignores legal boilerplate, standard sign-offs ("Best regards"), and environmental disclaimers, then extracts: - **Full name** split into `first_name` / `last_name` with Title Case applied. - **Job title** and **company name** exactly as written in the signature. - **Email address** from the signature (may differ from the envelope `From:` address). - **Phone numbers** — all numbers found, each standardised to international format and classified as `office`, `mobile`, or `fax`. - **Postal address** decomposed into street, city, state, postal code, and country. - **Social / profile links** (LinkedIn, Twitter/X, GitHub, etc.) as URL strings. - **Confidence flags** — a `missing_fields` array listing every key that could not be located so downstream pipelines can route or flag incomplete records. ### Format support The `email_body` field accepts any of the following input formats: - **Plain text** — the most common format from email clients and webhooks. - **HTML** — full HTML email source (tags are stripped server-side before inference). - **Mixed / MIME text** — forwarded threads, reply chains, or any hybrid content. ### Cost & safety controls - The email body is **hard-truncated to the last 4,000 characters** before being sent to DeepSeek. Signatures are always at the bottom of a thread, so this guarantees low, predictable token usage and prevents Lambda timeouts on huge forwarded threads without breaking pipeline compatibility. - Raw `email_body` is capped at 500,000 characters (DOS guard) — anything larger returns a `400 Bad Request` immediately. ### Pipeline integration examples - **Zapier**: Use a *Webhooks by Zapier* trigger on your inbox, POST the `{{body_plain}}` field to this endpoint, then map `contact_data` fields directly into a *HubSpot — Create Contact* action. - **Make.com**: Connect a *Gmail / Outlook* module to an *HTTP* module pointing at this endpoint, then pipe the response into a *Salesforce — Upsert Record* module. contact: name: Support license: name: Apache 2.0 servers: - url: https://7n75bbq4id.execute-api.us-east-1.amazonaws.com/prod description: Production API # REMOVED Backend Secrets. RapidAPI adds X-RapidAPI-Key automatically. security: [] tags: - name: Signature Extractor description: AI-powered email signature parsing for CRM automation pipelines paths: /extract/signature: post: tags: - Signature Extractor summary: Extract contact data from an email signature description: > Accepts the raw body of an inbound email (plain text, HTML, or mixed), locates the sender's signature block, and returns a CRM-ready contact record with structured fields and confidence flags. **Typical use-cases** - Auto-creating contacts in HubSpot / Salesforce from inbound sales emails - Enriching CRM records when a known contact emails from a new domain - Extracting contact details from email forwards inside support pipelines - Populating deal rooms with verified contact information from proposal replies operationId: extractSignature requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/ExtractSignatureRequest' examples: PlainTextEmail: summary: Plain-text email with full signature value: email_body: | Hi Michael, Thanks for the follow-up. I've attached the revised proposal. Best regards, Sarah -- Sarah Jenkins Vice President of Sales Acme Corp | 123 Innovation Way, Suite 400, Austin, TX 78701 Office: +1-555-019-8372 | Mobile: +1-555-992-1102 s.jenkins@acmecorp.com https://linkedin.com/in/sarahjenkins https://twitter.com/sjenkinssales CONFIDENTIALITY NOTICE: This email is for the intended recipient only. sender_email: s.jenkins@acmecorp.com HtmlEmail: summary: HTML email body value: email_body: >

Hi Michael,

Thanks for the follow-up.

Best,
Sarah

Sarah Jenkins

Vice President of Sales — Acme Corp

Office: +1-555-019-8372

s.jenkins@acmecorp.com

sender_email: s.jenkins@acmecorp.com MinimalSignature: summary: Email with sparse / minimal signature value: email_body: | John, Sounds good. Let's connect Thursday. - Alex Rivera | alex.rivera@startup.io NoSenderHint: summary: Plain text, no sender_email hint value: email_body: | Thank you for your interest. Regards, Dr. Priya Nair Chief Medical Officer, HealthGen Ltd. Tel: +44 20 7946 0831 priya.nair@healthgen.co.uk 71 Harley Street, London, W1G 8DH, United Kingdom responses: '200': description: Successful extraction content: application/json: schema: $ref: '#/components/schemas/ExtractSignatureResponse' example: status: success contact_data: first_name: Sarah last_name: Jenkins job_title: Vice President of Sales company_name: Acme Corp email: s.jenkins@acmecorp.com phone_numbers: - type: office number: "+1-555-019-8372" - type: mobile number: "+1-555-992-1102" address: street: 123 Innovation Way, Suite 400 city: Austin state: TX postal_code: "78701" country: USA social_links: - https://linkedin.com/in/sarahjenkins - https://twitter.com/sjenkinssales confidence_flags: missing_fields: [] '400': description: Bad request — missing or invalid input content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' examples: MissingEmailBody: summary: email_body field missing value: error: "Missing required field: email_body" EmptyEmailBody: summary: email_body is blank value: error: "email_body must not be empty" PayloadTooLarge: summary: email_body exceeds 500 000 characters value: error: "email_body exceeds the maximum allowed size of 500,000 characters" '401': description: Authentication failed content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: DeepSeek rate limit exceeded content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: "LLM rate limit exceeded. Please retry shortly." '500': description: Internal server error (API key not configured) content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '502': description: LLM returned an unparseable response content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '504': description: DeepSeek API timed out content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' example: error: "LLM API timed out. Please retry." components: schemas: ExtractSignatureRequest: type: object required: - email_body properties: email_body: type: string description: > The raw body of the inbound email. Accepts plain text, HTML, or mixed content. HTML tags are stripped server-side before inference. Maximum 500,000 characters. Only the last 4,000 characters are sent to the LLM (signatures are always at the bottom). maxLength: 500000 example: | Hi Sarah, Looking forward to our call on Thursday. Best, Michael -- Sarah Jenkins Vice President of Sales Acme Corp | Austin, TX Office: +1-555-019-8372 s.jenkins@acmecorp.com sender_email: type: string description: > Optional. The envelope `From:` address of the inbound email. When provided, the LLM uses it as a verification hint to resolve ambiguous company or domain matches in the signature. default: "" example: s.jenkins@acmecorp.com ExtractSignatureResponse: type: object properties: status: type: string enum: [success] example: success contact_data: $ref: '#/components/schemas/ContactData' confidence_flags: $ref: '#/components/schemas/ConfidenceFlags' ContactData: type: object description: Structured contact record extracted from the email signature. properties: first_name: type: string nullable: true example: Sarah last_name: type: string nullable: true example: Jenkins job_title: type: string nullable: true example: Vice President of Sales company_name: type: string nullable: true example: Acme Corp email: type: string nullable: true example: s.jenkins@acmecorp.com phone_numbers: type: array description: All phone numbers found in the signature. Empty array if none found. items: $ref: '#/components/schemas/PhoneNumber' address: $ref: '#/components/schemas/Address' nullable: true description: Postal address from the signature. null if none found. social_links: type: array description: Social / profile URLs found in the signature. Empty array if none found. items: type: string format: uri example: - https://linkedin.com/in/sarahjenkins - https://twitter.com/sjenkinssales PhoneNumber: type: object required: [type, number] properties: type: type: string enum: [office, mobile, fax] description: Classification of the phone number based on labels in the signature. example: office number: type: string description: Phone number in international format (E.164-style with country code). example: "+1-555-019-8372" Address: type: object nullable: true properties: street: type: string nullable: true example: "123 Innovation Way, Suite 400" city: type: string nullable: true example: Austin state: type: string nullable: true example: TX postal_code: type: string nullable: true example: "78701" country: type: string nullable: true example: USA ConfidenceFlags: type: object properties: missing_fields: type: array description: > List of contact field names that could not be located in the signature. An empty array means all tracked fields were successfully extracted. Array fields (phone_numbers, social_links) are never included here — an empty array is the normal "none found" state for those. items: type: string example: [] ErrorResponse: type: object properties: error: type: string description: Human-readable error message. example: "Missing required field: email_body"