Documentation

Build reliable financial enrichment workflows with confidence

From first API call to production governance, this docs experience gives engineers and operators a clear path to implementation.

Start integrating Request a demo

Authentication

Secure credentials and request headers

Store keys in environment variables and send bearer authentication on every API request.

# .env.local
MAZERIK_API_KEY=your_key_here

curl -X POST https://api.mazerik.com/v1/txen/normalize \
  -H "Authorization: Bearer $MAZERIK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"transaction":{"description":"POS DEBIT COFFEE SHOP"}}'

Quickstart

Ship your first integration in under five minutes

Use these steps to move from credentials to a validated enrichment response with minimal setup.

Step 1

Create your API key

Generate a test key from your dashboard workspace and store it in `.env.local`.

Read details

Step 2

Send your first enrichment request

Call the normalize endpoint with one transaction payload to verify your integration path.

Read details

Step 3

Interpret structured output

Read entity, category, and recurrence fields to power underwriting and automation workflows.

Read details

Core concepts

Understand the enrichment model before you scale

These capabilities define how structured outputs map to underwriting, risk, and operations workflows.

Transaction normalization

Convert noisy descriptors into stable, operator-readable transaction records.

Explore concept

Entity intelligence

Resolve merchant and counterparty signals with confidence and supporting metadata.

Explore concept

Categorization

Map transactions into decision-friendly taxonomies with explainable assignment behavior.

Explore concept

Recurrence

Identify recurring patterns and expected cadence to support monitoring and cashflow analysis.

Explore concept

Endpoint snapshot

Key API surfaces your team will touch first

This high-level map helps teams align endpoint ownership before deep implementation.

POST/v1/txen/normalize

Normalize a transaction

Transforms raw transaction text into a standardized enrichment object.

Open docs page

POST/v1/txen/entities

Resolve entity metadata

Returns normalized merchant and counterparty identity attributes.

Open docs page

POST/v1/txen/categorize

Assign taxonomy category

Produces primary and secondary category labels with confidence context.

Open docs page

POST/v1/txen/recurrence

Classify recurrence

Detects recurring behavior and cadence hints for ongoing transaction series.

Open docs page

GET/v1/txen/health

Platform health

Checks service readiness before high-volume ingestion jobs.

Open docs page

POST/v1/events/verify

Verify webhook signature

Validates webhook signatures before downstream processing.

Open docs page

SDKs and tools

Choose your preferred implementation path

Use API-first integration for backend control or combine dashboard tooling for faster operator rollout.

Direct API

Integrate enrichment calls directly into your transaction processing services.

Dashboard

Validate payloads, inspect outputs, and accelerate onboarding for non-engineering teams.

Workflow tooling

Use webhooks and exports to synchronize enriched data with downstream systems.

Errors, retries, and limits

Operational guidance for resilient integrations

Handle transient failures safely with explicit retry logic, idempotency keys, and paced throughput.

Error matrix

authentication_error

401

Verify the Authorization header and ensure your key is active for the target environment.

validation_error

422

Inspect request schema mismatches and send only supported fields for the endpoint.

rate_limit_exceeded

429

Respect response retry headers and use exponential backoff with jitter.

service_unavailable

503

Retry with bounded backoff and preserve idempotency keys for safe replays.

Rate limit strategy

Respect retry headers and spread retries with jitter to avoid synchronized bursts.
Use idempotency keys when replaying requests after transport failures.
Keep ingestion queues bounded and process in batches to maintain steady throughput.

Webhooks

Operational event delivery with signature checks

Use webhook notifications to process enrichment lifecycle updates without polling loops.

Event payload shape

{
  "event": "txen.enrichment.completed",
  "occurred_at": "2026-03-24T10:42:00Z",
  "data": {
    "transaction_id": "txn_123",
    "status": "completed"
  }
}

Signature verification

Validate delivery signatures before processing events and reject stale timestamps outside your replay tolerance window.

Open webhook docs

Versioning

Plan upgrades with a predictable release model

Track endpoint lifecycle changes and keep production migrations controlled and auditable.

Recent changes

Added recurrence confidence reason codes and expected-next-date hints.
Expanded category taxonomy aliases for cross-market normalization.
Introduced webhook signature helper endpoint for operational validation workflows.

Read versioning guidance

FAQ

Answers for implementation and rollout teams

Common questions from engineering and operations teams adopting transaction intelligence in production.

Can we test with sandbox data before production onboarding?

Yes. Start with sandbox credentials and representative sample transactions, then migrate to production keys after workflow validation.

How should we handle retries in batch ingestion?

Retry only transient failures (`429`, `503`, network timeouts) with exponential backoff and preserve idempotency identifiers.

Do docs pages reflect API versioning changes?

Yes. Versioning and changelog guidance are maintained in the docs set so teams can plan upgrades safely.

Where can implementation teams get support during rollout?

Use the support and onboarding guidance in docs, then reach out through Contact for deployment planning.

Support and next steps

Need help with production rollout?

Work with our team on architecture decisions, rollout sequencing, and quality controls tuned to your risk and operations environment.

Request a demo Contact support

All guides

Browse every documentation page

Jump directly into topic-specific pages with sidebar navigation and structured MDX references.

Getting Started

Quickstart

Make your first transaction enrichment request and validate structured output.

Open page

Getting Started

Authentication

API key handling, authorization headers, and environment best practices.

Open page

Core Concepts

Transaction Normalization

Transform fragmented transaction text into stable, queryable records.

Open page

Capabilities

Entity Intelligence

Resolve merchant and counterparty context for transaction-level decisions.

Open page

Capabilities

Categorization

Apply consistent category labels to support risk and finance workflows.

Open page

Capabilities

Recurrence

Detect recurring transaction patterns and cadence trends.

Open page

API Reference

Endpoint Reference

Core endpoint map for normalization and enrichment workflows.

Open page

API Reference

Errors and Retries

Handle transient and validation failures safely in production.

Open page

API Reference

Rate Limits

Throughput planning and backoff behavior for stable ingestion.

Open page

API Reference

Webhooks

Event delivery patterns and signature verification guidance.

Open page

Operations

SDKs and Tools

Integration paths across API, dashboard, and operational tooling.

Open page

Operations

Versioning and Changelog

Plan API lifecycle upgrades with clear migration steps.

Open page

Operations

FAQ and Support

Common implementation questions and escalation guidance.

Open page

Operations

Integration Patterns

Proven architecture patterns for API, queue, and webhook-based deployments.

Open page

Operations

Observability and Monitoring

Metrics, logs, and alerting guidance for production enrichment workloads.

Open page

Build with confidence

Join hundreds of companies taking control of their transactions

Mazerik is the most accurate financial data standardization and enrichment API. Any data source, any geography.

Start building Request a demo