Event API · Planned

A planned API for connected Event workflows.

API and webhooks are planned Business capabilities for connecting Events, attendees, calendar invitations and RSVP updates. No production API is available yet.

Request Business Access See example structure

Embedded registration forms remain included with Free.

                
                
                
              

curl https://api.bloomod.com/v1/events/evt_0182/invitations \
  -H "Authorization: Bearer $BLOOMOD_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "attendee_id": "att_0182",
    "requires_approval": true
  }'

# Planned example only
# No production endpoint is available
            

const res = await fetch("https://api.bloomod.com/v1/events/evt_0182/invitations", {
  method: "POST",
  headers: {
    Authorization: `Bearer ${process.env.BLOOMOD_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    attendee_id: "att_0182",
    requires_approval: true
  })
});

const invite = await res.json();
            

import os, requests

res = requests.post(
    "https://api.bloomod.com/v1/events/evt_0182/invitations",
    headers={"Authorization": f"Bearer {os.environ['BLOOMOD_KEY']}"},
    json={
        "attendee_id": "att_0182",
        "requires_approval": True,
    },
)

invite = res.json()
            

Planned API example. Names and paths may change before early access.

Example API structure

Proposed resources follow the Event workflow.

Planned example API resources
Method	Path	Does	Approval
POST	/v1/events	Create an Event	n/a
POST	/v1/events/{event}/attendees	Add an attendee to one Event	n/a
PATCH	/v1/events/{event}/attendees/{attendee}	Update attendee or verification status	n/a
POST	/v1/events/{event}/invitations	Queue a calendar invitation	Required
GET	/v1/events/{event}/invitations	Read delivery and RSVP status	n/a
DELETE	/v1/events/{event}/invitations/{invitation}	Request an Event cancellation update	Required

In the proposed model, invitation writes enter a review queue. This is an example design, not a promise of final paths, response codes or production availability.

Planned authentication

Proposed scoped keys limit each integration.

Early-access credentials are expected to carry narrow scopes, so attendee access, invitation writes and webhook management can be separated.

Bearer-style authentication is proposed
Separate test and live access is planned
Per-key scopes and rotation are planned
Credential use should appear in account activity

Scope

attendees:write

Create and update event attendees and verification status.

Scope

invites:write

Queue Event invitations for approval.

Scope

invites:read

Read lifecycle stage and RSVP state.

Scope

webhooks:manage

Register endpoints for RSVP and delivery events.

Planned webhooks

Event and RSVP updates, without polling.

Proposed webhooks would let Business integrations receive selected Event, attendee, invitation and RSVP changes. No live webhook service is attached today.

event.created attendee.registered attendee.verified invitation.sent rsvp.updated

POST your-endpoint

{
  "type": "rsvp.updated",
  "created": "2026-08-13T05:12:44Z",
  "data": {
    "event_id": "evt_0182",
    "attendee_id": "att_0182",
    "invitation_id": "inv_7Kq2",
    "rsvp_status": "accepted",
    "calendar": "google"
  }
}

Planned operating model

Operational limits will be published before launch.

Scoped

Access by integration purpose

Queued

Invitation writes enter review

Signed

Webhook verification is planned

Published

Limits documented before availability

Final authentication, paths, rate limits and webhook behaviour will be documented when early access opens. Calendar providers may also apply their own quotas and anti-abuse limits.

Tell us what your Event integration needs.

Request Business Access Security model