Leadmagic logo

Validate Email (LeadMagic)

LeadMagicValidate Email (LeadMagic)

POST/v1/leadmagic-email-validation
texau__leadmagic-email-validationenrichment
cURL · api.texau.app
84ms
POST/v1/leadmagic-email-validation
{
  "email": "[email protected]"
}
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]",
    "email_status": "[email protected]",
    "message": "sample",
    "mx_provider": "sample",
    "mx_security_gateway": true,
    "company_name": "sample",
    "company_size": "sample",
    "company_industry": "sample",
    "company_profile_id": "rec_4f3a91"
  }
}

Validates a given email address and returns verification status along with enriched company details using LeadMagic.

Install

Add validate email (leadmagic) to your MCP client.

Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__leadmagic-email-validation

When to use this.

The leadmagic-email-validation action is designed to validate email addresses and provide enriched company details through LeadMagic's robust API. By inputting an email address, users can ascertain its verification status and gain insights into the associated company, including its name, size, and industry. The key input parameter is the 'email' (text), which is essential for initiating the validation process. The output fields include the validated 'email' (email), 'email_status' (text), and a detailed 'message', along with technical data such as 'mx_provider' (text) and 'mx_security_gateway' (boolean). This action is particularly useful for marketing professionals, sales teams, and data analysts who need to ensure the accuracy of their email lists and enhance their lead enrichment processes. By categorizing this action under enrichment, it highlights its role in improving data quality and driving effective outreach strategies.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Validate Email (LeadMagic)

Try it

The email address you want to validate.

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • email
    Email
    text
  • email_status
    Email Status
    text
  • message
    Message
    nullabletext
  • mx_provider
    Mx Provider
    text
  • mx_security_gateway
    Mx Security Gateway
    nullableboolean
  • company_name
    Company Name
    text
  • company_size
    Company Size
    nullabletext
  • company_industry
    Company Industry
    text
  • company_profile_id
    Company Profile Id
    nullabletext

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/leadmagic-email-validation. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/leadmagic-email-validation
curl -X POST 'https://v3-api.texau.com/api/v1/leadmagic-email-validation' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"email":"[email protected]"}'
200 Accepted
{
  "ok": true,
  "data": {
    "email": "[email protected]",
    "email_status": "[email protected]",
    "message": "sample",
    "mx_provider": "sample",
    "mx_security_gateway": true,
    "company_name": "sample",
    "company_size": "sample",
    "company_industry": "sample",
    "company_profile_id": "rec_4f3a91"
  }
}

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → validate email (leadmagic) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Validate Email (LeadMagic)LeadMagic action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

Reliability

Rate limits & reliability.

  • Per-minute limit3000 / min
  • Per-day limit10,000 / day
  • RetriesAutomatic w/ backoff
  • ModeSync

Errors

HTTP status codes.

What each response means and what to do about it.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Light tier

Pricing tier on /pricing. Per-action credit cost is private.

FAQ.

  • Is this real-time?

    Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).

  • Do I get charged on failure?

    No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.

  • Does it work with Claude / Cursor via MCP?

    Yes. Add the texau MCP server to your client config, then call `texau__leadmagic-...` directly.

  • What CRMs can I push results to?

    HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.

Run Validate Email (LeadMagic) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.