Anomaly Detection API

Identify values that deviate from the rest of a dataset, with the basis for each flag.

What it does

Flag values that look unusual against the rest of the dataset.

When to use it

Reach for Anomaly Detection when you need to answer: “What looks unusual?” It sits in the Detect stage of the catalog — surface anomalies and revenue exposure.

Endpoint & cost

POST /api/v1/anomalies

Cost: 3 Zaps. 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/anomalies \
  -H "Authorization: Bearer zap_live_••••••" \
  -H "Content-Type: application/json" \
  -d '{"records":[{"amount":100},{"amount":105},{"amount":98000}]}'

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 Anomaly Detection in the playground to see the request, or run it live with your API key.

Revenue Leakage — Analyze orders, invoices, and payments for revenue leakage and exposure.