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.
The Developer Console at app.ionhour.com/developer is your home for all developer-facing operations. It's where you register apps, manage API credentials, and monitor how your integrations are performing.
Access the console by opening your avatar menu in the Ionhour dashboard and choosing Developer Console (or API Keys, which lands directly on Credentials). It's a standalone surface — your OAuth apps belong to you as a developer rather than to any workspace, and the console is also where you create and manage workspace API keys.
Credentials
The management home for your ionh_ API keys. Pick a workspace with the switcher in the page header — the table lists that workspace's keys, and everything you do on the page (create, edit, rotate, revoke) applies to the selected workspace.
What you see
| Column | What it tells you |
|---|---|
| Name | The key's name |
| Permission | Read Only or Read & Write (the scope of the key) |
| Expires | When the key expires, if configured |
| Calls | Total MCP tool calls made with this key |
| Last tool | The most recent MCP tool executed; empty if never called |
| Last used | When this key last made an API call, plus when it was created |
Disabled keys appear muted with a "Disabled" badge.
Creating and managing keys
Click Create token to mint a key: give it a name, choose a permission level (Read Only or Read & Write), optionally set an expiry, and optionally restrict it to specific resources. The secret is shown once — copy it immediately.
From the menu on each row you can Edit (rename, change permissions or restrictions), Rotate (mint a new secret under the same name, invalidating the old one), or Revoke (permanently disable the key).
Managing keys requires the workspace's API-keys permission and a plan that includes access tokens — other plans see an upgrade prompt for that workspace.
Empty state
If the selected workspace has no keys yet, use Create your first token right on the page.
Logs
A searchable, 30-day log of API requests made by your keys — both MCP tool calls and Integration API calls. Logs show what your integrations are doing, how fast they're running, and whether they succeeded.
What's captured
Every request made through:
- MCP tools — the 49 built-in Ionhour MCP server tools called via
POST /api/mcp - Integration API v1 — endpoints under
/api/v1/*
For each request, the log records:
- Tool or endpoint — the name of the MCP tool or the HTTP method and route
- Outcome — whether it succeeded (ok), failed (error), or was denied (denied)
- Latency — how many milliseconds the request took
- Key — which API key made the call
- Metadata — IP address and user agent for debugging
Logs are retained for 30 days, then purged automatically.
What's not captured
- Invalid or unknown keys — requests that fail authentication don't appear
- Chat assistant traffic — JWT-authenticated tool calls from the in-app assistant
- Dashboard traffic — only API-key-authenticated calls show up
- Monitoring endpoints — signal pings and slug provisioning don't log
Filtering logs
The filter bar narrows logs by:
- Surface — MCP vs Integration API (or all)
- Outcome — ok, error, denied (or all)
- Time range — last hour, today, last 7 days, etc.
- Search — tool name or endpoint path
Visibility rules
- Workspace owners and admins see all logs in that workspace
- Members and viewers see only logs from their own keys
Click any row to see the full details including IP, user agent, error code, and HTTP status.
Exporting
Export downloads the currently filtered view as CSV or NDJSON — the same rows, filters, and visibility rules as the table, up to 10,000 rows per export (a response header flags when the export was truncated).
The workspace switcher
The Credentials and Logs pages each carry a workspace switcher in their toolbar, listing every workspace you belong to. Selecting one scopes that page to the chosen workspace. The selection is shared between the two pages, local to the console, and never affects which workspace you're viewing in the dashboard.
Build on Ionhour
The Ionhour developer platform — register OAuth apps, request scoped permissions, and receive uptime webhooks, from your first credential to approved install.
OAuth apps
Register an OAuth app on the Ionhour developer platform — client types, one-time credentials, configuration, and the full review and distribution lifecycle.