Build on Ionhour
The Ionhour developer platform — register OAuth apps, request scoped permissions, and receive uptime webhooks, from your first credential to approved install.
Ionhour lets you build integrations the same way you would for Slack, Discord, or PagerDuty: register an OAuth app, request the scopes your product needs, and let any Ionhour workspace install it with one consent screen — no more asking customers to paste API keys.
The developer platform is rolling out gradually. If the Developer Console isn't visible on your account yet, it hasn't been enabled for you — the APIs below describe the platform as it ships.
The Developer Console
Everything happens in the Developer Console at app.ionhour.com/developer — open your avatar menu in the dashboard and choose Developer Console. It's a standalone surface: OAuth apps belong to you as a developer, not to any single workspace.
How an integration comes to life
- Create an app — a name, a client type, and accepting the developer terms. You immediately get a
client_id(ionh_app_…), a client secret for confidential apps (ionh_sec_…), and a webhook signing secret (ionh_whsec_…). Secrets are shown once. - Configure it — add exact-match
httpscallback URLs, pick scopes per product API, and subscribe to webhook events. - Use it privately — draft apps can be installed into workspaces you're a member of, which is how you develop and test.
- Submit for review — complete the distribution controls (vendor name, support contact, privacy policy, terms of service, data declaration) and submit. The Ionhour review team checks your links, scopes, and redirect URIs.
- Publish — approved apps are listed in the Ionhour app directory and any workspace can install them. Changing a published app's scopes or event subscriptions sends it back for re-review before the update goes live.
What installs look like
When a workspace member installs your app they see a consent screen listing exactly the scopes and events you request. Two rules protect the workspace:
- Scopes are consent ceilings. A granted scope is the most your app can do — effective authority is additionally capped by the installing member's own role, and never exceeds Admin. Owner-only actions are unreachable over OAuth.
- Events are scope-gated. A webhook event is only delivered to an installation that granted its backing read scope — see Webhooks.
In this section
| Page | What's in it |
|---|---|
| Developer Console | Manage credentials across workspaces and view operational logs |
| OAuth apps | Registering apps, client types, credentials, review & distribution lifecycle |
| Scopes & product APIs | Every scope, grouped by product API, with the ceiling rules |
| Webhooks | Event types, delivery envelope, signature verification, secret rotation |
| REST API reference | Complete OpenAPI documentation for workspace management and monitoring |
| Integrations | Built-in notification channels and third-party app directory |
Building something on Ionhour means accepting the developer terms.
Switching Between Workspaces
Jump between every workspace you belong to with the workspace switcher, create new ones, and control which workspace Ionhour opens by default each session.
Developer Console
The Ionhour developer console — create and manage API credentials, rotate secrets safely, and inspect live request logs to debug your own integrations faster.