External Developer Docs

These docs are for developers outside the ARBEC product team who want to add conference-specific capabilities, build a companion app, or connect an existing service to an ARBEC edition.

You bring the plugin or integration code. The conference organization provides the edition context and authorizes access. Your software connects through the documented manifest, API, and webhook contracts.

What you can build

• Edition plugins that declare conference-specific capabilities such as navigation, session widgets, registration hooks, or webhooks.
• Companion apps that read the published agenda for an organization-owned edition through REST or GraphQL.
• Connected services that receive signed events when submissions, registrations, or sessions change.

Two tracks in this section

Integrations — for developers outside the ARBEC product team:

• Plugin Integration for the manifest contract, lifecycle endpoints, API keys, and webhook verification
• Plugin System for the extension model and rollout boundary
• API Overview for the public agenda surfaces

Contributors — for developers working inside this repository:

• Platform Architecture
• Repository Structure
• Local Setup and Running Services
• Mobile App Overview
• Contributing

How an external integration is adopted

1. Build and test your plugin or companion service outside ARBEC.
2. Agree the plugin key, version, capabilities, and edition with the conference organization.
3. Have an authorized conference manager register the manifest and provide the API key or webhook details your integration needs.
4. Verify the integration against the target edition before enabling it.
5. Monitor API usage and webhook delivery outcomes, and disable the plugin if the integration needs to be paused.

Follow the workflow using the documented public contracts.

Current availability

Manifest registration and lifecycle management are available through the authenticated developer-platform endpoints. The public SDK package, runtime loader, plugin execution hooks, and self-service developer portal are still rolling out. A registered manifest is therefore a declaration of intent today; it does not upload or execute third-party code by itself.

Scope note

These pages document the external integration contracts and their current rollout status. They are written for plugin authors and integration developers.