One documented API, one key, every product surface. AHRI's team builds new member tools directly on your website while Agend keeps the Upbeat integration, sync and security running underneath. Members feel the difference in days, not release cycles.
For years the safest way to change the member experience was to ask Agend to build it. That protected the Upbeat integration, but it put a queue between AHRI and its members. Build on Agend removes the queue without removing the protection.
One release train. Today every AHRI idea, large or small, travels through Agend's development queue and monthly deployment cycle before a member ever sees it.
The integration is opaque. Member data lives in Upbeat, and only Agend's plugins know how to talk to it safely, so AHRI developers have had no supported way to build against it.
Custom and core are coupled. AHRI-specific features currently live inside the same plugins as the core membership engine, so a change to one carries risk to the other.
This is not a roadmap pitch. The gateway, the keys, the documentation, the Upbeat data feeds, the widget library and the webhooks below are all in production now. AHRI can hold keys as soon as the pilot is agreed.
Every Agend product behind one base URL: api.agend.com.au/v1. 169 endpoints across CRM, events, learning, community, directory, jobs, cart and content, all versioned and consistent: same auth, same response envelope, same pagination.
Issue ag_live_ and ag_test_ keys from your Agend dashboard. Each key carries named permissions such as crm.contacts.browse, so a tool only ever sees what you granted it. Revoke in one click.
/v1/docs is generated from the running API (OpenAPI 3.1), so every endpoint, schema and example is current by construction, with copy-paste requests your developers can run immediately.
Member contacts and sales history flow from Upbeat into the platform nightly, with a weekly full reconciliation. Upbeat remains AHRI's system of record; the platform is the fast, safe surface to build on.
Pre-built components: event lists and calendars, course catalogue, CPD balance, directory search, community feed and member portal. Each mounts on any page with a key and a data-widget tag, WordPress included.
Subscribe to data-change events with signed (HMAC-verified) deliveries, delivery logs and one-click replay, so AHRI systems react to changes instead of polling for them.
Reads against synced member data are open today. Writes that must land in Upbeat arrive in four phases; writes to Agend-native products are already open.
| Surface | Example builds | Read via API | Write via API |
|---|---|---|---|
| CRM · contacts & memberships | Member dashboards, segment views, welcome journeys | Live | Phase 1 |
| CRM · invoices & statements | Statement views, payment history, finance reporting | Live | Phase 2 |
| Joining, renewals & upgrades | Join flows, upgrade forms, win-back campaigns | Live | Phase 3 |
| Events & registrations | Event listings, programmes, registration flows | Phase 4 | Phase 4 |
| Learning & CPD | Course catalogues, CPD balances, learning paths | Live | Live |
| Community, directory & jobs | Member directory, feeds, announcements, job board | Live | Live |
A platform you build on is a platform you should be able to interrogate. These are the calls we have made deliberately, and the two that need AHRI's voice before phase 1 starts.
Progress counts platform milestones, not promises: seven of thirteen are live. Reads are open now; each write phase unlocks a new class of tools AHRI can build and own.
The foundation AHRI builds on from day one: gateway, keys, docs, data feeds, widgets and webhooks.
Members update their own details through AHRI-built pages; changes confirm instantly and flow through to Upbeat.
Choose one read-only tool for AHRI developers to ship first: a member dashboard, a CPD view or a searchable directory are all single-key builds.
Agend issues ag_test_ keys and walks AHRI developers through /v1/docs in a one-hour screen share.
A working session to confirm the phase order against AHRI's roadmap: profiles, payments, joining, events, or a reorder if priorities differ.
One page that names what AHRI builds and owns, what Agend operates (sync, security, uptime) and how support flows between the two teams.