Skip to main content
The developer area exposes the register to your own systems: a full API with per-key permissions, webhooks for events, and an OData feed for BI tools. Open Developer in the sidebar, or the API and AI agent access section under Integrations. Developer tools

​
API keys

External tools and AI agents connect through the same permissions model as your users. The recommended pattern:
  1. Create or pick a service identity in the workspace.
  2. Assign the minimum role and permissions needed, read-only where possible.
  3. Create an API key with matching scopes and an optional expiry date.
  4. Use that key in your agent or integration.
Each key shows its scopes and when it was last used, so unused or over-scoped keys are easy to spot and clean up.

​
Webhooks

Subscribe an external system to events like asset.created and asset.updated, and it gets a signed HTTP request the moment something happens instead of having to poll. Each webhook’s delivery history is visible on its page, including failures, so a broken endpoint is easy to diagnose. Verify the signature on your receiving end to confirm a delivery genuinely came from World Asset Register.

​
Data export

Data export configures a live, read-only OData v4 feed at /api/odata/Assets. Power BI, Excel and Tableau connect to it natively, authenticating with an API key or a workspace token. It supports filtering and incremental queries, so a BI dashboard can pull only what’s changed since its last refresh instead of the whole register every time.

​
MCP server

World Asset Register also runs an MCP server, so AI tools like Claude can work with your register directly, using either an API key or Clerk-hosted OAuth sign-in. This is the same permission-checked, generic-verb tool set the in-app AI assistant uses, so an external agent is bound by exactly the same role and field access rules a human member would be.