Skip to content
Back to skills

Email Normalize Post Batch

ASecurity

Normalizes up to 100 email addresses in one request. Results are in the same order as the input. Each item includes valid (boolean); when false, only original and message are set. Usage is billed per email processed (see gateway usage headers).

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
ai-agentsapi

Works with

  • api

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add bobadilla-tech/requiems-api-skills --skill email-normalize-post-batch --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Email Normalize Post Batch?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Email Normalize Post Batch
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/bobadilla-tech-email-normalize-post-batch/badge)](https://www.skillsdirectory.com/skills/bobadilla-tech-email-normalize-post-batch)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: email-normalize-post-batch
api: Email Normalizer
method: POST
path: /v1/text/normalize/batch
base_url: https://requiems.xyz
description: Normalizes up to 100 email addresses in one request. Results are in the same order as the input. Each item includes valid (boolean); when false, only original and message are set. Usage is billed per email processed (see gateway usage headers).
---

## Endpoint

**POST https://requiems.xyz/v1/text/normalize/batch**

## Normalize Email Batch

Normalizes up to 100 email addresses in one request. Results are in the same order as the input. Each item includes valid (boolean); when false, only original and message are set. Usage is billed per email processed (see gateway usage headers).

## Parameters

| Name | Type | Required | Location | Description |
| ---- | ---- | -------- | -------- | ----------- |
| `emails` | array<string> | yes | body | Array of addresses to normalize (min 1, max 100; each entry non-empty) |

## Request Example

```json
{
  "emails": [
    "user@example.com",
    "not-an-email",
    "te.st@gmail.com"
  ]
}
```

## Response Example

```json
{
  "data": {
    "results": [
      {
        "original": "user@example.com",
        "normalized": "user@example.com",
        "local": "user",
        "domain": "example.com",
        "changes": [],
        "valid": true
      },
      {
        "original": "not-an-email",
        "valid": false,
        "message": "invalid email address"
      },
      {
        "original": "te.st@gmail.com",
        "normalized": "test@gmail.com",
        "local": "test",
        "domain": "gmail.com",
        "changes": ["lowercased", "removed_dots"],
        "valid": true
      }
    ],
    "total": 3
  },
  "metadata": {
    "timestamp": "2026-01-01T00:00:00Z"
  }
}
```

## Response Fields

| Field | Type | Description |
| ----- | ---- | ----------- |
| `results` | array<object> | One normalization result per input email, in order |
| `total` | integer | Number of emails in the batch (same as results length) |

## Errors

- `422` **validation_failed** — Missing emails, empty array, too many items, or empty string in the array
- `400` **bad_request** — Invalid JSON or unknown fields in the body

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…