Changelog

RSVPs now expose a writable status field: tentative, confirmed, attended, or rejected. See the RSVP reference and cookbook.

• Read status and filter with ?status=.
• Set status on POST and PATCH. attended does not need a check-in time.
• confirmed, tentative, and rejected clear an existing check-in time.
• checked_in_at is accepted on POST as well as PATCH.

To write status, add it to the token scope’s Writable fields. A status change that would clear a recorded check-in time also needs checked_in_at there. Integrations should not assume every attended RSVP has a checked-in-at value.

The Brella Core API skill 1.2.0 adds a workflow for event and organization insights reports covering adoption, networking quality, meeting pairs, sessions, sponsors, interests, power users and recommendations.

• Follow Create an event insights report for resource access, counting definitions, rating scales and missing metrics.
• Use the bundled HTML template to select event or organization views, filter tables, switch themes and print a dated snapshot.
• Keep formulas, sources and coverage visible, including unavailable message reply rates and overlapping populations.

Replace your installed skill bundle to get the new workflow and template. Reporting uses existing Read endpoints and authorized local calculations; this update does not change the API contract. Live retrieval requires an authenticated API tool, and generating the report requires analysis and file tools.

These guides describe the Core API update scheduled for production on 9 October 2026. Documentation is being published ahead of the backend deployment; availability has not yet been confirmed. Check with Brella before relying on the changes in your production integration.

The upcoming update adds event-level sponsor setup and lead-scanning configuration:

• Sponsor categories: read, create, update and delete categories, with external IDs, display order and booth-meeting settings. Category deletion also removes its sponsors.
• Scanning questions: read, create, update and delete sponsor-owned lead questions. Choice questions support up to 50 non-empty string options, each up to 1,000 characters. Question deletion also removes collected answers.
• Speakers: DELETE is available with the scope’s delete action. The speaker becomes unavailable immediately and related cleanup is scheduled after commit.
• Registrant QR values: configure external_qr_string on create or update, including joined registrants. Read the effective external-qr-string and stable internal-qr-string separately. Overrides are unique within an event and cannot use internal Brella QR formats.

Networking-timeslot input change: remove registrant_list_ids and rating_registrant_list_ids from networking-timeslot requests and scope mappings. These inputs are unsupported and ignored. Configure event access separately.

The new resources require their own enabled token scopes. Grant only the actions, events, fields and filters your integration needs. See the cookbook examples for categories and questions.

The lead reference and create/update cookbook now explain how to create a lead with an omitted or null sponsor_id, how sponsor-restricted scopes choose a sponsor, and why omitting the field on PATCH preserves existing ownership.

The export guide covers event exports that include leads with sponsor-ids: [] and explains why sponsor filters and sponsor-restricted scopes exclude those leads.

The updated export guidance is also included in version 1.1.1 of the agent skill bundle. Replace an installed copy to use the revised bundled reference.

The Brella Core API skill now includes workflows for creating conference dashboards, exhibitor reports, networking reviews, event comparisons and program-planning briefs from existing Core API data.

• Start with one of the five prompts in Create dashboards and reports.
• Use the bundled Markdown report template to record findings, sources, calculations and missing data.
• Follow the shared metric interpretation guide for denominators, overlapping populations, comparisons and timeline verification.

The skill uses Read scopes for reporting. Producing a dashboard or report requires an agent with suitable analysis and file tools; live retrieval also needs an authenticated HTTPS tool.

Replace your installed skill bundle to get these instructions and references. This update adds reporting guidance for existing endpoints; it does not change the API contract.

The docs bring Brella’s updated website styling to black and charcoal surfaces, neutral text and white primary buttons in dark mode. Blue accents highlight links and controls in both themes, with a deeper blue on light mode’s white background.

Cards, request builders and the scope explorer share the same visual treatments. Validation errors have a distinct color, and the Brella tab icon uses the refreshed black-and-white palette.

Start from the overview, explore token scopes, or try the agenda recipe.

The rate-limit guide now states both limits:

• 500 requests per token per minute.
• 500 requests per IP per minute.

Both apply to the same traffic. The guide covers coordinating shared jobs, reusing snapshots and handling 429 responses. This corrects the documented limits; it is not an announcement of a new API limit.