Score API

Turn a record into a structured score you can sort and prioritize by, with every contributing factor exposed.

What it does

Produce a structured priority score with a transparent factor breakdown.

When to use it

Reach for Score when you need to answer: “How should I prioritize this?” It sits in the Decide stage of the catalog — score records and verify claims.

Endpoint & cost

POST /api/v1/score

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/score \
  -H "Authorization: Bearer zap_live_••••••" \
  -H "Content-Type: application/json" \
  -d '{"record":{"last_contact_days":210,"deal_size":48000}}'

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

Verification — Check whether a claim is actually supported by the evidence you supply.