Tenant API v1 — the contract automation teams actually read
Published OpenAPI specs, Postman collections, and permission scopes (`tenant.devices.write`, `tenant.integrations.m365.read`, `tenant.edge_devices.commands`, …) separate read telemetry from mutating operations — partners ship CI/CD‑safe integrations instead of screen‑scraping your tenant UI.
The tenant API spans context discovery, managed devices (provision, claim, reprovision, remote commands), locations and areas, reader presets, edge appliances, and explicit Microsoft 365 visit integration endpoints — everything namespaced per tenant header.
Personal API tokens inherit RBAC semantics — humans and service accounts stay distinguishable in audit evidence.
Edge gateways expose their own REST surfaces for appliance lifecycle; pairing cloud tenant APIs with edge automation covers full campus deployment pipelines.
Rate limits and error semantics mirror serious SaaS expectations — scripts recover predictably instead of hammering operators.
Interactive Scalar docs, OpenAPI YAML, and Postman artefacts ship alongside authenticated workspaces — procurement pilots review contracts beside live tenant references.
Spotlight
What API consumers get today
- OpenAPI YAML + Postman JSON maintained with releases — consumed via authenticated Scalar docs inside your tenant workspace.
- Granular ability scopes — separate read vs write vs command privileges for devices, edge hardware, locations, and integrations.
- Provisioning pipelines — create managed devices, issue claims, push remote commands, and audit outcomes programmatically.
- M365 visit automation — integration status and sync endpoints align visitor posture with calendar reality.
- Edge orchestration — manage edge devices and remote commands where LAN gateways participate in rollout.
- Tenant isolation by construction — ambiguous headers fail closed instead of leaking neighbouring estates.
Depth
Endpoints teams wire into CI/CD
Integration surfaces
Microsoft 365 visits status & sync — keep visitor programmes aligned without manual refresh jobs.
Managed devices
List, create, claim, reprovision, and issue remote commands — automate commissioning at scale.
Edge appliances
Provision gateways, patch metadata, and issue remote commands with the same scoped tokens.
Locations & areas
Structure automation around facility hierarchy — align orchestration jobs with physical truth.
Reader presets
Codify safe defaults and propagate configuration consistently across fleets.
Tokens & rotation
Tenant API tokens with explicit abilities — rotate and revoke without hunting shared secrets.
Motion
How platform teams ship safely
Read the contract
Import OpenAPI into your gateway — agree error semantics before writing glue.
Scope tokens
Grant least privilege per workload — readers vs integrations vs edge commands.
Automate
Wire provisioning pipelines with retries, backoff, and structured logging.
Prove audit
Demonstrate lineage for security reviews — tokens map cleanly to automation identities.
Outcomes teams feel in production
Fewer bespoke scripts and VPN‑dependent hacks holding integrations together.
Clear accountability when automation touches readers, gateways, or visitor records.
Partners onboard faster — references share OpenAPI artefacts instead of tribal knowledge.
Security reviews shorten because scopes encode intent explicitly.
Related reading
Continue in neighbouring hubs
Deep dives that pair naturally with this integration chapter.
Product preview
Chapter walkthrough
Short cinematic clip for this integrations chapter — muted, looped in-page players follow your motion preferences elsewhere on the site.
Integrations hub
Every integration chapter at a glance
Open a chapter for full narrative and product video — identity cloud, smart-building bridges, and developer APIs.
Identity cloud
Entra ID joins, Microsoft 365 visit API automation, and cohort semantics that match grants — no parallel IAM theatre.
Open
Smart building
OT bridges, building signals, and edge gateways with explicit segmentation discipline.
Open
Developer APIs
Tenant API v1 — OpenAPI, Postman, device provisioning, edge commands, and M365 visit sync with granular scopes.
OpenContinue exploring
Open workspace identity, facility topology, or ledger exports — or return to the platform core.