UniAsset
Home/Knowledge Base/Settings/Integrations Overview — API Keys, Webhooks, and Entra ID
Back to Settings

Integrations Overview — API Keys, Webhooks, and Entra ID

4 minIntermediateLast updated: January 2, 2026

Integrations overview

Settings → Integrations is the developer platform: API keys, webhooks, the activity log, and the developer guide.

Requirements

  • Available on: Odyssey, Cosmos
  • Roles: Owner only

The whole subtree is Owner-only. Admins and Managers cannot reach it.

The five sections

SectionWhat it does
OverviewThe landing page for the integration platform
API KeysCreate, inspect, and revoke keys for machine access
WebhooksPush events from UniAsset into your own systems
Activity LogEvery API request made against your keys
Developer GuideEndpoints, payloads, and examples, in-product

What you can do with the API

The REST API covers:

  • Creating assets
  • Updating asset assignment
  • Recording maintenance
  • Updating geo position
  • Ingesting IoT signals

See Getting started with the REST API.

Webhooks

Thirteen event types can be pushed to an HTTPS endpoint you control, signed so you can verify they came from UniAsset.

See How to use webhooks.

The activity log

Every API request against your keys is recorded: endpoint, key, IP address, status code, timestamp, and a sanitised request body.

Failed requests are logged as faithfully as successful ones, which is what makes the log useful precisely when an integration is broken.

Watch it while going live. It is the fastest way to see what the server actually received rather than what you think you sent.

Microsoft Entra ID

(Cosmos)

Directory sync — automatic user provisioning, group-to-role mapping, and deprovisioning — is configured from the integrations area. It is a separate capability from API access.

See Connecting Microsoft Entra ID.

What happens if you downgrade

Nothing is deleted. API keys are not revoked and webhooks are not deactivated by a plan change.

They stop working while the capability is absent — webhook deliveries for organizations without the capability are dropped without an HTTP call — and resume on upgrade with nothing to reconfigure.

Common mistakes

Expecting Admins to be able to manage keys. Integrations is Owner-only.

Assuming IoT works with any API key. IoT ingestion is gated separately and needs the IoT permission on the key as well as the plan capability.

Ignoring the activity log during setup. Most integration problems are visible there in seconds.

Troubleshooting

Integrations isn't in my Settings. It needs Odyssey or above, and Owner.

I'm an Admin and can't get in. Integrations is Owner-only. The settings index used to advertise it to Admins who were then turned away on arrival; it no longer does.

My API calls return 403 PLAN_UPGRADE_REQUIRED. Your plan does not include API access. Odyssey or above is required.

My webhooks stopped delivering. Check your plan still includes webhooks. Deliveries for organizations without the capability are dropped.

Related articles

Need Help?

If you have questions not covered in this article, our support team is here to help.

Contact Support