Build coupon
flows, not guesswork.
Flicp gives developers one operating surface for coupon issuance, timed drops, auctions, FlicpToken-enabled payment flows, transfer events, and redemption.
The point is not abstract protocol language. The point is to help a team ship real coupon products across app, POS, internal tooling, and partner integrations without inventing separate logic for each.
Use this public site for guides, API concepts, and integration examples. Nominated developers manage their organisation's real API keys, webhook secrets, sandbox testing, and integration logs from the authenticated developer portal.
One API, every kind of offer.
Coupons
Create, check, redeem, and track coupons through one consistent API.
Timed drops
Schedule a release, cap the supply, and let Flicp run the countdown — no launch system to build.
Auctions + tokens
Run auctions and let customers claim offers with FlicpTokens — the same API handles both.
Transfer + audit
Every transfer and redemption leaves a clear record you can query and audit.
Keep the app simple.
Customers should see a clean product. Internal teams should see clear states. Developers should not need a different service for auctions, another for drops, and another for redemption.
Why teams build on Flicp- Idempotency keys, retries, and offline mode built in
- Same stacking rules verified across backend, SDK, and POS
- Org-nominated keys — revoking a nomination kills access instantly
const { FlicpClient } = require('@flicp/sdk');
const client = new FlicpClient({
apiKey: process.env.FLICP_API_KEY,
env: 'production',
});
// Verify connection
const status = await client.ping();
console.log(status.ok); // trueStart with the real product.
Build around the coupon lifecycle you actually run today: issue, drop, auction, transfer, redeem, and settle.