Developer access
API keys, service accounts, OAuth apps and webhooks for agents, integrations and automations.
Developer (/app/settings/developer) creates Blocchi credentials for agents, integrations and automations without sharing your login session. Use them with the REST API and MCP.
API keys
Two kinds of key:
| Key | Acts as | Who can create it |
|---|---|---|
| Personal key | You. It always follows your current Blocchi role and data scope. | Any member |
| Service account | A workspace-owned machine identity for durable automations. | Workspace admins |
When you create a key, choose its scopes — for example compute metrics and analytics, trigger source synchronization, manage findings and decisions, or change governed configuration — and optionally restrict it to specific networks. The secret is shown once; store it safely.
Send it as a bearer token:
OAuth apps
Create OAuth apps for integrations that act on behalf of users, or install a public app for the workspace. Deleting or uninstalling an app revokes its tokens and workspace authorization. Save the client secret when it is shown.
Webhooks
Register webhook endpoints to receive Blocchi events. Each endpoint gets a signing secret (shown once) to verify deliveries, and you can send a test event and watch its delivery status.
Good to know
- Keys and apps never bypass governance: consequential actions still require confirmation or approval and are audited.
- For scoped non-human routines with daily limits, see Automation identities.
Related
Last updated on