Model A

Brizz mints the codes

You pre-fund a campaign and Brizz generates the codes. Nothing is required from your engineering team — the API below is optional.

You build nothing

Machine-readable contract

The optional Partner API is published as OpenAPI at /coupon-integration/partner-api-v1.yaml — the same contract documented on Model B.

Flow

Everything the partner does happens before a customer ever checks out. The right-hand half of the partner lane is empty — that is what “you build nothing” looks like.

How the codes reach people

Brizz generates the code batch. Distribution is coordinated through the campaign's agreed channel and is currently an operational service, not an automated API capability — there is no per-recipient allocation, email/WhatsApp send or delivery tracking built into the platform yet.

Printed or QR coupon cards handed out at an event or booth.
One-to-one email or WhatsApp delivery operated by Brizz on your behalf.
A secure CSV handoff of the batch for you to distribute yourself.

A banner or newsletter advertises — it does not allocate

A campaign banner or a newsletter can promote the offer, but neither can hand a unique code to each visitor today. Automated per-recipient allocation — with consent, delivery status, retries and GDPR retention — would be a separate feature; talk to us before assuming it.

What you need from your side

OptionalNothing mandatoryA Brizz operator runs the campaign end to end from the internal admin dashboard — there is no partner portal to learn, and nothing below is required of you.
OptionalAn API keyOnly if you want to trigger minting or pull redemptions programmatically rather than from the dashboard.
OptionalA webhook URL and signing secretOnly if you would rather have redemption events pushed to you than poll for them.

Minting codes via the API

Brizz generates opaque codes into a campaign you own. Models A and B share one API — the authentication, endpoint list, scopes and reconciliation surface are documented on Model B; only the request body differs between minting and importing.

POST /api/partner/v1/campaigns/{uuid}/codes

# scope: codes:write
Authorization: Bearer brz_partner_<credential_id>.<secret>
Idempotency-Key: 7f3c…

{
  "quantity": 500,
  "prefix": "PARTNER"      // optional
}

Retry-safe

The Idempotency-Key header is required. A retry after a timeout returns the original batch — you can never accidentally mint twice.

Reconciliation

Identical to Model B: code.redeemed webhooks, the /redemptions endpoint, and downloadable reports.

Model BYou upload Model CReal-time