API Reference

A complete, machine-readable contract. Import the OpenAPI spec or Postman collection directly into your tools.

Base URL

https://zapinner.com/api/v1

Endpoints

POST/api/v1/repairrequires auth

Repair (flagship) — send messy data, get production-ready data back: infer schema, reconcile field names, normalize values, merge duplicates, flag anomalies, with a full audit trail.

POST/api/v1/maprequires auth

Map (flagship) — turn incoming data into the exact schema your application expects: infer field mappings, combine/split fields, and convert every value to the target type, with confidence and reasons.

POST/api/v1/guardrequires auth

Guard (flagship) — validate, repair, or reject data before it reaches your application: a per-record pass / repair / review / reject decision with reasons and configurable policy.

POST/api/v1/leads/recoveryrequires auth

Lead Recovery — score a single lead (also accepts a { leads: [] } convenience batch).

POST/api/v1/leads/recovery/batchrequires auth

Lead Recovery — score up to 1,000 leads and return an aggregated pipeline summary.

POST/api/v1/reconcilerequires auth

Reconciliation — compare two datasets and surface mismatches, duplicates, and missing records.

POST/api/v1/verifyrequires auth

Verification — check whether a claim is supported by the evidence supplied.

POST/api/v1/revenue-leakrequires auth

Revenue Leakage — find commercial discrepancies that may represent financial exposure.

GET/api/healthpublic

Non-sensitive service health and scoring version.

Authentication

All non-public endpoints require a Bearer API key. See Authentication. Send Authorization: Bearer zap_live_... with every request.

Conventions

Requests and responses are JSON. Timestamps are ISO 8601 (UTC). Monetary values are plain numbers in your own currency. Every response includes an X-Request-Id header that matches the request_id in the body.