Normalize API

Deterministically standardize names, amounts, dates, and other fields into a consistent, structured shape.

What it does

Turn messy, inconsistent fields into clean, structured, usable data.

When to use it

Reach for Normalize when you need to answer: “Turn messy data into usable data.” It sits in the Prepare stage of the catalog — clean and de-duplicate raw data.

Endpoint & cost

POST /api/v1/normalize

Cost: 1 Zap. Zaps draw down your shared monthly allowance; requests that fail validation are not charged.

Authentication

Send your key as a bearer token: Authorization: Bearer zap_live_…. See Authentication for key management and the alternate header.

Example request

curl https://zapinner.com/api/v1/normalize \
  -H "Authorization: Bearer zap_live_••••••" \
  -H "Content-Type: application/json" \
  -d '{"data":{"company":" ACME, INC. ","amount":"$1,245.00","date":"9/6/26"}}'

Every response is structured JSON and includes a request_id. Full field-level request and response schemas for this endpoint live in the OpenAPI spec and the API reference.

Errors & limits

Errors use one consistent shape ( error.code, error.message, request_id). See Errors and Rate limits.

SDK

The TypeScript SDK (@zapinner/sdk) is coming soon. Until it ships, call the endpoint over HTTPS with the example above — the API is plain JSON and needs no dependency.

Try it

Select Normalize in the playground to see the request, or run it live with your API key.

Dedupe — Find duplicate records within a dataset.