Brizz

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

Flow

PARTNERBRIZZEND USERAHEAD OF TIMEAT CHECKOUT — THE CUSTOMER IS WAITINGFunds campaignGenerates +distributes codesReceives codeEnters at checkoutMatched locallyDiscount appliedPays lessno partner involvement at checkout
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.

What you need from your side

  • OptionalNothing mandatoryA campaign can be run end to end from the Brizz dashboard by a non-technical operator. Everything below is a convenience, not a prerequisite.
  • 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 uploadModel CReal-time

Brizz uses cookies to improve your experience and measure site usage. You can manage your preferences at any time.