kawaa-com · Schema

BatchAccepted

What `POST /v1/verify/batch` answers with on acceptance. `unique_emails` is what the job will verify; `credits_used` is what was charged, and the two can differ when queueing some addresses could not be confirmed; see the fields themselves.

CompanyEmail VerificationSoftware-as-a-ServiceMarketing

Properties

Name Type Description
job_id string
status object
total_submitted integer Addresses in the request.
unique_emails integer Addresses CONFIRMED queued: what the job will actually verify. It is not always what was charged: when queueing some addresses cannot be confirmed, the API counts what it could confirm and reports the
duplicates_removed integer Removed before charging: the same address twice costs once.
invalid_emails_skipped integer Rejected as malformed and never verified. The results will be shorter than the list you sent.
credits_used number 0 on an idempotent replay: what this request charged, not what the batch cost. The batch's cost is its job's `credits_used` less `credits_refunded`, from `GET /v1/jobs/{id}`.
credits_remaining number Absent when the post-charge balance could not be safely recovered.
idempotent_replay boolean True when this returned an earlier submission's job and charged nothing.
dispatch_in_progress boolean A request under this same `Idempotency-Key` is still queueing the batch. Nothing more was charged. Retry after `Retry-After`, or poll the job.
enqueue_unknown integer How many sends could not be confirmed. Credits for them are HELD, not spent. Poll the job until it reconciles.
credits_held number Held pending reconciliation of an ambiguous enqueue. Not a settled charge.
include_activity boolean
message string
estimated_time_seconds integer A rough estimate of how long the job will take, at about two seconds per address. An estimate for a progress bar, not a deadline. Poll `GET /v1/jobs/{job_id}` for the truth.
enqueue_failures integer How many addresses the queue DEFINITIVELY rejected, present only when some were. Distinct from `enqueue_unknown`, which is "we do not know". Their credits are refunded where the refund succeeds; where
View JSON Schema on GitHub

JSON Schema

kawaa-com-batch-accepted-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://artifacts.apis.io/kawaa-com/json-schema/kawaa-com-batch-accepted-schema.json",
  "title": "BatchAccepted",
  "description": "What `POST /v1/verify/batch` answers with on acceptance. `unique_emails` is what the job will verify; `credits_used` is what was charged, and the two can differ when queueing some addresses could not be confirmed; see the fields themselves.",
  "x-generated": "2026-10-31",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/kawaa-com-openapi.json#/components/schemas/BatchAccepted",
  "type": "object",
  "properties": {
    "job_id": {
      "type": "string",
      "format": "uuid"
    },
    "status": {
      "$ref": "#/$defs/status"
    },
    "total_submitted": {
      "type": "integer",
      "description": "Addresses in the request."
    },
    "unique_emails": {
      "type": "integer",
      "description": "Addresses CONFIRMED queued: what the job will actually verify. It is not always what was charged: when queueing some addresses cannot be confirmed, the API counts what it could confirm and reports the rest in `enqueue_unknown`, so this can be lower than `credits_used` and, in the extreme, 0 on a job that charged. Reconcile billing against `credits_used` and `credits_held`, never against this count."
    },
    "duplicates_removed": {
      "type": "integer",
      "description": "Removed before charging: the same address twice costs once."
    },
    "invalid_emails_skipped": {
      "type": "integer",
      "description": "Rejected as malformed and never verified. The results will be shorter than the list you sent."
    },
    "credits_used": {
      "type": "number",
      "description": "0 on an idempotent replay: what this request charged, not what the batch cost. The batch's cost is its job's `credits_used` less `credits_refunded`, from `GET /v1/jobs/{id}`."
    },
    "credits_remaining": {
      "type": "number",
      "description": "Absent when the post-charge balance could not be safely recovered."
    },
    "idempotent_replay": {
      "type": "boolean",
      "description": "True when this returned an earlier submission's job and charged nothing."
    },
    "dispatch_in_progress": {
      "type": "boolean",
      "description": "A request under this same `Idempotency-Key` is still queueing the batch. Nothing more was charged. Retry after `Retry-After`, or poll the job."
    },
    "enqueue_unknown": {
      "type": "integer",
      "description": "How many sends could not be confirmed. Credits for them are HELD, not spent. Poll the job until it reconciles."
    },
    "credits_held": {
      "type": "number",
      "description": "Held pending reconciliation of an ambiguous enqueue. Not a settled charge."
    },
    "include_activity": {
      "type": "boolean"
    },
    "message": {
      "type": "string"
    },
    "estimated_time_seconds": {
      "type": "integer",
      "description": "A rough estimate of how long the job will take, at about two seconds per address. An estimate for a progress bar, not a deadline. Poll `GET /v1/jobs/{job_id}` for the truth."
    },
    "enqueue_failures": {
      "type": "integer",
      "description": "How many addresses the queue DEFINITIVELY rejected, present only when some were. Distinct from `enqueue_unknown`, which is \"we do not know\". Their credits are refunded where the refund succeeds; where it does not they stay held and `message` says so, so this number beside an unchanged `credits_used` is the case to reconcile rather than to retry."
    }
  },
  "required": [
    "job_id",
    "status",
    "total_submitted",
    "unique_emails",
    "credits_used"
  ]
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/kawaa-com-batch-accepted"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.