API
Hyper does not yet publish this page as a stable public API reference. Use this page as current-status guidance so rollout owners and developers can understand what is supported today and which alternative path to use instead.
Current support status
Section titled “Current support status”- A stable public API contract is not currently documented here.
- The supported path for most production workflows is still built-in integrations, workspace automations, and export or reporting flows that already exist in the product.
- Do not build against an assumed API surface until your deployment has a formal contract, auth model, and versioning agreement.
What to use instead right now
Section titled “What to use instead right now”- Calendars for meeting creation and sync.
- Slack, Notion, and automations for follow-up routing.
- Reporting and export workflows for downstream analysis when they are available in your deployment.
What to collect before requesting API access
Section titled “What to collect before requesting API access”- Auth and versioning should be treated as part of the contract, not as implementation detail.
- Artifact permissions and retention rules still apply when meeting data leaves Hyper through an API.
- The first practical API use cases are usually post-meeting routing, reporting, and lifecycle automation.