Documentation

Happa Plugin Platform

Build hosted plugins for Happa event creators. You run your own backend, and Happa connects to it with signed webhooks, installation-scoped API tokens, and audit logs in the developer portal.

Quickstart
Stand up a verified webhook endpoint in Node.js and receive your first test.ping.
Webhooks
Understand request signing, delivery timing, and how to build idempotent handlers.
REST API
Read events, attendees, polls, comments, profile data, and ticket revenue using installation tokens.
Scopes
Choose the smallest permission set your plugin needs and map it to the endpoints you call.
Financial Plugins
Review the extra approval, contracting, and operational controls for payment-sensitive integrations.

What a Happa plugin is

A Happa plugin is a service you host, not code you upload into Happa. The developer portal is for registering your integration, managing credentials, testing deliveries, reviewing logs, and submitting for marketplace approval.

Once installed by an organizer, Happa sends your backend signed HTTP webhooks and gives that installation its own scoped API token. Your service uses that token to call the Happa REST API for fresh data.

The platform is designed for automations, analytics, CRM sync, ticketing add-ons, and internal tooling that runs outside the Happa mobile app.

Portal flow: the homepage call to action now opens the portal first, then asks for Google sign-in only when you need to create or manage plugins. There is no in-browser plugin builder inside Happa.

Plugin lifecycle

  1. Register your plugin in the Developer Portal with a webhook URL, scopes, pricing, and categories.
  2. Receive credentials immediately: a public clientId and a secret webhookSecret.
  3. Build and test your backend against signed webhooks, API logs, and manual test.ping deliveries.
  4. Submit for review. Approved plugins appear in the marketplace; rejected ones return to draft with reviewer feedback.
  5. Store installation tokens when users install your plugin so your backend can call the API on their behalf.

Mental model: Happa provides the portal, install flow, webhooks, scoped REST API, and marketplace review. You provide the backend, business logic, storage, and deployment.

Sensitive category: if your plugin touches payments or other regulated financial workflows, read the Financial Plugins guide before you register it. Those integrations are reviewed under a separate approval standard.

Platform surface

Surface What it does
Developer Portal Create plugins, rotate credentials, test deliveries, review logs, and submit integrations for approval.
Signed webhooks Notify your backend about RSVPs, join requests, published events, and ticket sales in real time.
REST API Read and update scoped organizer data using one installation token per plugin install.
Audit logs Track webhook deliveries and API requests per plugin inside the portal.

Requestable scopes

Scope Access
events.readRead the organizer's events, comments, and polls.
events.writeUpdate an event's description, location, and date.
attendees.readList attendees for events the organizer owns.
attendees.writeAdd or remove attendees for organizer-owned events.
profile.readRead the installing organizer's profile and counts.
tickets.readRead aggregate ticket revenue and ticket counts without buyer PII.

Webhook events delivered today

Event When it fires
test.pingManual connectivity test from the developer portal.
event.createdAn organizer publishes a new public event.
rsvp.createdSomeone joins an event.
rsvp.cancelledAn attendee leaves an event.
join_request.createdA join request is submitted for an approval-based event.
join_request.approvedAn organizer approves a pending join request.
join_request.rejectedAn organizer rejects a pending join request.
ticket.soldA paid ticket purchase is confirmed for an organizer's event.

Need help? Start in the Developer Portal, then email developers@happa.site if you need a review unblock or API clarification.