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. See the API reference for the full list of endpoints a key can reach.

​
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. The signing secret is shown once, when you create the webhook, so copy it then. It is not shown again, and a webhook whose secret is lost has to be deleted and created again.

​
Power BI, Excel and Tableau (OData feed)

Integrations → Power BI configures a live, read-only OData v4 feed at /api/odata/Assets. It’s on by default for every organisation - a scoped API key is what actually lets a report connect, so switching the feed off pauses every connected report without touching any key.
  1. Open Integrations → Power BI and create a key. It only reads the feed.
  2. In Power BI Desktop, choose Get data → OData feed and paste the feed URL shown on the page.
  3. Choose Basic authentication, type any username (it’s ignored) and paste the key as the password, then connect.
The same Basic credentials work for a report published to the Power BI service - set them once on the semantic model’s data source under Settings → Data source credentials, with privacy set to Organizational, and no on-premises gateway is needed. Excel connects the same way, from Data → Get Data → From Other Sources → From OData Feed. The feed supports $filter, $select, $orderby, $top, $skip and $count, pages at 100 rows by default (up to 1000 if a client asks for more) and follows its own paging links, so a client keeps pulling past the first page automatically. Filtering on updatedAt is what lets Power BI’s incremental refresh pull only what changed since the last read, and each key reads with its creator’s own permissions, so a location- or field-restricted key produces a correspondingly restricted feed. Archived assets are excluded unless Include archived assets is turned on. The Power BI page also has Test connection, which reads the feed with your current session so a broken feed shows itself immediately, and Disconnect, which revokes the keys created for Power BI - an admin-scoped key that can also read the feed is left alone, and needs revoking individually if you mean to cut its access too.

​
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.