# ZeroCut complete website corpus > Public product, company, comparison, use-case, changelog, policy-summary, documentation, and REST API reference content for ZeroCut. This file is designed for AI retrieval and offline indexing. Sections preserve their canonical and Markdown URLs. Private account pages and user-specific authenticated data are excluded. --- # ZeroCut > Create a stream-ready donation page with 0% platform fees, OBS alerts, Stripe and PayPal payments, Discord donor roles, and revenue analytics. - Canonical page: https://zerocut.gg/ - Markdown version: https://zerocut.gg/index.md ## What ZeroCut is ZeroCut is a donation and revenue platform for streamers, content creators, developers, and other online creators. A creator gets a customizable public donation page, direct Stripe and PayPal payments, browser-source alerts for streaming software, Discord donor tools, and analytics that connect visits, live sessions, and donations. ZeroCut charges no percentage platform fee on donations. Standard payment-processing fees from Stripe or PayPal can still apply. Money is processed by the connected provider rather than being held by ZeroCut. ## Core product - **Donation pages:** A public page at `zerocut.gg/{handle}` with preset or custom amounts, optional donor messages, social links, donation goals, and creator branding. - **Payments:** Stripe and PayPal support, including card payments and provider-supported wallets such as Apple Pay and Google Pay. Availability depends on the creator's payment provider and country. - **Stream alerts:** Browser-source overlays for OBS, Streamlabs, TikTok Studio, and similar broadcasting tools. Creators can configure sounds, images, text, and alert tiers. - **Revenue analytics:** Donation totals, top donors, countries, activity, live-session revenue, page traffic, conversion data, and real-time visitor activity. - **Discord integration:** Donation notifications, donor-to-Discord mapping, automatic roles, leaderboards, and configurable bot behavior. - **Developer tools:** REST API access, API keys, outgoing webhooks, and embeddable donation, follower, leaderboard, goal, and donation-total widgets. - **Branding:** Theme and color controls, custom messages and amounts, optional removal of ZeroCut branding, and custom domains. ## Pricing ZeroCut combines lifetime Basic access with recurring Premium subscriptions: - **Basic, $20 lifetime:** 0% platform fees, unlimited donations, a standard donation page, basic stream alerts, Stripe and PayPal support, Insights, and donation analytics fixed to the most recent 30 days. It does not include page customization, visitor, platform, or comparison analytics, Live Log, Live Map, or team access, and its ZeroCut watermark stays visible. - **Premium has two subscription choices:** Choose 3 months of Premium for $50, then the current $5.99/month rate, which may change with at least 30 days' notice. Or start at $19.99/month and keep that base Premium rate while the same subscription remains active. The introductory renewal can be canceled before a notified rate change takes effect. Both choices include broader customization, removable ZeroCut branding, Discord webhooks and automation, advanced analytics, one collaborator seat, and priority support. - **Legacy lifetime Premium:** A completed former $50 lifetime Premium purchase remains a lifetime grant. It does not include recurring add-ons or separately purchased collaborator seats. - **Trial:** The seven-day trial begins after the creator receives their first donation. No credit card is required to start. - **Custom domains:** A monthly component on the same recurring bill: $5/month with Basic or $1/month with Premium. Prices offered to new subscribers and plan details can change. Once subscribed, the renewal policy shown for the chosen offer applies. Confirm current terms on the canonical website before making a purchase. ## How setup works 1. Sign in and choose a public handle. 2. Connect Stripe or PayPal through the provider's authorization flow. 3. Customize the donation page, branding, defaults, alerts, and integrations. 4. Share the public donation link in stream panels, video descriptions, social bios, Discord, a website, or anywhere else. 5. Add optional browser-source overlay URLs to broadcasting software and configure Discord, webhooks, embeds, or API access as needed. ## Frequently asked questions ### Really? 0% fees? Yes. ZeroCut does not take a cut. Stripe or PayPal still charge their normal processing fees, but we add $0 on top. ### How do I get paid? Payouts are handled directly through Stripe or PayPal. Money goes straight to your account, usually instantly or within a standard rolling window depending on the provider. ### How does Premium billing work? Choose 3 months of Premium for $50, then the current $5.99/month rate, which may change with at least 30 days' notice. Or start at $19.99/month and keep that base Premium rate while the same subscription remains active. Custom domains and other add-ons are priced separately. ### Can I use this on Twitch/YouTube/TikTok? Yes. Put the link in Twitch panels, YouTube descriptions, TikTok bio, Discord, X, or anywhere else. Alerts use browser source URLs, so they work in OBS, Streamlabs, TikTok Studio, and similar broadcasting tools. ### Is my data secure? We do not store card numbers. Stripe and PayPal process payments directly, and sensitive app data is encrypted where it needs to be. ### I already use Streamlabs. Can I migrate my donors? Yes. Switch your panel link / bio link to your new ZeroCut page whenever you're ready — your existing donors will just see a new, faster donation page. Past donation history stays with Streamlabs; from day one with ZeroCut, every new dollar is yours. ### Do my fans need to sign up to donate? No. Supporters open your page, tap an amount, pay with card / Apple Pay / Google Pay / PayPal — done. No account, no password, no friction. ### Do I need to handle taxes? Yes. The money goes from Stripe or PayPal to you, so tax reporting is between you, the processor, and your local tax authority. ZeroCut never holds the money, so we do not issue tax forms for donations. ### What if I cancel or stop using ZeroCut? Basic is a $20 lifetime purchase with no renewal. You can cancel Premium from Billing to stop future renewals. A canceled Premium subscription keeps access through the paid period, then the account returns to its available non-Premium access. ### Is this better than Ko-fi or Buy Me a Coffee? For live donations, yes. ZeroCut has OBS alerts, Discord integrations, and stream-to-revenue analytics. Ko-fi and Buy Me a Coffee do more for shops and memberships. If the job is taking donations without losing 5%, ZeroCut is the sharper tool. ## Important links - [Documentation](https://zerocut.gg/docs.md) - [Live product demo](https://zerocut.gg/demo.md) - [Changelog](https://zerocut.gg/changelog.md) - [Contact](https://zerocut.gg/contact.md) - [Full AI-readable website corpus](https://zerocut.gg/llms-full.txt) --- # Free tools > Free tools for creating channel art. One generation is available before sign-in. - Canonical page: https://zerocut.gg/tools - Markdown version: https://zerocut.gg/tools.md ## Available now - [Creator art studio](https://zerocut.gg/tools/creator-studio.md): Start with clean ZeroCut art, then add color, structure, motion, or more signal. The studio is live and works without an account. That's the whole catalog today. There are no placeholder listings for unfinished ideas. These tools create static files. Live alerts, goals, chat, timers, and other broadcast widgets use ZeroCut and OBS-compatible browser-source integrations instead. --- # Creator art studio > Make banners, panels, thumbnails, and profile marks in your colors, then download PNG or SVG files. - Canonical page: https://zerocut.gg/tools/creator-studio - Markdown version: https://zerocut.gg/tools/creator-studio.md ## What it makes - Static stream scenes, banners, channel headers, thumbnails, panels, vertical covers, and square posts. - Profile marks and emotes sized for small identity uses. - PNG files at standard and high resolution, editable SVG files, and an embed snippet. Pick a design. Change the style, colors, text, or uploaded image. Reroll to generate another seed. The studio downloads files but does not publish to streaming or social accounts. ## Watermark behavior Large free exports include a ZeroCut watermark. Premium accounts can turn it off. Profile marks and emotes never include the watermark. SVG files remain editable after download, so the watermark is a product rule rather than a security boundary. ## Boundaries The studio makes static art. Live alerts, goals, chat, and timers require ZeroCut's live widgets and an OBS-compatible browser source. In-context views are plain proportion guides, not copied platform interfaces, logos, colors, or official layouts. Users may upload custom images they own or have permission to use. They are responsible for the rights to uploaded assets. [Browse every free tool](https://zerocut.gg/tools.md) --- # ZeroCut live demo > Explore a read-only ZeroCut creator dashboard without creating an account. - Canonical page: https://zerocut.gg/demo - Markdown version: https://zerocut.gg/demo.md ## What the demo shows The public demo presents the same main dashboard surfaces available to a creator account, backed by showcase data. It includes headline donation and follower metrics, period comparisons, recent donations, live sessions, donation goals, top activity, top donors, top countries, Discord-connected donors, and the real-time visitor map. The demo is read-only. It is intended for evaluating the product interface and analytics workflow before signing up; it does not expose a real creator's private account or permit account mutations. ## Continue exploring - [Open the interactive demo](https://zerocut.gg/demo) - [Read the feature documentation](https://zerocut.gg/docs/features.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # Create or sign in to a ZeroCut account > Start a ZeroCut donation page or return to an existing creator account using Google or Discord. - Canonical page: https://zerocut.gg/sign-in - Markdown version: https://zerocut.gg/sign-in.md ## Account access ZeroCut uses Google or Discord for account authentication. Creating an account is free to start and does not require a credit card. After sign-in, new creators are guided through choosing a public handle, connecting a payment provider, setting a currency, and configuring their donation page. The seven-day product trial begins when the account receives its first donation, not when the account is created. Supporters do not need a ZeroCut account to donate. [Open the secure sign-in page](https://zerocut.gg/sign-in) --- # Contact ZeroCut > Contact ZeroCut about support, creator partnerships, billing, press, feedback, or the product. - Canonical page: https://zerocut.gg/contact - Markdown version: https://zerocut.gg/contact.md ## Ways to get help Use the contact form for product questions, account support, billing questions, partnerships, press, or anything else related to ZeroCut. Include an email address, select the most relevant reason, and describe the issue or request. Do not include passwords, full card details, API secrets, webhook secrets, or other sensitive credentials. You can also email [contact@zerocut.gg](mailto:contact@zerocut.gg). For bugs and feature requests that other users should be able to discuss and upvote, use the public [feedback and roadmap page](https://zerocut.gg/feedback.md). --- # ZeroCut feedback and roadmap > Browse, submit, and upvote ZeroCut bugs, feature requests, and product ideas. - Canonical page: https://zerocut.gg/feedback - Markdown version: https://zerocut.gg/feedback.md ## How the roadmap works The feedback board is the public place for ZeroCut bugs, feature requests, and early product ideas. Visitors can browse and sort existing submissions. Signed-in users can submit feedback, add comments, and upvote the items that matter to them. The board is intentionally public so creators can see what has already been reported and help prioritize the roadmap. For private account, payment, or security questions, use the [contact page](https://zerocut.gg/contact.md) instead of posting sensitive information publicly. --- # ZeroCut Founding Streamers program > Apply for free lifetime ZeroCut Premium in exchange for using the product, sharing honest feedback, and keeping a small stream-overlay watermark. - Canonical page: https://zerocut.gg/sponsors - Markdown version: https://zerocut.gg/sponsors.md ## The offer Approved Founding Streamers receive Premium free for life as a program benefit and keep it even if they later leave the program. This is a sponsor grant, not one of the paid Premium subscription offers. The program also includes a direct line to the founder, input on the roadmap, early access to new features, and a permanent public founder credit. There is no trial clock, payment card, or later clawback. ## What ZeroCut asks in return 1. Keep a small, non-intrusive ZeroCut watermark on the stream overlay while participating. 2. Send at least one honest piece of product feedback each month through whichever channel is easiest. 3. Mention ZeroCut when it comes up naturally, without posting quotas, scripted endorsements, or forced testimonial videos. There is no minimum channel size. Consistent streaming and genuine product use matter more than subscriber count. The current program is limited to 100 spots, and applications are generally reviewed within 72 hours. ## Application Email [david@zerocut.gg](mailto:david@zerocut.gg?subject=Founding%20Streamer%20application) with your channel URL, how often you stream, and a short note about what frustrates you about your current way of receiving donations. You can also use the [contact page](https://zerocut.gg/contact.md). --- # ZeroCut Privacy Policy > How ZeroCut collects, uses, protects, and shares information. - Canonical page: https://zerocut.gg/privacy-policy - Markdown version: https://zerocut.gg/privacy-policy.md ## Plain-language summary ZeroCut collects account information such as a display name and email address, plus service usage, device, and cookie data needed to operate and improve the platform. Stripe and PayPal process payment details; ZeroCut does not directly store full card numbers or bank-account credentials. Information is used to provide accounts and donation services, communicate important updates, analyze and improve the service, and protect against fraud or unauthorized access. ZeroCut does not sell or rent personal information for third-party marketing. Information may be shared with payment processors and necessary service providers, disclosed when legally required, or transferred as part of a business transaction subject to applicable safeguards. Users can access and update account information, request deletion, manage browser cookies, and opt out of non-essential communications. ZeroCut is intended for people aged 18 or older. This Markdown page is a discovery summary, not a replacement for the policy. Read the [canonical Privacy Policy](https://zerocut.gg/privacy-policy) for the complete, authoritative terms and contact [contact@zerocut.gg](mailto:contact@zerocut.gg) with privacy requests. --- # ZeroCut Terms of Service > The terms governing ZeroCut accounts, payments, plans, custom domains, and use. - Canonical page: https://zerocut.gg/terms-of-service - Markdown version: https://zerocut.gg/terms-of-service.md ## Plain-language summary Users must be at least 18, have legal capacity to agree to the terms, provide accurate account information, protect their credentials, and comply with applicable laws. Stripe or PayPal must be connected to receive donations. ZeroCut charges no percentage platform fee, while payment processors may apply their own fees and payout rules. Basic is a lifetime purchase with the limits described on the pricing page. Premium is a recurring subscription under the offer selected at checkout and may be canceled for future renewal. Choose 3 months of Premium for $50, then the current $5.99/month rate, which may change with at least 30 days' notice. Or start at $19.99/month and keep that base Premium rate while the same subscription remains active. The introductory renewal can be canceled before a notified rate change takes effect. A payment-retry grace period does not by itself end the monthly price lock, but cancellation, expiration, termination, or an unresolved payment failure that ends the subscription does. Taxes, add-ons, and provider fees are outside the lock. A completed former $50 lifetime Premium purchase remains a lifetime grant and does not require a new Premium subscription. Premium includes additional customization, Discord tools, analytics, and one collaborator seat; extra collaborator seats are separate lifetime purchases. Custom domains are a monthly component on the same ZeroCut subscription and require the user to control the domain, configure DNS correctly, keep registration active, and take responsibility for content served on that domain. A full refund or an opened or lost dispute affecting a Premium subscription payment ends the composed subscription and its recurring components; a partial refund does not by itself cancel it. Prohibited uses include unlawful, fraudulent, deceptive, hateful, infringing, phishing, malware, or abusive activity. ZeroCut can suspend accounts, disable custom domains, remove content, or cooperate with competent authorities when needed to enforce the terms and applicable law. This Markdown page is a discovery summary, not a replacement for the agreement. Read the [canonical Terms of Service](https://zerocut.gg/terms-of-service) for the complete, authoritative terms and contact [contact@zerocut.gg](mailto:contact@zerocut.gg) with questions. --- # ZeroCut for Streamers — Live Alerts, 0% Fees, Instant Payouts > Accept donations on Twitch, YouTube, and TikTok with 0% platform fees. Live OBS alerts, Discord integration, and instant payouts. - Canonical page: https://zerocut.gg/for/streamers - Markdown version: https://zerocut.gg/for/streamers.md ## You're live. Someone donates. The alert fires. Money hits your account. That's the whole product. No catch. ## Problems this setup addresses 1. **Platforms eat your earnings.** You built an audience from nothing. Then the tipping platform takes its cut on top of processing fees. You're losing money just for the privilege of being paid. 2. **Your alerts look like everyone else's.** Default donation alerts are generic. Every streamer has the same pop-up, the same sound, the same look. Your brand deserves better than a template. 3. **Payouts take forever.** You had a great stream tonight. Too bad the money won't show up for days — or weeks if the platform has a minimum threshold. ## Relevant ZeroCut features 1. **0% Platform Fee.** We don't touch your donations. Only standard Stripe or PayPal processing fees apply. 2. **Custom Stream Alerts.** Design alerts that match your brand. Custom sounds, images, and text — delivered via OBS browser source. 3. **Instant Payouts.** Money goes to your Stripe or PayPal account directly. No holding period, no minimum threshold. 4. **Discord Integration.** Automatic role assignments for donors, live notifications in your server, and full donor management. ## Setup 1. **Sign up and connect Stripe or PayPal.** Takes about 2 minutes. We walk you through it. 2. **Add the browser source to OBS.** Copy a URL, paste it into OBS. Your alerts are live. 3. **Share your donation link.** Drop it in your Twitch panels, YouTube description, or stream chat. ## Next step ### Get paid from your next stream 7-day free trial. Your trial doesn't start until you receive your first donation. - 0% platform fees - 7-day free trial - No credit card required - [Read the getting-started guide](https://zerocut.gg/docs/getting-started.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # ZeroCut for Content Creators — One Link, Zero Fees > Accept donations from your audience on YouTube, TikTok, podcasts, and more. Custom branded page, 0% platform fees, instant payouts. - Canonical page: https://zerocut.gg/for/content-creators - Markdown version: https://zerocut.gg/for/content-creators.md ## Not every creator goes live. You still deserve to get paid. A donation page that works wherever your audience is. ## Problems this setup addresses 1. **Monetization is fragmented.** You're on YouTube, TikTok, Instagram, and maybe a podcast. Each platform has its own tip jar, and none of them work together. 2. **Platform fees stack up.** YouTube Super Chat takes 30%. Patreon takes 5-12%. Buy Me a Coffee takes 5%. Your audience wants to support you, but the platforms take the first bite. 3. **Your brand gets buried.** When someone donates through a third-party platform, they see that platform's branding. Your supporters should feel like they're supporting you — not some company in the middle. ## Relevant ZeroCut features 1. **One Link for Everything.** A single donation page you can put anywhere — bio links, video descriptions, podcast show notes, newsletters. 2. **Your Brand, Your Page.** Custom colors, logos, and your own domain. Supporters see your brand, not ours. 3. **Stripe + PayPal.** Your audience pays however they prefer. Cards, Apple Pay, Google Pay, PayPal — all covered. 4. **Real Analytics.** See who's donating, how much, and when. Track trends and understand what's working. ## Setup 1. **Create your donation page.** Pick your handle, connect a payment provider, and you're live in under 2 minutes. 2. **Make it yours.** Add your brand colors, logo, and optionally connect your own custom domain. 3. **Link it everywhere.** Bio links, video descriptions, email signatures — one URL that works across every platform. ## Next step ### Give your audience a way to support you Set up takes under 2 minutes. Free trial included. - 0% platform fees - Custom branding - No credit card required - [Read the getting-started guide](https://zerocut.gg/docs/getting-started.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # ZeroCut for Developers — API, Webhooks, Zero Fees > Accept sponsorships and donations for your open source work. Full REST API, webhook notifications, Discord integration. 0% platform fees. - Canonical page: https://zerocut.gg/for/developers - Markdown version: https://zerocut.gg/for/developers.md ## You built something people use every day. You should get paid for it. Webhooks, API access, and no paperwork. ## Problems this setup addresses 1. **GitHub Sponsors has a waitlist.** You applied months ago. Still waiting. Meanwhile, people want to fund your work and there's no straightforward way to accept it. 2. **Payment infrastructure is a rabbit hole.** Stripe integration, webhook handling, compliance, tax forms... You wanted to write code, not build a fintech side project. 3. **Existing platforms don't get developers.** Ko-fi and Buy Me a Coffee are built for people making videos, not shipping software. No API, limited webhooks, no way to integrate donations into your workflow. ## Relevant ZeroCut features 1. **Full REST API.** Read donations, followers, live sessions, and analytics with ZeroCut Premium. Build custom integrations with your own API key. 2. **Webhook Notifications.** Get notified instantly when someone donates. Trigger builds, update your README, send a thank-you — automatically. 3. **Embeddable Widget.** Drop a donation widget into your docs, project page, or README. A few lines of code, done. 4. **Discord Bot.** Automatic role assignments and notifications for your project's Discord. Reward supporters without manual work. ## Setup 1. **Sign up and connect Stripe or PayPal.** Connect your own Stripe or PayPal account to receive payments. 2. **Grab your API key and webhook URL.** With ZeroCut Premium, create an API key in settings and follow the REST API docs. 3. **Integrate or just share the link.** Embed the widget, wire up webhooks, or just paste the link in your README. ## Next step ### Start accepting sponsorships for your work REST API access is included with ZeroCut Premium. - Full REST API - Webhook notifications - No credit card required - [Read the getting-started guide](https://zerocut.gg/docs/getting-started.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # ZeroCut — Instant Payouts, No Minimums, No Waiting > Get paid instantly with Stripe or PayPal. No minimum thresholds, no monthly payout cycles, no platform holding your money. - Canonical page: https://zerocut.gg/for/fast-payouts - Markdown version: https://zerocut.gg/for/fast-payouts.md ## Your money shouldn't sit in someone else's account. Instant payouts through Stripe. Same-day through PayPal. No minimums. ## Problems this setup addresses 1. **Your money sits in limbo.** You earned it today, but the platform says you can't have it until next week. Or next month. Net-30, minimum thresholds — all ways to hold your cash. 2. **Hidden fees chip away at payouts.** Platform cut, processing fee, withdrawal fee. By the time money reaches your account, it's noticeably lighter than what your supporter actually sent. 3. **No transparency on timing.** The dashboard says 'processing.' It's been saying that for three days. You check tomorrow — still processing. No ETA, no explanation. ## Relevant ZeroCut features 1. **Stripe Instant Payouts.** With Stripe, payouts can arrive in minutes — not days. Enable instant payouts and the money moves fast. 2. **PayPal Direct.** Donations hit your PayPal balance immediately. Withdraw to your bank whenever you want. 3. **No Minimums.** One dollar or one thousand. Withdraw whenever you want. No minimum payout threshold standing between you and your money. 4. **Real-time Dashboard.** Watch donations come in live. Know exactly how much you've earned and when it arrives. ## Setup 1. **Connect Stripe or PayPal.** Five minutes to set up. We guide you through the whole thing. 2. **Receive your first donation.** Share your link, embed the widget, or add it to your stream. 3. **Money arrives — no waiting.** Stripe instant payouts or PayPal direct. Your money, on your schedule. ## Next step ### Stop waiting for your money Connect Stripe or PayPal and start receiving instant payouts. - Instant Stripe payouts - No minimums - No credit card required - [Read the getting-started guide](https://zerocut.gg/docs/getting-started.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # ZeroCut vs Streamlabs — 0% Platform Fees > Compare ZeroCut and Streamlabs side by side: 0% platform fees, a lifetime Basic tier, donation alerts, and stream revenue analytics. - Canonical page: https://zerocut.gg/compare/streamlabs - Markdown version: https://zerocut.gg/compare/streamlabs.md ## Streamlabs charges monthly. ZeroCut Basic charges once. You didn't start streaming to figure out subscription tiers and platform fees. Streamlabs is a full streaming suite — software, alerts, themes, merch, and more. It does a lot, and plenty of streamers rely on it. But if donations are your bread and butter, you're paying monthly for features you might never touch while the platform takes its cut. ZeroCut handles donations, handles them well, and stays out of your wallet. And it's the only one that shows you which stream actually made the money — every session, every dollar, every visitor who didn't donate, side by side. ## Feature comparison | Feature | ZeroCut | Streamlabs | | --- | --- | --- | | Platform Fee | 0% | Varies | | Pricing Model | From $20 lifetime | $25/month | | Donation Alerts | Yes | Yes | | Custom Overlays | Yes | Yes | | Stripe Support | Yes | Yes | | PayPal Support | Yes | Yes | | Custom Domains | Yes | No | | Discord Integration | Yes | Limited | | API & Webhooks | Yes | Limited | | Streaming Software | No | Yes | | Merch Store | No | Yes | ## Pricing model - **Streamlabs: $25/month.** Streamlabs Ultra subscription. That's $300/year to keep your features running. - **ZeroCut: From $20 one-time.** Basic is a lifetime purchase. Premium is an optional recurring subscription. Prices and competitor details can change. Verify current pricing and capabilities with each provider. ## Where ZeroCut differs 1. **Your money stays yours.** 0% platform fee on every donation. Only standard Stripe or PayPal processing fees apply — fees we don't control and don't profit from. 2. **Basic is yours for life.** Pay for Basic once and keep it for life. Premium is there if you need its extra tools. 3. **Revenue-first analytics.** Streamlabs shows donations. ZeroCut connects every stream you go live to every dollar that comes in — plus every visitor who opened your page and left without giving. The 94% who almost donated are your biggest growth lever, and we're the only platform that shows them to you. ## Honest fit ### Use Streamlabs when - You want an all-in-one streaming suite with desktop software - You need a built-in merch store and theme marketplace - You're deep in the Streamlabs ecosystem and switching feels expensive ### Use ZeroCut when - Donations are your main revenue and you want every dollar - You want a lifetime Basic tier instead of another required monthly plan - You want to know which stream actually made the money — not just that money came in ## Learn more - [ZeroCut features](https://zerocut.gg/docs/features.md) - [ZeroCut pricing and product overview](https://zerocut.gg/index.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # ZeroCut vs StreamElements — Donations Without the Extras > Compare ZeroCut and StreamElements. Both handle donations, but ZeroCut keeps it simple with 0% fees and a lifetime Basic tier. - Canonical page: https://zerocut.gg/compare/streamelements - Markdown version: https://zerocut.gg/compare/streamelements.md ## StreamElements gives you everything. We give you the one thing that matters. Sometimes less software is the answer. StreamElements is a full production suite — alerts, overlays, chatbot, loyalty points, merch store. If you want all of that bundled together, it's solid. But if you just need donations to work without a platform taking a cut, ZeroCut is sharper and simpler. No ecosystem lock-in, no feature overload. And ZeroCut is the only donation platform that tracks three things at once: every session you stream, every dollar it earns, and every visitor who opened your tip page and never donated. ## Feature comparison | Feature | ZeroCut | StreamElements | | --- | --- | --- | | Platform Fee | 0% | 0% on tips | | Pricing Model | From $20 lifetime | Free + paid tiers | | Donation Alerts | Yes | Yes | | Custom Domains | Yes | No | | Discord Integration | Yes | Limited | | API & Webhooks | Yes | Yes | | Chatbot | No | Yes | | Loyalty Points | No | Yes | | Merch Store | No | Yes | ## Pricing model - **StreamElements: Free (with extras).** Base tools are free. Revenue comes from merch sales, sponsorships, and premium features. - **ZeroCut: From $20 one-time.** Basic is a lifetime purchase. Premium is an optional recurring subscription. Prices and competitor details can change. Verify current pricing and capabilities with each provider. ## Where ZeroCut differs 1. **No ecosystem lock-in.** Your data, your payment accounts, your donors. ZeroCut doesn't try to become your entire streaming stack. 2. **Professional custom domains.** Run donations from your own domain. donate.yourname.com looks a lot better than a generic platform URL. 3. **Analytics built around revenue, not engagement.** StreamElements tracks chat messages and loyalty points. ZeroCut tracks what pays your rent — every stream you go live, every dollar it made, and every visitor who left your tip page without donating. One dashboard. Three numbers that matter. ## Honest fit ### Use StreamElements when - You want a full streaming toolkit — chatbot, loyalty, overlays, and more - You need merch store integration built into your streaming platform - You prefer a free tier and don't mind the trade-offs ### Use ZeroCut when - You already have OBS and just need clean donation handling - Custom branding and your own domain matter to you - You want to know which stream actually makes money — and which visitors are walking away ## Learn more - [ZeroCut features](https://zerocut.gg/docs/features.md) - [ZeroCut pricing and product overview](https://zerocut.gg/index.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # ZeroCut vs Tipeeestream — Zero Commissions, Lifetime Basic > Compare ZeroCut and Tipeeestream: no ZeroCut commission, a lifetime Basic tier, donation alerts, and Stripe/PayPal support. - Canonical page: https://zerocut.gg/compare/tipeeestream - Markdown version: https://zerocut.gg/compare/tipeeestream.md ## Tipeeestream takes commissions. We don't. Both platforms handle donations. Only one keeps its hands off your money. Tipeeestream has been around for years and it works. But they charge commissions on your donations and monthly fees for premium features. ZeroCut offers a lifetime Basic tier and never takes a platform cut from donations. If you're streaming in Europe, Tipeeestream's multi-currency support is solid, but ZeroCut handles that too through Stripe. ## Feature comparison | Feature | ZeroCut | Tipeeestream | | --- | --- | --- | | Platform Fee | 0% | Commission-based | | Pricing Model | From $20 lifetime | Monthly plans | | Donation Alerts | Yes | Yes | | Text-to-Speech | Yes | Yes | | Custom Domains | Yes | No | | Discord Integration | Yes | Limited | | Multi-currency | Yes | Yes | | API & Webhooks | Yes | Limited | | PayPal Support | Yes | Yes | ## Pricing model - **Tipeeestream: Monthly + commission.** Pay a monthly subscription AND a percentage of each donation you receive. - **ZeroCut: From $20 one-time.** Basic is one payment. ZeroCut takes no commission from donations; processing fees still apply. Prices and competitor details can change. Verify current pricing and capabilities with each provider. ## Where ZeroCut differs 1. **Zero commissions, period.** Tipeeestream takes a percentage of your donations on top of monthly fees. ZeroCut takes nothing — ever. 2. **A lifetime Basic option.** Basic has no monthly renewal. Premium remains optional for extra tools. 3. **Modern developer tools.** Full API access, webhook notifications, and Discord integration that actually works. Build on top of your donation platform. ## Honest fit ### Use Tipeeestream when - You're already set up on Tipeeestream and the commission rate is low enough for you - You need specific European payment methods they support - You prefer their alert design and customization style ### Use ZeroCut when - You're tired of commissions eating into every donation - You want a lifetime Basic option with no required monthly renewal - You need an API and webhooks for custom integrations ## Learn more - [ZeroCut features](https://zerocut.gg/docs/features.md) - [ZeroCut pricing and product overview](https://zerocut.gg/index.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # ZeroCut vs Ko-fi — Built for Live Streaming, Not Storefronts > Compare ZeroCut and Ko-fi. Both let you accept donations with 0% fees, but ZeroCut is built for streamers with live alerts, OBS integration, and Discord support. - Canonical page: https://zerocut.gg/compare/ko-fi - Markdown version: https://zerocut.gg/compare/ko-fi.md ## Ko-fi wants to be your storefront. We just want to get you paid. Tip jars don't need to be this complicated. Ko-fi started as a tipping platform and grew into memberships, shops, and commissions. If you want an all-in-one creator store, Ko-fi handles that. If you want a fast donation page with live streaming alerts, OBS browser sources, and a Discord bot that manages your community — that's where ZeroCut lives. ## Feature comparison | Feature | ZeroCut | Ko-fi | | --- | --- | --- | | Platform Fee | 0% | 0% tips, 5% shops | | Pricing Model | From $20 lifetime | Free + $6/mo Gold | | Live Stream Alerts | Yes | No | | OBS Integration | Yes | No | | Custom Domains | Yes | Gold only | | Discord Integration | Yes | Limited | | Memberships | No | Yes | | Digital Shop | No | Yes | | Commissions | No | Yes | ## Pricing model - **Ko-fi: Free + $6/month Gold.** Basic donations are free. Gold unlocks custom domains and removes branding. Shops take 5%. - **ZeroCut: From $20 one-time.** Basic includes a donation page and basic stream alerts. Premium starts at $50 for three months, then the current $5.99/month rate. Prices and competitor details can change. Verify current pricing and capabilities with each provider. ## Where ZeroCut differs 1. **Built for live streaming.** OBS browser sources, custom donation alerts, real-time event feed. Ko-fi wasn't built for this — ZeroCut was. 2. **A clear Basic tier.** Basic covers the donation page and basic alerts for life. Premium adds customization, integrations, and analytics. 3. **Discord that actually integrates.** Automatic role assignment for donors, live notifications in your server, and a bot that manages it all. Not just a webhook. ## Honest fit ### Use Ko-fi when - You sell digital products and need a shop alongside donations - You want to offer memberships and recurring support tiers - You don't stream live and just need a simple tip page ### Use ZeroCut when - You stream live and need OBS alerts and browser sources - Your Discord community is central to your brand - You want a clean donation experience without the storefront stuff ## Learn more - [ZeroCut features](https://zerocut.gg/docs/features.md) - [ZeroCut pricing and product overview](https://zerocut.gg/index.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # ZeroCut vs Buy Me a Coffee — 0% Fees vs 5% on Everything > Buy Me a Coffee takes 5% of every transaction. ZeroCut takes 0%. On $1,000 in donations, that's $50 you keep. Compare the two platforms. - Canonical page: https://zerocut.gg/compare/buymeacoffee - Markdown version: https://zerocut.gg/compare/buymeacoffee.md ## Buy Me a Coffee takes 5%. We take 0%. Math that works out in your favor for once. Millions of creators use Buy Me a Coffee, but its 5% fee adds up. On $1,000 in donations, that is $50, the same as ZeroCut's three-month Premium start. BMAC also lacks live-stream alerts and OBS integration. It tells you who bought coffee. ZeroCut shows which stream brought visitors, which visitors donated, and which visitors left without paying. For donation-focused creators, the three numbers tell the story. ## Feature comparison | Feature | ZeroCut | Buy Me a Coffee | | --- | --- | --- | | Platform Fee | 0% | 5% | | Pricing Model | From $20 lifetime | Free (5% cut) | | Live Stream Alerts | Yes | No | | OBS Integration | Yes | No | | Custom Domains | Yes | No | | Discord Integration | Yes | Limited | | API & Webhooks | Yes | Yes | | Memberships | No | Yes | | Extras (digital products) | No | Yes | ## Pricing model - **Buy Me a Coffee: Free (5% fee).** No upfront cost, but 5% of every donation goes to BMAC. On $1,000 that's $50 lost. - **ZeroCut: From $20 one-time.** Basic is one payment. Every donation goes to you minus standard payment processing fees. Prices and competitor details can change. Verify current pricing and capabilities with each provider. ## Where ZeroCut differs 1. **$0 taken from your donations.** BMAC takes 5% of everything. On $1,000 in donations, that's $50, the same as ZeroCut's three-month Premium start. 2. **Live streaming tools included.** Donation alerts, OBS browser sources, real-time feed. BMAC is built for static pages, not live streams. 3. **See the 90% who almost donated.** BMAC shows you the coffees you sold. ZeroCut shows you the whole funnel — every visitor who opened your page, every one who didn't donate, and exactly which stream or link brought them in. The people who almost supported you are the fastest growth lever you have, and nobody else surfaces them. ## Honest fit ### Use Buy Me a Coffee when - You sell digital products (extras) and need that built in - You want memberships and recurring supporter tiers - You don't mind the 5% and prefer their brand recognition ### Use ZeroCut when - You'd rather keep that 5% (it adds up faster than you think) - You stream live and need real-time alerts in OBS - You want to know which stream earned the money — and who walked away without paying ## Learn more - [ZeroCut features](https://zerocut.gg/docs/features.md) - [ZeroCut pricing and product overview](https://zerocut.gg/index.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # ZeroCut vs TikTok Gifts — 0% Platform Fees vs 30-50% > TikTok takes 30-50% of every gift your fans send. ZeroCut takes 0%. Compare the two and see how much you're really losing. - Canonical page: https://zerocut.gg/compare/tiktok - Markdown version: https://zerocut.gg/compare/tiktok.md ## TikTok keeps up to 50% of your gifts. We keep 0%. Your fans think they're supporting you. Half their money never reaches you. TikTok Gifts are built into the app, which means your audience doesn't need to leave TikTok to support you. That's convenient. But TikTok takes 30-50% of every gift before you see a cent, and you can't withdraw until you hit a minimum threshold. ZeroCut lets you link your donation page in your bio — your fans tap once, and the money goes straight to your Stripe or PayPal. You keep everything. ## Feature comparison | Feature | ZeroCut | TikTok Gifts | | --- | --- | --- | | Platform Fee | 0% | 30-50% | | Pricing Model | From $20 lifetime | Built into TikTok | | Payout Speed | Instant (Stripe/PayPal) | 15-30 days | | Minimum Withdrawal | No minimum | $100 minimum | | Custom Branding | Yes | No | | Custom Domain | Yes | No | | OBS Stream Alerts | Yes | No | | Discord Integration | Yes | No | | Works Outside TikTok | Yes | No | | API & Webhooks | Yes | No | ## Pricing model - **TikTok Gifts: 30-50% of every gift.** TikTok converts gifts to Diamonds, then Diamonds to cash. The exchange rate loses you 30-50% every step of the way. - **ZeroCut: From $20 one-time.** Basic is one payment. Your fans donate directly, and ZeroCut adds $0 on top of standard payment processing. Prices and competitor details can change. Verify current pricing and capabilities with each provider. ## Where ZeroCut differs 1. **ZeroCut takes $0.** TikTok takes 30-50% of gifts. On $100 in gifts, you might see $50-70. With ZeroCut, you keep ~$97 (only Stripe/PayPal processing). 2. **No withdrawal minimum.** TikTok won't let you cash out until you hit $100 in Diamonds. ZeroCut has no minimums — withdraw $1 or $1,000 whenever you want. 3. **Works everywhere, not just TikTok.** One donation link for your TikTok bio, YouTube description, Twitch panels, Twitter, Discord — everywhere your audience is. ## Honest fit ### Use TikTok Gifts when - Your audience only engages within the TikTok app - You want the convenience of built-in tipping without external links - You're OK losing 30-50% for the ease of in-app gifts ### Use ZeroCut when - You'd rather keep $97 out of $100 than $50-70 - You have a presence on multiple platforms beyond TikTok - You want to get paid instantly instead of waiting 15-30 days ## Learn more - [ZeroCut features](https://zerocut.gg/docs/features.md) - [ZeroCut pricing and product overview](https://zerocut.gg/index.md) - [Create an account](https://zerocut.gg/sign-in.md) --- # ZeroCut Changelog > Product updates and improvements shipped to ZeroCut. - Canonical page: https://zerocut.gg/changelog - Markdown version: https://zerocut.gg/changelog.md ## Updates - [🎁 Add perks people can buy on your page](https://zerocut.gg/changelog/perks.md) — 2026-08-03: Set a price for the things you already do for supporters, like a shoutout or a Discord role. They pick one off your page instead of guessing at an amount. - [📊 Your analytics numbers just got more accurate](https://zerocut.gg/changelog/page-analytics-overhaul.md) — 2026-04-12: Today's visits are now included in the headline numbers, and switching between date ranges is noticeably faster. - [📈 Traffic on your custom domain is now counted properly](https://zerocut.gg/changelog/custom-domain-tracking.md) — 2026-03-08: If your page runs on your own domain, adblockers were hiding a chunk of your visits from your stats. We fixed that. - [🌐 Put your page on your own domain](https://zerocut.gg/changelog/custom-domains.md) — 2026-03-02: You can now run your ZeroCut page from your own domain — something like tips.yourname.com instead of zerocut.gg/yourname. --- # Add perks people can buy on your page — ZeroCut Changelog > Set a price for the things you already do for supporters, like a shoutout or a Discord role. They pick one off your page instead of guessing at an amount. - Canonical page: https://zerocut.gg/changelog/perks - Markdown version: https://zerocut.gg/changelog/perks.md - Published: 2026-08-03 - Category: Product update ## What changed Set a price for the things you already do for supporters, like a shoutout or a Discord role. They pick one off your page instead of guessing at an amount. ## Set up your first perk A title and a price is all it takes to put one on your page. - [Open donation settings](https://zerocut.gg/app/dashboard/settings/donations) [Browse every update](https://zerocut.gg/changelog.md) --- # Your analytics numbers just got more accurate — ZeroCut Changelog > Today's visits are now included in the headline numbers, and switching between date ranges is noticeably faster. - Canonical page: https://zerocut.gg/changelog/page-analytics-overhaul - Markdown version: https://zerocut.gg/changelog/page-analytics-overhaul.md - Published: 2026-04-12 - Category: Product update ## What changed Headline analytics now include today's visits, so the totals reflect activity up to the current minute instead of stopping at yesterday. Date-range changes also reuse same-day results more effectively, making repeat views and switches between common periods noticeably faster. The update removes the brief number shift that could happen after loading and keeps the server-rendered dashboard consistent with the hydrated data. ## Take a look at your page stats See who's visiting your page and where they're coming from. - [Open analytics](https://zerocut.gg/app/dashboard/page-analytics) [Browse every update](https://zerocut.gg/changelog.md) --- # Traffic on your custom domain is now counted properly — ZeroCut Changelog > If your page runs on your own domain, adblockers were hiding a chunk of your visits from your stats. We fixed that. - Canonical page: https://zerocut.gg/changelog/custom-domain-tracking - Markdown version: https://zerocut.gg/changelog/custom-domain-tracking.md - Published: 2026-03-08 - Category: Product update ## What changed Traffic analytics for donation pages on custom domains now use ZeroCut's first-party relay instead of relying on the standard analytics hostname. Browsers and content blockers were filtering some of those requests, which caused custom-domain visitor totals to be undercounted. The change requires no action from creators and makes the dashboard's visitor numbers more representative of real page traffic. ## See your traffic Open your dashboard to see how supporters are finding your page. - [Go to dashboard](https://zerocut.gg/app/dashboard) [Browse every update](https://zerocut.gg/changelog.md) --- # Put your page on your own domain — ZeroCut Changelog > You can now run your ZeroCut page from your own domain — something like tips.yourname.com instead of zerocut.gg/yourname. - Canonical page: https://zerocut.gg/changelog/custom-domains - Markdown version: https://zerocut.gg/changelog/custom-domains.md - Published: 2026-03-02 - Category: Product update ## What changed Creators can connect a domain they control, such as tips.example.com, and serve their ZeroCut donation page from it. Setup uses either a supported one-click Domain Connect flow or the DNS records shown in settings. ZeroCut provisions and renews HTTPS certificates automatically. The original zerocut.gg/{handle} address continues to work, and the custom-domain add-on remains subject to the plan and billing terms shown in the dashboard. ## Move your page to your own domain A couple of minutes to set up. We handle the technical stuff. - [Open settings](https://zerocut.gg/app/dashboard/settings) [Browse every update](https://zerocut.gg/changelog.md) --- # Analytics > Track donations, revenue, and supporters - Canonical page: https://zerocut.gg/docs/analytics - Markdown version: https://zerocut.gg/docs/analytics.md ## Dashboard overview [#dashboard-overview] * **Total raised** shows your donation revenue. * **Recent activity** lists new donations and followers. * **Top donors** ranks supporters by total donated. ## Charts and exports [#charts-and-exports] Charts show revenue over time and average donation size. Export your donation history as CSV from **Settings > Billing**. Stripe and PayPal also provide transaction exports. --- # Custom Domains > Point your own domain to your ZeroCut donation page - Canonical page: https://zerocut.gg/docs/custom-domains - Markdown version: https://zerocut.gg/docs/custom-domains.md Custom domains let you serve your ZeroCut donation page from your own domain — like `donate.yourdomain.com` instead of `zerocut.gg/yourhandle`. It looks more professional and builds trust with your audience. ## Recommended Setup [#recommended-setup] We recommend buying your domain from **[Cloudflare Registrar](https://www.cloudflare.com/products/registrar/)** or **[Namecheap](https://www.namecheap.com/)**, and managing your DNS through **Cloudflare**. Why Cloudflare? * **Free SSL/TLS** — your custom domain is automatically secured * **DDoS protection** — built-in protection at no extra cost * **Domain Connect support** — Cloudflare supports the [Domain Connect](https://www.domainconnect.org/) protocol, which means ZeroCut can automatically configure your DNS records for you. No manual CNAME setup needed. * **Tight integration with ZeroCut** — we use Cloudflare internally, so your domain is served from the same network with minimal latency If you buy from Namecheap (or another registrar), you can still point your nameservers to Cloudflare for free to get all of these benefits. Cloudflare has a [guide on how to do this](https://developers.cloudflare.com/dns/zone-setups/full-setup/setup/). ## Adding a Custom Domain [#adding-a-custom-domain] 1. Go to **Settings** in your dashboard 2. Open the **Custom Domain** section 3. Enter your domain (e.g. `donate.yourdomain.com`) 4. If your DNS is managed by a provider that supports **Domain Connect** (like Cloudflare or GoDaddy), the CNAME record will be configured automatically — you don't need to do anything else 5. Otherwise, add a CNAME record in your DNS provider pointing to `cname.zerocut.gg` After adding the domain, ZeroCut will automatically provision an SSL certificate. Verification usually takes a few minutes but can take up to an hour depending on DNS propagation. ## Features [#features] Once your custom domain is verified, you can: * **Auto-Redirect** — automatically redirect visitors from your `zerocut.gg` page to your custom domain. You can bypass the redirect by appending `?noredirect` to your zerocut.gg URL. * **Enable/Disable** — temporarily disable your custom domain page without removing it. ## Pricing [#pricing] * **Premium members**: $1/mo add-on * Custom domain access is also included for qualifying users — check your dashboard for details ## Troubleshooting [#troubleshooting] * **Domain stuck on "Pending"**: Make sure your CNAME record is correctly pointing to `cname.zerocut.gg`. You can click "Re-verify" in your settings to trigger a fresh check. * **SSL not working**: SSL certificates are auto-provisioned. Give it up to an hour after DNS verification. If it's still not working, try re-verifying. * **Domain Connect didn't work**: Some DNS providers advertise Domain Connect support but have it partially implemented. In that case, fall back to manually adding the CNAME record. --- # Discord Integration > Connect your Discord server to engage with your community - Canonical page: https://zerocut.gg/docs/discord - Markdown version: https://zerocut.gg/docs/discord.md Discord integration requires Premium Access. After your 7-day free trial ends, upgrade to Premium to unlock this feature. Connect your Discord server to automatically engage with your community when donations come in. The Discord integration provides powerful automation features that help you recognize and reward your supporters. ## Features [#features] ### Donation Announcements [#donation-announcements] Automatically send a message to a specific channel in your Discord server whenever you receive a donation. You can customize the announcement text to match your server's style and include details like the donor's name, amount, and message. ### Role Management [#role-management] Automatically assign roles to donors based on their total donation amount. Set up role tiers (e.g., give a "Supporter" role to anyone who donates $5+, or a "VIP" role for $50+ donors) to recognize your most generous supporters. ### Top Donors Leaderboard [#top-donors-leaderboard] Display a live leaderboard of your top donors directly in your Discord server. The leaderboard automatically updates as new donations come in, keeping your community engaged and encouraging friendly competition. ### Donation Goals [#donation-goals] Set donation goals and track progress in your Discord server. When goals are reached, automatically announce milestones to keep your community informed and motivated. ## Setting Up Discord Integration [#setting-up-discord-integration] 1. Go to **Settings > Integrations**. 2. Click **Connect Discord Server**. 3. Select the Discord server you want to connect. 4. Authorize the zerocut.gg bot to join your server. 5. Configure your announcement channel, role tiers, and leaderboard settings. 6. Save and start receiving donation notifications in Discord! --- # Donation Page > Customize how your public donation page looks and reads - Canonical page: https://zerocut.gg/docs/donation-page - Markdown version: https://zerocut.gg/docs/donation-page.md Your public page is where supporters land to donate. Open the **Page Editor** from **Settings > Customize Page** — it shows a live preview that updates as you type, at phone, tablet, and desktop widths. ## Bio [#bio] Add a short line of text that appears above your goal, introducing yourself or your page (for example, "Variety streamer, six nights a week. Chat picks the game."). * Available to every creator — it is page content, not a premium styling control. * Plain text, up to 80 characters, so it stays to about two lines at any width. * Leave it empty and the line simply doesn't render. Set it under **Branding** in the Page Editor. ## Layout [#layout] Choose how the page arranges itself on wide screens under **Layout**: * **Adaptive** (default) — splits into two columns when there's enough beside the form to fill the second column, and stays single-column otherwise. * **Single column** — always stacks everything in one column, like a phone. * **Split** — always uses the two-column layout. The split layout needs a **goal and at least one perk** to have something to place beside the donation form — with only one of them, a two-column page would leave a mostly-empty column, so Adaptive and Split stay single-column until both are present. Phones always use a single column, so every supporter sees the same reading order regardless of your setting. The rest of the page — theme, colors, avatar, watermark — is configured in the same editor. See [Features](/docs/features) for what's included on each access plan. --- # Stream Overlays > How to set up alerts and overlays for your stream - Canonical page: https://zerocut.gg/docs/embeds - Markdown version: https://zerocut.gg/docs/embeds.md Engage your viewers by showing donations and events live on your stream. ZeroCut provides "Browser Source" URLs that you can add to your broadcasting software. ## Setting Up in OBS / Streamlabs [#setting-up-in-obs--streamlabs] 1. Go to your **Dashboard > Settings > Integrations**. 2. Under **Embeds**, enable embeds if they aren't already. 3. Copy the **Embed URL** for the widget you want (e.g., Donation Alert). 4. Open OBS / Streamlabs. 5. Add a new Source and select **Browser**. 6. Paste the HTTPS Embed URL into the **URL** field. 7. Set the Width and Height (recommended: 800x600 for alerts). 8. Click **OK**. ## Available Widgets [#available-widgets] ### Donation Alert [#donation-alert] Displays a popup notification when someone donates. This is our most feature-rich widget. #### Customization Options [#customization-options] * **Variants**: Choose from 5 distinct styles: * **Simple**: Clean and minimal. * **GIF**: Displays a GIF for your alert. Premium users can upload a custom alert GIF or paste an HTTPS GIF URL. * **Banner**: A sleek, wide banner style. * **Party**: Festive confetti animation. * **Diamond**: A premium, diamond-themed look. * **Message**: Customize the text template (e.g., "New Donation!"). * **Custom GIF**: Premium users can upload a GIF or paste any HTTPS GIF URL (external links may be reviewed). * **Sound**: Upload your own custom MP3 or use our default sound. #### Text-to-Speech (TTS) [#text-to-speech-tts] Enable TTS to have donation messages read aloud on your stream. * **Minimum Amount**: Set a minimum donation amount (e.g., $5) required to trigger TTS, preventing spam from small donations. #### Profanity Filter [#profanity-filter] A profanity filter covers alert messages and text-to-speech. * **Actions**: Choose what happens when profanity is detected: * **Censor**: Replaces bad words with asterisks (e.g., `****`). TTS will skip reading the censored words. * **Hide Message**: Completely hides the message from the alert and skips TTS reading entirely (only the amount is announced). * **Custom Blocklist**: Add specific words you want to block that aren't in our default list. * **Allowlist**: View the default blocklist and uncheck specific words to allow them if you don't find them offensive. ### Follower Alert [#follower-alert] Get notified when you get a new follower. * **Variants**: Same styles as donation alerts (Simple, GIF, Banner, Party, Diamond). * **Sound**: Upload a custom sound for new followers. * **GIF**: The GIF style uses the same Alert GIF configured under Donation Alert. ### Goal Bar [#goal-bar] Shows live donation totals, a progress bar, and a completion percentage. 1. Create a goal in **Settings > Donations** and keep it active. 2. Open **Settings > Integrations > Embeds > Donations**. 3. Under **Donation goal overlay**, enable visibility for the goals you want to show. 4. Choose **Compact bar** or **Card**, then copy the **Goal Browser Source URL** into OBS. The overlay shows up to three goals, newest first. The compact layout puts the percentage above the bar and the amount raised below it. At completion, it shows **Goal reached**; the bar stays at 100% while the amount raised can continue increasing. Start with a 600 × 176 browser source for one compact bar, or use the dimensions shown in settings for multiple goals. The surrounding canvas is transparent. With no active goals enabled for the overlay, the source stays blank. Layout choices apply to the copied URL. Paste the updated URL into OBS when switching layouts. Existing goal URLs keep the card layout. ### Recent Events [#recent-events] A scrolling list of recent donations and follows. * **Profanity Filter**: This widget also respects your profanity filter settings, ensuring that any listed donations are censored or hidden according to your preferences. ## TikTok Live Studio [#tiktok-live-studio] The process is similar for TikTok Live Studio: 1. Click **Add Component** > **Browser Source**. 2. Paste your ZeroCut Embed URL. 3. Adjust the size and position on your canvas. --- # Features > Compare ZeroCut features and access plans - Canonical page: https://zerocut.gg/docs/features - Markdown version: https://zerocut.gg/docs/features.md ## Donation page [#donation-page] Create a public page with Stripe and PayPal payments, themes, donation goals, and perks. See [Donation page](/docs/donation-page). ## Analytics [#analytics] Track revenue, recent activity, top donors, and goals. See [Analytics](/docs/analytics). ## Stream overlays [#stream-overlays] Add donation alerts, goal bars, and recent events to OBS, Streamlabs, or TikTok Live Studio. See [Stream overlays](/docs/embeds). ## Access plans [#access-plans] After your 7-day free trial (which starts automatically when you receive your first donation), you'll need to purchase access to continue using zerocut.gg. ### Basic access [#basic-access] Basic Access includes: * Donation page and payment connections * Donation analytics and goals * Stream overlays ### Premium access [#premium-access] Premium Access adds: * Custom domains as a $1 monthly add-on * Branding removal and more themes * Discord integration * Webhooks --- # Feedback & Roadmap > How the public roadmap works. Submit ideas, upvote what matters, watch them ship. - Canonical page: https://zerocut.gg/docs/feedback - Markdown version: https://zerocut.gg/docs/feedback.md ZeroCut ships in public. Every bug fix and feature starts life as a post on [/feedback](/feedback). If the thing you want is already there, upvote it. If it isn't, post it. I read every submission myself. ## What you can do [#what-you-can-do] Anyone can read the roadmap without signing in. You need an account to submit or upvote. * Browse sorted by Top (most upvoted) or New. * Filter by Bug, Feature, Improvement, Question, or Other. * Upvote anything that affects you. Votes tell me what to build next. * Submit a post when the thing you need isn't already listed. ## Submitting [#submitting] Three ways to open the submit dialog — pick whichever is closer: 1. The Submit button at the top of `/feedback`. 2. "Submit feedback" in the user dropdown (top-right avatar). 3. `/feedback/new` if you like direct URLs. You need three things: * **Category.** Closest match is fine. I'll re-categorize on review if needed, so don't overthink it. * **Title.** One line. * **Details.** For bugs: what you did, what you expected, what happened. For features: who it helps and why now. ## Lifecycle [#lifecycle] Posts move through statuses. Public statuses show on the roadmap. The others don't. | Status | Meaning | Public? | | --------------- | ----------------------------------------- | ------------------------- | | **Pending** | Just submitted. Waiting for review. | Only to author + admin | | **Open** | Approved and live. Vote away. | Yes | | **Planned** | On the short list. | Yes | | **In progress** | I'm actively building it. | Yes | | **Shipped** | Done. Links to the changelog entry. | Yes | | **Rejected** | Not shipping this. You'll get the reason. | No | | **Duplicate** | Merged into an existing thread. | No. Redirected to target. | I try to review within 72 hours. If yours sits longer, poke me at [contact@zerocut.gg](mailto:contact@zerocut.gg). ## Duplicates [#duplicates] If your post matches one already on the board, I merge yours into the existing thread. Your upvote carries over automatically, and you get an email with a link to the combined thread. If I got it wrong, reply to that email and I'll unmerge it. ## Admin replies [#admin-replies] Sometimes I need to ask a follow-up before I can act on a post. You'll get an email from me and can reply to it directly — I'm not hiding behind a ticket queue. Keep the conversation going by email as long as you want. ## Notifications [#notifications] You don't get notified when a post you care about changes state yet. That's on the roadmap. Ironic, I know. For now, bookmark the post or check back. Shipped items link to the [changelog](/changelog). ## FAQ [#faq] **Can I edit a post after submitting?** Not yet. If you made a typo or want to add detail, post a follow-up and I'll merge them. **Does voting cost me anything?** No. One account, one vote per post. Toggle it off to undo. **Will you always ship the top-voted item?** No. Votes tell me what's wanted, but some things ship in a specific order. I'll explain when I skip the top. **What about private feedback?** Email [contact@zerocut.gg](mailto:contact@zerocut.gg). Billing questions, security reports, or anything you don't want on the public board stays off it. --- # Getting Started > Set up your ZeroCut account and start accepting donations - Canonical page: https://zerocut.gg/docs/getting-started - Markdown version: https://zerocut.gg/docs/getting-started.md ## 1. Create your account [#1-create-your-account] Sign in with Google or Discord, then choose the handle used in your public URL. ## 2. Connect payments [#2-connect-payments] 1. Go to **Settings > Billing**. 2. Click **Connect Stripe** or **Connect PayPal**. 3. Follow the prompts to link your account. Stripe and PayPal send funds directly to your account. ZeroCut does not hold them. ## 3. Customize your page [#3-customize-your-page] 1. Go to **Page Editor**. 2. Choose a theme, avatar, and background. 3. Set the default donation amount and message. 4. Check the live preview. ## 4. Share your page [#4-share-your-page] Copy your donation link from the dashboard. Add it to your stream profile, social bio, or Discord server. ## Trial and access [#trial-and-access] Your seven-day trial starts with your first donation. See [Access plans](/docs/features#access-plans) for what happens after the trial. --- # Introduction > Welcome to the ZeroCut documentation - Canonical page: https://zerocut.gg/docs - Markdown version: https://zerocut.gg/docs.md ZeroCut creates donation pages for creators and takes no platform fee. Stripe or PayPal still charges its payment-processing fee. ## Start here [#start-here] 1. [Create your account and connect payments](/docs/getting-started). 2. [Customize your donation page](/docs/donation-page). 3. [Add alerts to your stream](/docs/embeds). 4. Share your donation link. Your seven-day trial starts with your first donation. See [Access plans](/docs/features#access-plans) for plan details. ## Help [#help] Email [contact@zerocut.gg](mailto:contact@zerocut.gg) if the docs do not answer your question. --- # Integrations > Connect payment providers, Discord, and webhooks - Canonical page: https://zerocut.gg/docs/integrations - Markdown version: https://zerocut.gg/docs/integrations.md ## Payment providers [#payment-providers] ### Stripe [#stripe] Accept cards, Apple Pay, and Google Pay. Stripe sends payouts to your bank account and charges its standard processing fees. ### PayPal [#paypal] Accept PayPal payments directly into your PayPal balance. ## Discord [#discord] Connect Discord for donation alerts, donor roles, and leaderboards. See the [Discord setup guide](/docs/discord). Requires [Premium Access](/docs/features#access-plans). ## Webhooks [#webhooks] Send signed donation events to your own endpoint. See the [webhooks guide](/docs/webhooks). --- # Page Analytics > Visitor tracking for your handle page (premium feature) - Canonical page: https://zerocut.gg/docs/page-analytics - Markdown version: https://zerocut.gg/docs/page-analytics.md Page Analytics tracks visits to your handle page. It requires [Premium Access](/docs/features#access-plans). ## What you can see [#what-you-can-see] The Page Analytics dashboard shows: * Visitors, visits, pageviews, bounce rate, and average visit duration * Realtime visitors * Traffic sources and referrers * Countries and regions * Devices and browsers * Donation conversions and payment methods ## How to access it [#how-to-access-it] Open **Dashboard > Page Analytics**. The main dashboard chart can also show or hide a **Page Visitors** line alongside donations, followers, and live hours. ## Accuracy [#accuracy] Visitor analytics are estimates: * Ad blockers may prevent a visit from being counted. * VPNs, mobile carriers, and corporate networks can make locations inaccurate. * A blocked analytics request does not stop the visitor from using your page or donating. Use visitor counts to compare trends, not as a billing record. Donation records come from the payment flow and remain exact when visitor tracking is blocked. ## Data freshness [#data-freshness] Dashboard data is cached for one hour. Use the refresh button to request current data. Realtime visitors refresh every 30 seconds and may be cached for up to 60 seconds. --- # Perks > Offer fixed-price rewards donors can pick on your donation page - Canonical page: https://zerocut.gg/docs/perks - Markdown version: https://zerocut.gg/docs/perks.md ## Creating a perk [#creating-a-perk] 1. Go to **Settings > Donations**. 2. Add a perk in the **Perks** section. 3. Set its label, price, currency, and maximum quantity. 4. Add a Discord role or webhook action if needed. 5. Save it. Active perks appear under **Pick a perk** on your donation page. Archive a perk to hide it without losing its donation history. Payment minimums apply to the whole cart. A $1 repeatable perk can meet a $5 minimum when the donor buys five. ## Quantities and combinations [#quantities-and-combinations] A maximum quantity above 1 adds quantity controls to the donation page. Checkout enforces the limit. Choose how different perks can share one cart: * **One perk at a time** limits the cart to one kind of perk. * **Any combination** allows active perks in the same currency. * **Selected combinations** allows only the pairs you enable. Discord-role perks stay limited to one per donation. Perks in different currencies cannot share a cart. ## Perk actions [#perk-actions] Actions run after payment: * **Discord role** emails the donor a one-time link to claim a role in your server. * **Webhook** sends a signed request containing `incentiveId` and `incentiveTitle`. Match rules still apply. A failed match records a **Skipped** outcome under **Recent Donations**. Webhooks with required donor input cannot run as perk actions. See [One webhook, many perks](/docs/webhooks#one-webhook-many-perks) for routing several perks through one endpoint. Discord-role perks require the [Discord integration](/docs/discord). Refunding or reversing the donation revokes the role. ## Claiming a Discord role [#claiming-a-discord-role] When a donor buys a Discord-role perk: 1. They receive a **claim link by email** after payment. 2. They connect their Discord account. 3. ZeroCut grants the role. The link is single-use and expires after seven days. Donors can request another email from their receipt. --- # SEO & Sharing > Control how your donation page appears on Google and social platforms - Canonical page: https://zerocut.gg/docs/seo - Markdown version: https://zerocut.gg/docs/seo.md ZeroCut gives you control over how your donation page appears across the web — from Google search results to link previews on Discord, Twitter, and iMessage. ## Sitemap [#sitemap] When you enable **Show on Sitemap**, your page gets added to our `sitemap.xml` file. This is the file that Google and other search engines read to discover pages on a website. Once listed, Google will eventually crawl and index your page, making it show up in search results for your name or handle. ### Things to know [#things-to-know] * **It takes time.** Google doesn't crawl instantly — it can take days to weeks for your page to appear in search results after enabling this. * **Disabling doesn't remove you immediately.** If you turn this off, your page is removed from the sitemap right away, but Google may keep showing cached results for a while. If you need a faster removal, contact us at [contact@zerocut.gg](mailto:contact@zerocut.gg) and we can manually request removal on your behalf. * **Your page must be public.** If you've disabled your public page, it won't appear in search results regardless of this setting. ## Metadata Image [#metadata-image] The **metadata image** (also called an OG image) is the preview image that shows up when someone shares your link on platforms like Discord, Twitter/X, iMessage, Slack, and others. You can choose between a **light** or **dark** color scheme for this image. The image is generated automatically using your page's current theme colors. Use the **Preview** button in the editor to see exactly how your link will look when shared on different platforms. ## Favicon [#favicon] Enabling **Profile Picture as Favicon** replaces the default ZeroCut icon in browser tabs with your profile picture. This gives your page a more personal, branded feel when visitors have it open in their browser. --- # Webhooks > Build custom workflows with donation webhooks - Canonical page: https://zerocut.gg/docs/webhooks - Markdown version: https://zerocut.gg/docs/webhooks.md Webhooks require Premium Access. After your 7-day free trial ends, upgrade to Premium to unlock this feature. Webhooks let you collect custom information from a donor and forward it to your own server after a successful donation. This is perfect for building custom integrations, like: * Adding donors to a Minecraft whitelist. * Triggering in-game events. * Updating a custom database. ## How It Works [#how-it-works] Webhooks fire **after a donation is paid and verified**. Once the donor submits your custom fields, ZeroCut confirms the payment (a paid Stripe Checkout Session or a completed PayPal order) and then sends a `POST` request to the URL you configured. The request body is JSON and contains the webhook's identity, the custom fields the donor filled out, the identifier of the verified payment, and the delivery metadata used for signing. The payload does **not** include the donation amount, currency, donor name, or donation message. It carries the custom input fields the donor submitted, the perk the donation bought (if any), and the payment identifier (`provider` and `providerPaymentId`). If you need the amount or payer details, look them up in your own records or via the payment provider using that identifier. ## Custom Input Fields [#custom-input-fields] You can ask donors for specific information when they donate. For example, if you run a Minecraft server, you can add a required field labelled "Minecraft Username". Each field you configure has a **Label** (up to 100 characters), an optional placeholder, and a required toggle. A webhook can have up to 20 fields, and each submitted value can be up to 1000 characters. The donor's answers are sent in the `data` object, keyed by the field label. Keys are sorted alphabetically. ## Match Rules [#match-rules] **Match rules** in the webhook editor decide which donations this webhook goes out for. Every rule is a condition on the donation or the donor: * **Donation** — Donation amount, Currency, Payment provider, Billing country, Donation message, Perk purchase, Perk. * **Donor** — Discord linked, Lifetime giving, Donation count. Conditions inside a rule group are joined with **all** or **any**, and every group has to hold for the delivery to go out. The editor writes the whole thing back to you as a sentence ("Runs only when all of these hold…"), so you can read the rule instead of decoding it. Rules are evaluated on **both** delivery paths — the donor-triggered webhook on your donation page and the same webhook fired as a perk's action. Nothing in the list depends on the donor's form input: every fact comes from the donation record itself, which the perk path holds in full. When a perk-fired delivery doesn't match, no request goes out and the outcome is recorded rather than lost. Expand the donation in **Recent Donations** and its **Perk actions** list shows **Skipped** — "this delivery's match rules didn't match this donation". That is a decision, not a failure: it isn't retried and it doesn't count against the webhook. A perk rule no longer prevents a webhook from being a perk's action. Adding **Perk is …** used to hide the webhook from the perk's action picker; now it stays selectable and the rule is simply evaluated when the perk fires — true when the donation bought that perk, a recorded skip when it bought another. A donation without a perk never matches a **Perk** rule — "is not" included. To target perkless donations, use **Perk purchase** set to "the donation bought no perk". ## Setting Up a Webhook [#setting-up-a-webhook] 1. Go to **Settings > Donations**. 2. Find the **Custom Webhooks** card. 3. Click **Create Webhook**. 4. Enter a **Name**, an optional **Description**, and your **Webhook URL**. 5. Add any **Input Fields** you need (Label, optional Placeholder, and whether it's required). 6. Save. ZeroCut generates a signing secret and shows it to you once — copy it now (see below). ## Payload [#payload] The JSON body has these keys: | Key | Type | Notes | | ------------------- | ----------------- | ------------------------------------------------------------------------------------ | | `webhookId` | string | The webhook's UUID. | | `webhookName` | string | The name you gave the webhook. | | `data` | object of strings | Donor-submitted custom fields, keyed by field label. Keys are sorted alphabetically. | | `incentiveId` | string or null | The perk this donation funded, when one was chosen — `null` otherwise. | | `incentiveTitle` | string or null | The label of that perk — `null` otherwise. | | `incentives` | array, optional | Frozen purchased lines with each perk's ID, title, unit price, quantity, and total. | | `provider` | string | How the donor paid — `"stripe"` or `"paypal"`. | | `providerPaymentId` | string | The Stripe Payment Intent ID, or the PayPal capture ID, for the payment we verified. | | `deliveryId` | string | Stable ID for this delivery. Matches the `X-Zerocut-Delivery-Id` header. | | `timestamp` | string | ISO-8601 time the request was signed. Matches the `X-Zerocut-Timestamp` header. | ```json { "webhookId": "b1a7c3e2-4f5d-6a7b-8c9d-0e1f2a3b4c5d", "webhookName": "Minecraft Server Access", "data": { "Discord ID": "steve#1234", "Minecraft Username": "StevePro123" }, "incentiveId": "9c2f8a41-6d3b-4e15-9a70-2f8b1c4d5e6a", "incentiveTitle": "VIP Discord role", "incentives": [ { "incentiveId": "9c2f8a41-6d3b-4e15-9a70-2f8b1c4d5e6a", "incentiveTitle": "VIP Discord role", "unitAmount": 1000, "currency": "USD", "quantity": 1, "lineTotal": 1000 } ], "provider": "stripe", "providerPaymentId": "pi_3Pa1B2c3D4e5F6g7", "deliveryId": "5f3c1d9e8b7a6c5d4e3f2a1b0c9d8e7f6a5b4c3d2e1f0a9b8c7d6e5f4a3b2c1d", "timestamp": "2026-07-10T10:00:00.000Z" } ``` Deliveries used to identify the payment with `sessionId` (Stripe Checkout Session) or `paypalOrderId` instead. Those keys are gone: they are the same identifiers a donor's browser carries in its return URL, and forwarding them to a third-party endpoint spread them further than they should go. Use `provider` and `providerPaymentId`, which name the payment itself. Deliveries that were queued before the perk keys existed replay without them, so treat a missing `incentiveId` or `incentiveTitle` the same as `null`. The `incentives` array is also omitted for donations recorded before cart snapshots existed. For a combined donation, `incentives` is the authoritative list. The legacy `incentiveId` and `incentiveTitle` fields remain useful for a single-perk donation; they are `null` when a donor-triggered webhook covers several purchased perks. A webhook action attached to one perk still names that action's perk in the legacy fields and includes the full purchased list in `incentives`. Structured request bodies that interpolate `{{donation.incentiveTitle}}` get a joined summary of every purchased line (for example `Shout-out, 50 push-ups ×3`), so a stacked cart does not render as an empty string. `{{donation.incentiveId}}` stays the single-perk identifier and is empty for a combined donation — branch on `incentives` when you need every line. ## One Webhook, Many Perks [#one-webhook-many-perks] You don't need one URL per perk. Attach the **same** webhook as the action on every perk that should reach your server (see [Perks](/docs/perks)), then let the payload tell you which one was bought: `incentiveTitle` is what the donor saw, and `incentiveId` is the stable identifier that survives a rename. Dispatch on it server-side, after you've verified the signature: ```js switch (payload.incentiveId ?? null) { case "9c2f8a41-6d3b-4e15-9a70-2f8b1c4d5e6a": await grantVip(payload); break; case "3e7d05b2-91cc-4a88-b0f1-7d2e6a9c8b40": await queueMerchOrder(payload); break; case null: await thankDonor(payload); // a donation with no perk break; default: // A perk you haven't wired up yet. Log it and return 200 so ZeroCut stops retrying. break; } ``` The perk keys arrive on both delivery paths: * **Perk actions** fire after payment with no donor input, so `data` carries `incentiveId` and `incentiveTitle` too — those entries predate the top-level keys and stay for receivers already reading them. Both name the same perk. * **Donor-triggered webhooks** (the ones with custom input fields on your donation page) fire for any donation and name the perk when the donor picked one, so a single endpoint can serve perk and perkless donations alike. If you'd rather not branch at all, scope the webhook instead: [match rules](#match-rules) include **Perk purchase** (yes/no) and **Perk** (is / is not / is one of, picked from your own perks), so the request only goes out for the donations you care about. They apply to perk-fired deliveries too, which makes the two settings compose predictably: A **Perk** rule evaluates all lines in a combined donation: **is** and **is one of** match when any purchased line matches, while **is not** matches only when none of them do. * A webhook attached to perk X with a **Perk is X** rule always matches when that perk fires — the rule restates the binding. * The same webhook attached to perk Y instead sends nothing and records a **Skipped** outcome on that donation, so you can see the rule turned the delivery away rather than wonder where it went. * A rule on a **Donor** field (say, **Lifetime giving is at least $100**) narrows a perk's deliveries to repeat supporters without touching the perk itself. ### Linking Perks from the Webhook [#linking-perks-from-the-webhook] You can wire the same binding from either end. Open the webhook and its **Used by perks** list shows every perk that currently fires it, with a toggle per perk to link or unlink. Linking is exactly what picking this webhook in a perk's **Action** field does; unlinking removes only this webhook's action from that perk and leaves the perk's other actions — a Discord role, a second webhook — alone. A webhook with a **required** donor input field can't be a perk's action: it shows up in neither the perk's action picker nor **Used by perks**. A perk fires after payment with no form in between, so nothing can collect that required answer. Make the field optional, or use a separate webhook for perks. Match rules never create links on their own. A rule is a condition ("only for these donations"); a link is an action ("this perk fires this webhook"). Adding **Perk is VIP** to a webhook does not attach it to that perk — ZeroCut may point out the mismatch, but you decide. ## Headers [#headers] Every delivery includes these headers: | Header | Value | | ----------------------- | --------------------------------------------------------------- | | `Content-Type` | `application/json` | | `X-Zerocut-Timestamp` | ISO-8601 timestamp (the same value as `timestamp` in the body). | | `X-Zerocut-Delivery-Id` | Stable delivery ID. Use it as an idempotency key. | | `X-Zerocut-Signature` | `v1=`, an HMAC-SHA256 signature (see below). | ## Verifying a Delivery [#verifying-a-delivery] Anyone who knows your URL could `POST` to it. Verify the signature so you only act on requests that genuinely came from ZeroCut. The signature is computed as: ``` v1= + hex( HMAC_SHA256(secret, `${timestamp}.${rawBody}`) ) ``` where `secret` is the signing secret shown when you created (or rotated) the webhook, `timestamp` is the `X-Zerocut-Timestamp` header value, and `rawBody` is the exact request body. To verify, on your server: 1. Read the **raw request bytes** before any JSON parsing or re-serialisation. Re-encoding the body changes the bytes and breaks the signature. 2. Parse the ISO-8601 `X-Zerocut-Timestamp` and reject anything outside a **±5-minute** window of your own clock. This blocks replays. 3. Compute `HMAC_SHA256(secret, timestamp + "." + rawBody)` and hex-encode it, prefixed with `v1=`. 4. Compare it against `X-Zerocut-Signature` using a **timing-safe** comparison with an equal-length guard (for example `crypto.timingSafeEqual`) — never `===`. 5. Treat `X-Zerocut-Delivery-Id` as an **idempotency key**. Deliveries are retried (with exponential backoff, up to 12 attempts), so store the ID and ignore any you have already processed. Retries reuse the **same** `X-Zerocut-Delivery-Id` but generate a **new** `X-Zerocut-Timestamp` and signature each time. Verify the signature on every attempt, and dedupe on the delivery ID — not on the timestamp or the signature. ## Example (Node / Express) [#example-node--express] ```js const express = require("express"); const { createHmac, timingSafeEqual } = require("node:crypto"); const SECRET = process.env.ZEROCUT_WEBHOOK_SECRET; const REPLAY_WINDOW_MS = 5 * 60 * 1000; // Swap this in-memory set for Redis or a database in production so dedupe // survives restarts and works across multiple instances. const seenDeliveries = new Set(); const app = express(); // The raw body is required: parsing then re-serialising JSON changes the bytes // and invalidates the signature. app.post("/webhook", express.raw({ type: "application/json" }), (req, res) => { const timestamp = req.get("X-Zerocut-Timestamp"); const deliveryId = req.get("X-Zerocut-Delivery-Id"); const signature = req.get("X-Zerocut-Signature"); const rawBody = req.body; // Buffer, thanks to express.raw if (!SECRET || !timestamp || !deliveryId || !signature) { return res.sendStatus(400); } // 1. Reject stale or future timestamps (guards against replays). const sentAt = Date.parse(timestamp); if (Number.isNaN(sentAt) || Math.abs(Date.now() - sentAt) > REPLAY_WINDOW_MS) { return res.sendStatus(400); } // 2. Recompute the signature over the raw bytes and compare in constant time. const expected = "v1=" + createHmac("sha256", SECRET).update(`${timestamp}.`).update(rawBody).digest("hex"); const expectedBuf = Buffer.from(expected); const actualBuf = Buffer.from(signature); if (expectedBuf.length !== actualBuf.length || !timingSafeEqual(expectedBuf, actualBuf)) { return res.sendStatus(401); } // 3. Idempotency: deliveries are retried, so ignore ones we've already handled. if (seenDeliveries.has(deliveryId)) { return res.sendStatus(200); } seenDeliveries.add(deliveryId); const payload = JSON.parse(rawBody.toString("utf8")); // payload.data holds the donor's answers, e.g. payload.data["Minecraft Username"]. console.log(`Verified delivery ${deliveryId} for "${payload.webhookName}"`); return res.sendStatus(200); }); app.listen(3000); ``` ## The Signing Secret [#the-signing-secret] * The secret (it looks like `zwhsec_...`) is shown **exactly once**, when you create the webhook or rotate its secret. ZeroCut does not expose it again. * Copy it and store it somewhere safe (an environment variable like `ZEROCUT_WEBHOOK_SECRET`, a secrets manager, etc.). Never commit it or log it. * Rotation stops future and not-yet-started deliveries from using the old secret. An attempt that already crossed ZeroCut's durable send boundary may still arrive—or be retried after an ambiguous timeout/process crash—with the old secret and the same `X-Zerocut-Delivery-Id`. During rotation, accept both the previous and new secret for at least the delivery retry window, deduplicate by delivery ID, then retire the previous secret. New deliveries use only the new secret. * Webhooks created before request signing existed have no secret and are flagged **Not signed** in the dashboard. They are unavailable until you click **Generate signing secret**. ## Delivery Ordering During Changes [#delivery-ordering-during-changes] ZeroCut linearizes each outbound attempt immediately before network I/O: * If deletion, URL/name change, secret rotation, refund, or dispute wins first, that uncommitted attempt is canceled and its encrypted snapshot is destroyed. * If the attempt wins first, it is allowed to finish with its immutable URL, payload, and signing secret even when the configuration or payment changes immediately afterward. * A confirmed non-2xx HTTP response releases that attempt boundary before a retry is scheduled, so a later configuration/payment change can cancel the next attempt. * A network timeout or process death is ambiguous: the receiver may already have accepted the request. ZeroCut preserves the boundary and retries the same delivery ID at least once. This is why receiver-side durable idempotency is required. These rules prevent an owner change from racing a request that has not started while preserving an honest at-least-once contract for requests that may already have crossed the network. --- # Top Activities - Canonical page: https://zerocut.gg/docs/api/analytics-activities - Markdown version: https://zerocut.gg/docs/api/analytics-activities.md Get top stream activities by duration. --- # Daily Analytics - Canonical page: https://zerocut.gg/docs/api/analytics-daily - Markdown version: https://zerocut.gg/docs/api/analytics-daily.md Get day-by-day time series analytics (up to 120 days). --- # Hourly Analytics - Canonical page: https://zerocut.gg/docs/api/analytics-hourly - Markdown version: https://zerocut.gg/docs/api/analytics-hourly.md Get hour-by-hour time series analytics (up to 7 days). --- # Oldest Data - Canonical page: https://zerocut.gg/docs/api/analytics-oldest - Markdown version: https://zerocut.gg/docs/api/analytics-oldest.md Get the timestamp of the oldest data point for the user. --- # Analytics Overview - Canonical page: https://zerocut.gg/docs/api/analytics-overview - Markdown version: https://zerocut.gg/docs/api/analytics-overview.md Get KPI summary: revenue, donations, sessions, live hours. --- # Weekly Analytics - Canonical page: https://zerocut.gg/docs/api/analytics-weekly - Markdown version: https://zerocut.gg/docs/api/analytics-weekly.md Get week-by-week time series analytics (up to 365 days). --- # Donation Breakdown - Canonical page: https://zerocut.gg/docs/api/donation-breakdown - Markdown version: https://zerocut.gg/docs/api/donation-breakdown.md Get donation breakdown by category (named vs anonymous). --- # Daily Donations - Canonical page: https://zerocut.gg/docs/api/donation-daily - Markdown version: https://zerocut.gg/docs/api/donation-daily.md Get daily donation aggregation. --- # Hourly Donations - Canonical page: https://zerocut.gg/docs/api/donation-hourly - Markdown version: https://zerocut.gg/docs/api/donation-hourly.md Get hourly donation aggregation. --- # List Donations - Canonical page: https://zerocut.gg/docs/api/donation-list - Markdown version: https://zerocut.gg/docs/api/donation-list.md Get a paginated list of donations. --- # Donation Stats - Canonical page: https://zerocut.gg/docs/api/donation-stats - Markdown version: https://zerocut.gg/docs/api/donation-stats.md Get donation statistics grouped by currency. --- # Top Countries - Canonical page: https://zerocut.gg/docs/api/donation-top-countries - Markdown version: https://zerocut.gg/docs/api/donation-top-countries.md Get countries ranked by donation volume. --- # Top Donors - Canonical page: https://zerocut.gg/docs/api/donation-top-donors - Markdown version: https://zerocut.gg/docs/api/donation-top-donors.md Get top donors leaderboard. --- # Create Donation - Canonical page: https://zerocut.gg/docs/api/donation - Markdown version: https://zerocut.gg/docs/api/donation.md Record a donation for a creator (server-to-server; amount returned in cents). --- # Event Stream (SSE) > Subscribe to donations, perk purchases, followers, and goal completions over Server-Sent Events. - Canonical page: https://zerocut.gg/docs/api/events-stream - Markdown version: https://zerocut.gg/docs/api/events-stream.md `GET /api/v1/events/stream` pushes your creator events to a long-lived Server-Sent Events connection. It carries business facts only — a donation was recorded, perks were purchased, a follower was recorded, a goal was reached — scoped to the account that owns the API key. This page is written by hand. The stream returns `text/event-stream`, which has no JSON response schema, so it is **not** part of the generated OpenAPI document. Everything you need to write a client is below. The companion endpoint `POST /api/v1/events/stream-token` *is* in the OpenAPI document. ## Authentication [#authentication] Send your API key in the `X-API-Key` header, exactly as with every other endpoint: ```bash curl -N \ -H "X-API-Key: zerocut.your_api_key_here" \ -H "Accept: text/event-stream" \ https://zerocut.gg/api/v1/events/stream ``` API keys are never accepted in the query string. Passing `apiKey`, `api_key`, `apikey`, `key`, or `token` as a query parameter returns `400` with code `QUERY_PARAM_CREDENTIAL`, before the key is even hashed. Browsers that need `EventSource` use the [stream token flow](#eventsource-stream-tokens) instead. The stream requires the same premium API access as the REST endpoints. Access is re-checked every 30 seconds while the connection is open; if the key is disabled, deleted, expires, or the account loses API access, the server sends a terminal `error` frame and closes. ## Event catalog [#event-catalog] | `type` | Meaning | | ------------------ | ------------------------------------ | | `donation.created` | A donation was recorded | | `perks.purchased` | One donation purchased one perk cart | | `follower.created` | A follower was recorded | | `goal.reached` | A donation goal completed | Every type is sent by default. To receive only donations — or any other subset — pass the [`events` filter](#filters), e.g. `?events=donation.created`. Test alerts fired from your dashboard are **not** published — every id on this stream resolves over REST. ## Envelope [#envelope] Each frame's `data:` line is one JSON object: ```json { "id": "1788093001234-0", "family": "domain", "type": "donation.created", "version": 1, "createdAt": "2026-08-30T12:30:01.234Z", "replayed": false, "data": { "id": "0f2d6c1e-9b5a-4c7e-8f1a-3d2b5e7c9a04", "amount": 1500, "currency": "USD", "donorName": "Ada", "message": "great stream", "country": "GB", "perk": { "id": "8b1f...", "title": "Shoutout" }, "perks": [ { "id": "8b1f...", "title": "Shoutout", "quantity": 1, "unitAmount": 1500, "lineTotal": 1500, "currency": "USD" } ], "createdAt": "2026-08-30T12:30:01.180Z" } } ``` * `id` — the resume cursor for this event. Monotonic for your account. * `family` — `domain` for catalog events, `control` for the lifecycle frames below. **Ignore families you do not recognise**; new ones may be added. * `version` — envelope version, currently `1`. * `createdAt` — derived from `id`, so it is identical whether the frame arrived live or as a replay. `data.createdAt` is the authoritative business time. * `replayed` — `true` when the frame came from reconnect replay. Money is always an integer in the currency's minor unit, and `currency` is always uppercase, matching the REST API. ### `donation.created` [#donationcreated] | Field | Type | Notes | | ----------- | ----------------- | ------------------------------------------- | | `id` | string (uuid) | Resolves via `GET /donation/getById?id=...` | | `amount` | integer | Minor units, gross | | `currency` | string | Three letters, uppercase | | `donorName` | string \| null | Creator-visible display name | | `message` | string \| null | Donor message | | `country` | string \| null | ISO-3166 alpha-2 when known | | `perk` | object \| null | `{ id, title }`, the primary perk | | `perks` | array | Cart lines, `[]` when none | | `createdAt` | string (ISO-8601) | Donation creation time | Each `perks[]` entry is `{ id, title, quantity, unitAmount, lineTotal, currency }`. ### `perks.purchased` [#perkspurchased] Sent for each perk-bearing donation, immediately after its `donation.created` event. Both frames have separate monotonic IDs and are appended atomically. Producer retries can publish the pair again with new envelope IDs; use `data.donationId` to prevent duplicate fulfillment. | Field | Type | Notes | | ------------ | ----------------- | ------------------------------------------- | | `donationId` | string (uuid) | Resolves via `GET /donation/getById?id=...` | | `currency` | string | Three letters, uppercase | | `donorName` | string \| null | Creator-visible display name | | `perk` | object \| null | Legacy `{ id, title }` reference | | `perks` | array | Frozen purchased cart lines | | `cartTotal` | integer \| null | Sum of frozen line totals; null for legacy | | `createdAt` | string (ISO-8601) | Donation creation time | The `perks` snapshot does not change when a current catalog perk is renamed, archived, or deleted. Use [`GET /perk/list`](/docs/api/perk-list) to discover current IDs; use the donation endpoints to reconcile historical purchases. ### `follower.created` [#followercreated] | Field | Type | Notes | | ------------- | ----------------- | --------------------------------- | | `id` | string | Follower record id | | `username` | string | Platform handle | | `displayName` | string \| null | Platform display name | | `platform` | string | Platform slug | | `origin` | string | `manual`, `provider`, or `legacy` | | `createdAt` | string (ISO-8601) | Follow time observed by ZeroCut | ### `goal.reached` [#goalreached] | Field | Type | Notes | | ------------- | ----------------- | --------------------------------- | | `goalId` | string | Goal id | | `description` | string \| null | Goal description | | `amount` | integer | Target, minor units | | `totalRaised` | integer | Raised at completion, minor units | | `currency` | string | Three letters, uppercase | | `completedAt` | string (ISO-8601) | Completion time | ## Control frames [#control-frames] Control frames carry `family: "control"` and an `event:` name matching `type`. | `type` | Meaning | | ----------- | ------------------------------------------------------------ | | `connected` | Stream is live. `data.baselineCursor` is the start point. | | `replayed` | Replay finished. `data.count`, `data.endCursor`. | | `ping` | Keepalive every 10s. `data.timestamp` (epoch ms). | | `reconnect` | The server is rotating this connection. Reconnect now. | | `resync` | Your cursor is unusable. `data.reason`. Reconcile over REST. | | `error` | Terminal. `data.code`, `data.message`. A close follows. | `connected` is not guaranteed to be the first frame. When a resume fails, the sequence is `resync` then close, with **no** `connected` and no `baselineCursor` — do not block waiting for `connected`. `error` codes: `keyRevoked`, `keyDisabled`, `keyExpired`, `entitlementLost`, `subscriberUnavailable`, `subscriptionUnavailable`, `streamFailed`. ## Wire framing [#wire-framing] ``` retry: 2000 id: 1788093001234-0 event: donation.created data: {"id":"1788093001234-0","family":"domain","type":"donation.created",...} ``` The `retry:` hint is sent once, before any frame. Domain frames carry `id:` and `event:`; control frames carry `event:` only, except `ping`, which may carry an `id:` checkpoint (see [Filters](#filters)). ## Filters [#filters] Both filters are optional and evaluated on the server. | Parameter | Value | Cap | | --------- | ---------------------------- | --- | | `events` | Comma-separated public types | 8 | | `perkIds` | Comma-separated perk uuids | 10 | ``` /api/v1/events/stream?events=donation.created&perkIds=8b1f...,c33a... ``` `perkIds` narrows `donation.created` and `perks.purchased` by their legacy perk or any frozen cart line. It leaves follower and goal events untouched. For a perk-purchase-only stream, use: ``` /api/v1/events/stream?events=perks.purchased&perkIds=8b1f...,c33a... ``` An unknown type is `400` `UNKNOWN_EVENT_TYPE`; an empty or over-cap value is `400` `INVALID_FILTER`. A filtered-out event still moves your cursor forward: the next `ping` carries an `id:` checkpoint so a narrow filter cannot strand you in a window you keep re-scanning. Treat a `ping` with an `id:` exactly like any other id you store. ## Resuming [#resuming] On reconnect, send the last id you processed. In priority order the server reads the `Last-Event-ID` request header, then the `lastEventId` query parameter (browsers only send the header on automatic reconnects). ```bash curl -N \ -H "X-API-Key: zerocut.your_api_key_here" \ -H "Last-Event-ID: 1788093001234-0" \ https://zerocut.gg/api/v1/events/stream ``` Delivery is **at-least-once**. Use the envelope `id` to resume the stream and deduplicate replayed frames. Producer retries can publish the same donation again with new envelope IDs, for example if publication succeeds but recording completion fails. Envelope IDs alone do not prevent duplicate fulfillment. For donation-related actions, persist these business keys in storage scoped to the creator: | Event | Business deduplication key | | ------------------ | -------------------------- | | `donation.created` | `(type, data.id)` | | `perks.purchased` | `(type, data.donationId)` | Use a unique constraint and record the action, or enqueue it in a durable outbox, in the same transaction as the key. Fulfill perks from `perks.purchased` only; handling the same purchase through both event types would duplicate it even with separate per-type keys. One purchase event contains every cart line and its quantity. Roughly the last 256 events per account are retained, trimmed to a 15-minute window. A cursor older than that window, ahead of the stream, or requiring more than 50 replayed events produces a `resync` frame and an immediate close, with `data.reason` one of `cursor-trimmed`, `cursor-ahead`, `replay-over-cap`, `replay-scan-over-cap`, `replay-corrupt`, `live-buffer-overflow`. `replay-corrupt` also means this server cannot interpret an event's protocol version, including during a rolling deployment. Live streams close with the same reason before sending any later event, so they cannot advance your cursor past an unreadable event. A `resync` means there is a gap. Reconcile over `GET /donation/list` (including its frozen `perk` and `perks` fields), `GET /follower/list`, and `GET /goal/list`, then reconnect **without** a resume point. Reconnecting with the same cursor only produces another `resync`. `0-0` is rejected with `400` `INVALID_CURSOR`. To start from live, send no resume point at all. ## EventSource (stream tokens) [#eventsource-stream-tokens] `EventSource` cannot set request headers, so browsers exchange the API key for a short-lived token first. Mint the token from your server, never from a page that would have to embed the API key. ```bash curl -X POST https://zerocut.gg/api/v1/events/stream-token \ -H "X-API-Key: zerocut.your_api_key_here" \ -H "Content-Type: application/json" \ -d '{"events":["donation.created"]}' ``` ```json { "streamToken": "zcst.0123...", "expiresAt": "2026-08-30T12:31:01.234Z", "expiresIn": 60 } ``` The token is single-use and lives 60 seconds. It authorises *opening* a stream, not holding one — once connected, the connection's lifetime is governed by the API key. Send `{}` when you want no filters. A token is spent the moment a connection opens, and connections rotate roughly every 4.5 minutes, so **every** `EventSource` client needs a re-mint loop. The browser's own automatic reconnect replays the spent token, gets a `401`, and — per the SSE specification — closes the connection permanently without retrying again. A snippet without the loop below goes silently dark after the first rotation. ```js let source; let lastEventId = null; async function connect() { const streamToken = await mintStreamToken(); // your server, POST /events/stream-token const url = new URL("/api/v1/events/stream", location.origin); url.searchParams.set("streamToken", streamToken); if (lastEventId) url.searchParams.set("lastEventId", lastEventId); source = new EventSource(url); source.addEventListener("donation.created", (event) => { lastEventId = event.lastEventId; const frame = JSON.parse(event.data); console.log(frame.data.amount, frame.data.currency); }); // Rotation: expected every ~4.5 minutes. Reconnect with a fresh token. source.addEventListener("reconnect", () => { source.close(); void connect(); }); source.addEventListener("resync", () => { source.close(); lastEventId = null; // Refetch over REST, then resume from live. void connect(); }); source.onerror = () => { source.close(); setTimeout(connect, 2000); // Back off; the previous token is already spent. }; } ``` The browser resends `Last-Event-ID` automatically on reconnect, but a stream token is single-use — mint a fresh one for every connect, including after a `reconnect` frame and after any non-200 response. A rejected connect (rate limit, filter error, concurrency cap) also consumes the token, so always re-mint rather than retrying the same URL. Filters bound at mint time win: if the token carries `events` or `perkIds`, repeating either parameter on the connect URL returns `400` `FILTER_CONFLICT`. ## Streaming fetch example [#streaming-fetch-example] ```js const response = await fetch("https://zerocut.gg/api/v1/events/stream", { headers: { "X-API-Key": process.env.ZEROCUT_API_KEY, Accept: "text/event-stream", ...(lastEventId ? { "Last-Event-ID": lastEventId } : {}), }, }); if (!response.ok) throw new Error(await response.text()); const reader = response.body.pipeThrough(new TextDecoderStream()).getReader(); let buffer = ""; while (true) { const { value, done } = await reader.read(); if (done) break; buffer += value; let split; while ((split = buffer.indexOf("\n\n")) !== -1) { const raw = buffer.slice(0, split); buffer = buffer.slice(split + 2); let id; let data; for (const line of raw.split("\n")) { if (line.startsWith("id: ")) id = line.slice(4); if (line.startsWith("data: ")) data = JSON.parse(line.slice(6)); } if (id) lastEventId = id; if (data?.family === "domain") handleEvent(data); } } ``` Reconnect when the loop ends, using the last id you stored. ## Handling events with one switch [#handling-events-with-one-switch] Every domain frame shares the same envelope and discriminates on `type`, so a single `switch` covers the whole catalog. Copy these types — they match the field tables above exactly: ```ts type PerkLine = { id: string; title: string; quantity: number; unitAmount: number; lineTotal: number; currency: string; }; type Envelope = { id: string; family: "domain"; type: Type; version: 1; createdAt: string; replayed: boolean; data: Data; }; type DonationCreated = Envelope< "donation.created", { id: string; amount: number; currency: string; donorName: string | null; message: string | null; country: string | null; perk: { id: string; title: string } | null; perks: PerkLine[]; createdAt: string; } >; type PerksPurchased = Envelope< "perks.purchased", { donationId: string; currency: string; donorName: string | null; perk: { id: string; title: string | null } | null; perks: PerkLine[]; cartTotal: number | null; createdAt: string; } >; type FollowerCreated = Envelope< "follower.created", { id: string; username: string; displayName: string | null; platform: string; origin: "manual" | "provider" | "legacy"; createdAt: string; } >; type GoalReached = Envelope< "goal.reached", { goalId: string; description: string | null; amount: number; totalRaised: number; currency: string; completedAt: string; } >; type ZeroCutEvent = DonationCreated | PerksPurchased | FollowerCreated | GoalReached; ``` ```ts function handleEvent(frame: ZeroCutEvent) { switch (frame.type) { case "donation.created": console.log(`${frame.data.donorName ?? "Anonymous"} donated`, frame.data.amount); break; case "perks.purchased": console.log(`${frame.data.donorName ?? "Anonymous"} purchased`, frame.data.perks); break; case "follower.created": console.log(`${frame.data.username} followed on ${frame.data.platform}`); break; case "goal.reached": console.log(`Goal reached: ${frame.data.totalRaised}/${frame.data.amount}`); break; default: // New types may be added; ignore what you do not recognise. break; } } ``` Route into it from either transport. The streaming-fetch loop above already calls `handleEvent(data)` for `family === "domain"` frames. With `EventSource`, named `event:` lines mean `onmessage` never fires — attach the same listener once per type: ```ts const TYPES = ["donation.created", "perks.purchased", "follower.created", "goal.reached"] as const; for (const type of TYPES) { source.addEventListener(type, (event) => { lastEventId = event.lastEventId; handleEvent(JSON.parse(event.data) as ZeroCutEvent); }); } ``` If you subscribed with an `events` filter, only the listed types can arrive — the unused `case` branches are simply never hit, so the same handler works for a full stream and a donations-only stream alike. ## Channels and scope [#channels-and-scope] The stream is scoped to the account that owns the key. There is no way to request a channel: a `channels` query parameter returns `400` `CHANNEL_PARAM_NOT_ALLOWED` rather than being ignored, and `client_type` returns `400` `CLIENT_TYPE_NOT_ALLOWED`. ## Limits [#limits] | Limit | Value | | --------------------------- | ----------- | | Connects per IP | 60 / minute | | Connects per API key | 20 / minute | | Stream-token mints per key | 30 / minute | | Concurrent streams per key | 4 | | Concurrent streams per user | 16 | | Concurrent streams per IP | 64 | Exceeding a concurrency limit returns `429` with code `TOO_MANY_CONNECTIONS` and a `Retry-After` header. The per-IP ceiling is shared with the creator's own dashboard and overlay connections from the same address, so an aggregator hosting many creators' integrations on one host can reach it before the per-key and per-user caps. Connections rotate shortly before 5 minutes with a `reconnect` frame. That is normal — reconnect immediately with your last id. A connection that stops reading is disconnected rather than buffered indefinitely. Process frames promptly and hand slow work to a queue. Rejections before the stream opens are JSON `{ error, code }` bodies with the same status codes as the REST API. Once the response is `text/event-stream`, failures arrive as `error` control frames. ## CORS [#cors] The stream responds with `Access-Control-Allow-Origin: *` and never uses cookies, so `Access-Control-Allow-Credentials` is never set. `OPTIONS` preflight is supported. ## Test mode [#test-mode] `/api/test/v1/events/stream` and `/api/test/v1/events/stream-token` return `404`. There is no fixture stream: fabricated frames teach nothing about ordering, replay, or backpressure. Develop against your own key and a sandbox donation. --- # Followers by Date Range - Canonical page: https://zerocut.gg/docs/api/follower-by-date-range - Markdown version: https://zerocut.gg/docs/api/follower-by-date-range.md Get historical follower counts per day within a date range. --- # Current Follower Count - Canonical page: https://zerocut.gg/docs/api/follower-current - Markdown version: https://zerocut.gg/docs/api/follower-current.md Get the current (latest) follower count. --- # List Followers - Canonical page: https://zerocut.gg/docs/api/follower-list - Markdown version: https://zerocut.gg/docs/api/follower-list.md Get a paginated list of follower count records. --- # Follower Stats - Canonical page: https://zerocut.gg/docs/api/follower-stats - Markdown version: https://zerocut.gg/docs/api/follower-stats.md Get follower growth statistics. --- # Update Follower Count - Canonical page: https://zerocut.gg/docs/api/follower-update - Markdown version: https://zerocut.gg/docs/api/follower-update.md Update/upsert the follower count. --- # Add Follower - Canonical page: https://zerocut.gg/docs/api/follower - Markdown version: https://zerocut.gg/docs/api/follower.md Add a follower count record via the API. --- # Active Goals - Canonical page: https://zerocut.gg/docs/api/goal-active - Markdown version: https://zerocut.gg/docs/api/goal-active.md Get active (non-completed) donation goals with progress. --- # Get Goal - Canonical page: https://zerocut.gg/docs/api/goal-get-by-id - Markdown version: https://zerocut.gg/docs/api/goal-get-by-id.md Get a single donation goal with progress. --- # List Goals - Canonical page: https://zerocut.gg/docs/api/goal-list - Markdown version: https://zerocut.gg/docs/api/goal-list.md Get all donation goals with progress. --- # ZeroCut API reference > ZeroCut REST API authentication, test requests, rate limits, and versioning. - Canonical page: https://zerocut.gg/docs/api - Markdown version: https://zerocut.gg/docs/api.md Use the ZeroCut REST API to read your creator data and automate donations, follower records, and live sessions. The [OpenAPI specification](/api/v1/openapi) describes the JSON endpoints, their operation IDs, inputs, responses, and errors. ## Get started [#get-started] 1. [Sign in](/sign-in) and complete account setup. API access requires ZeroCut Premium; the donation-platform trial alone does not include API keys. 2. Create a key in [API key settings](/app/dashboard/settings/api-keys). Keep it in server-side secret storage. 3. Send the key in the `x-api-key` header. Start with `GET /api/v1/profile/get` to verify access. The documentation and OpenAPI specification are public. Account setup and key creation require a person to sign in; there is no anonymous key-issuance endpoint. ## Authentication [#authentication] All API requests require an API key passed in the `x-api-key` header: ```bash curl -H "x-api-key: zerocut.your_api_key_here" \ https://zerocut.gg/api/v1/profile/get ``` You can create and manage API keys in your [dashboard settings](/app/dashboard/settings/api-keys). Keys belong to one creator account. They grant access to that account's API reads and writes and can be disabled or revoked in settings. There are no per-key permission scopes or delegated OAuth grants. ZeroCut's provider sign-in and payment-provider connections do not authorize REST API clients. ## Test requests [#test-requests] Use `/api/test/v1` in place of `/api/v1` for the documented test responses. Authentication, subscription checks, input validation, and rate limits still apply. Test requests can write API usage logs. Event streaming and stream-token creation are unavailable in test mode. For example, test donation creation with a fixture response: ```bash curl https://zerocut.gg/api/test/v1/donation/create \ -H "x-api-key: $ZEROCUT_API_KEY" \ -H 'Content-Type: application/json' \ -d '{"amount":10,"currency":"usd","donorName":"Test Donor"}' ``` The test donation endpoint returns sample data without recording a real donation or charging a payment method. The production donation endpoint records a donation; do not use it as a connectivity probe. ## Live Events [#live-events] `GET /api/v1/events/stream` pushes donations, perk purchases, followers, and goal completions over Server-Sent Events. Use `GET /api/v1/perk/list` to discover IDs for a perk-filtered subscription. The stream returns `text/event-stream`, which has no JSON response schema, so it is **absent from the OpenAPI document** and from any client generated from it — do not expect a generated method for it. It is documented by hand in [Event Stream (SSE)](/docs/api/events-stream). Its companion `POST /api/v1/events/stream-token` is a normal JSON endpoint and is in the document. ## Rate Limiting [#rate-limiting] The JSON API enforces a sliding window rate limit of **60 requests per minute** per user account. All API keys belonging to the same account share this limit. A separate **120 requests per minute** IP limit applies before authentication. Stream-token creation also has a **30 requests per minute** limit per key. The [event stream](/docs/api/events-stream) has separate connection limits. ### Response Headers [#response-headers] Responses from the JSON API dispatcher include the applicable rate limit headers, including authentication failures, unknown API paths, rejected HTTP methods, and throttled responses. Public documentation and OpenAPI responses do not consume this quota and do not report a remaining allowance. `RateLimit-Policy` and `RateLimit` use the [IETF HTTPAPI draft format](https://www.ietf.org/archive/id/draft-ietf-httpapi-ratelimit-headers-11.html). Existing `X-RateLimit-*` headers remain available. | Header | Description | | ----------------------- | ------------------------------------------------------------------------------------ | | `RateLimit-Policy` | Policy name, request quota, and window in seconds, such as `"account";q=60;w=60` | | `RateLimit` | Remaining requests and seconds until capacity returns, such as `"account";r=59;t=60` | | `X-RateLimit-Limit` | Maximum requests allowed for the reported policy | | `X-RateLimit-Remaining` | Requests remaining in the current window | | `X-RateLimit-Reset` | Unix timestamp in seconds when the oldest request leaves the sliding window | ### Rate Limit Exceeded [#rate-limit-exceeded] When the limit is exceeded, the API returns a `429 Too Many Requests` response with an additional `Retry-After` header indicating how many seconds to wait: ```json { "error": "Rate limit exceeded. Please try again later.", "code": "TOO_MANY_REQUESTS" } ``` ### Best Practices [#best-practices] * Monitor the `X-RateLimit-Remaining` header and back off before hitting 0 * Cache responses client-side when possible * Use the `Retry-After` header to schedule retries after a 429 response ## Versioning and deprecation [#versioning-and-deprecation] The current REST API version is `v1`, served at `/api/v1`. Breaking request or response changes require a new API version. Clients should tolerate new optional fields and new endpoints within a version. Deprecations are announced in the [ZeroCut changelog](/changelog), with a replacement and a retirement date before removal. A retiring endpoint will carry `Deprecation` and `Sunset` response headers. No retirement date is currently scheduled for v1, so current responses do not include those headers. --- # Add Session Event - Canonical page: https://zerocut.gg/docs/api/live-session-add-event - Markdown version: https://zerocut.gg/docs/api/live-session-add-event.md Add an event to a live session. --- # Delete Live Session - Canonical page: https://zerocut.gg/docs/api/live-session-delete - Markdown version: https://zerocut.gg/docs/api/live-session-delete.md Delete a live session. --- # Get Session Events - Canonical page: https://zerocut.gg/docs/api/live-session-events - Markdown version: https://zerocut.gg/docs/api/live-session-events.md Get events for a live session. --- # Get Live Session - Canonical page: https://zerocut.gg/docs/api/live-session-get-by-id - Markdown version: https://zerocut.gg/docs/api/live-session-get-by-id.md Get a live session by ID with associated donations. --- # List Live Sessions - Canonical page: https://zerocut.gg/docs/api/live-session-list - Markdown version: https://zerocut.gg/docs/api/live-session-list.md Get a paginated list of live sessions. --- # Update Live Session - Canonical page: https://zerocut.gg/docs/api/live-session-update - Markdown version: https://zerocut.gg/docs/api/live-session-update.md Update a live session. --- # Add Live Session - Canonical page: https://zerocut.gg/docs/api/live-session - Markdown version: https://zerocut.gg/docs/api/live-session.md Add a live streaming session record via the API. --- # Get Donation Perk - Canonical page: https://zerocut.gg/docs/api/perk-get-by-id - Markdown version: https://zerocut.gg/docs/api/perk-get-by-id.md Get one current donation perk. A deleted perk returns `null`; use the frozen snapshot on its donation when reconciling an older purchase. --- # List Donation Perks - Canonical page: https://zerocut.gg/docs/api/perk-list - Markdown version: https://zerocut.gg/docs/api/perk-list.md List current donation perks and obtain the stable IDs accepted by the event stream's `perkIds` filter. This is the mutable catalog; historical donations carry their own frozen `perk` and `perks` snapshots. --- # Get Profile - Canonical page: https://zerocut.gg/docs/api/profile-get - Markdown version: https://zerocut.gg/docs/api/profile-get.md Get your own profile information. --- # Query Donation - Canonical page: https://zerocut.gg/docs/api/query-donation - Markdown version: https://zerocut.gg/docs/api/query-donation.md Query a donation by ID via the API. --- # Visitor Aggregate - Canonical page: https://zerocut.gg/docs/api/visitor-aggregate - Markdown version: https://zerocut.gg/docs/api/visitor-aggregate.md Aggregate visitor stats for your handle page (visitors, pageviews, bounce rate, visit duration, visits) with % change vs previous period. Premium only. --- # Visitor Breakdown - Canonical page: https://zerocut.gg/docs/api/visitor-breakdown - Markdown version: https://zerocut.gg/docs/api/visitor-breakdown.md Top-N visitor breakdown by source, referrer, country, region, device, browser, or OS. Premium only. --- # Visitor Donation Methods - Canonical page: https://zerocut.gg/docs/api/visitor-donation-methods - Markdown version: https://zerocut.gg/docs/api/visitor-donation-methods.md Donation events broken down by payment method for your handle page. Premium only. --- # Visitor Goal Conversions - Canonical page: https://zerocut.gg/docs/api/visitor-goals - Markdown version: https://zerocut.gg/docs/api/visitor-goals.md Donation-event conversion stats for your handle page — unique donors, total donation events, and conversion rate. Premium only. --- # Visitor Realtime - Canonical page: https://zerocut.gg/docs/api/visitor-realtime - Markdown version: https://zerocut.gg/docs/api/visitor-realtime.md Current live visitor count. Site-wide due to an analytics-provider limitation — not filtered by handle. Premium only. --- # Visitor Timeseries - Canonical page: https://zerocut.gg/docs/api/visitor-timeseries - Markdown version: https://zerocut.gg/docs/api/visitor-timeseries.md Daily visitor timeseries for your handle page. Historical days cached 24h; today refreshed every 60s. Premium only.