Docs

Live reactions for static sites, blogs, and docs — the bar goes on any page in two lines. Readers tap; everyone watching sees it fall, in real time.

Get a key

Create an account, then create a Tapbar in the console. You'll get a publishable key (pk_live_…) for your embed and a secret key shown once — keep it safe, but you don't need it for the basic embed.

Paste the snippet

Drop this where the reactions bar should appear. The console's Embed panel generates it pre-filled with your key.

<script type="module" async src="https://api.tapback.party/loader.js"
  data-key="pk_live_yourkey"
  data-api="https://api.tapback.party"
></script>
<tapback-bar entity="your-page-id"></tapback-bar>

The bar renders with the reactions, colors, icons, and layout you set in the console — change them there and every embed updates, no code change needed. entity names the counter; leave it off and Tapback infers one from the page's URL.

Where next

Setting up a blog? Reactions on your blog has copy-paste recipes for Hugo, Jekyll, Eleventy, Astro, Next.js, Gatsby, Zola, Ghost and WordPress — inline bars on the index, a floating bar on the post.

Making it yours? Theming covers icons, colors, and layout; the embed reference lists every attribute the script and the bar accept, and how entities scope a count.

Building past the bar? The JS API fires reactions from your own buttons and renders live counts in your own UI; ambient mode drops the bar entirely. Verifiable counts and export get the numbers out, and your agent can run all of it over MCP.

Sizing it up? Plans & limits is every cap in one table, privacy is the complete inventory of what Tapback stores, and what's the catch? is how a free live widget pays for itself.