ButterflyMX
ButterflyMX is a property-access technology company whose smart video intercoms, keypads, smart locks, elevator controls, vehicle-access readers, package rooms and front-desk stations are installed in more than 20,000 multifamily, commercial, gated-community, student-housing and senior-living buildings. Its public ButterflyMX API (v4) exposes the same access-control core to partners and property-technology platforms: buildings, units, tenants, access points, devices, access groups, permanent access tools (PINs and RFID tags), keychains and virtual keys for visitor passes, door-release requests for programmatic swipe-to-open, and access and video-call logs. Real-time delivery is handled by building- and tenant-scoped webhook integrations, and native iOS and Android SDKs add in-app video-call handling on top of the REST surface. Authorization is OAuth 2.0 authorization-code, issued by an OpenID-Connect-discoverable authorization server at accounts.butterflymx.com, with a full sandbox replica for pre-production testing.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles ButterflyMX the way a machine reads it — 35 machine-readable artifacts across 14 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ButterflyMX scores 56.5/100 (strong), with a separate agent-readiness read of 44/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from ButterflyMX's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/butterflymx/"
title="ButterflyMX on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/butterflymx.svg"
alt="ButterflyMX Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/butterflymx/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/butterflymx/"
title="ButterflyMX on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/butterflymx/card.svg"
alt="ButterflyMX Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile ButterflyMX
Each block below is one kind of artifact we hold for ButterflyMX. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
ButterflyMX Access groups API
The Access groups API from ButterflyMX — 6 operation(s) for access groups.
ButterflyMX Access Logs API
The Access Logs API from ButterflyMX — 2 operation(s) for access logs.
ButterflyMX Access Points API
The Access Points API from ButterflyMX — 3 operation(s) for access points.
ButterflyMX Access Tools API
The Access Tools API from ButterflyMX — 5 operation(s) for access tools.
ButterflyMX Building Integrations API
The Building Integrations API from ButterflyMX — 2 operation(s) for building integrations.
ButterflyMX Buildings API
The Buildings API from ButterflyMX — 3 operation(s) for buildings.
ButterflyMX Calls API
The Calls API from ButterflyMX — 2 operation(s) for calls.
ButterflyMX Devices API
The Devices API from ButterflyMX — 2 operation(s) for devices.
ButterflyMX Door Release Requests API
The Door Release Requests API from ButterflyMX — 1 operation(s) for door release requests.
ButterflyMX Keychains API
The Keychains API from ButterflyMX — 6 operation(s) for keychains.
ButterflyMX Tenant Integrations API
The Tenant Integrations API from ButterflyMX — 2 operation(s) for tenant integrations.
ButterflyMX Tenants API
The Tenants API from ButterflyMX — 3 operation(s) for tenants.
ButterflyMX Units API
The Units API from ButterflyMX — 4 operation(s) for units.
ButterflyMX Virtual Keys API
The Virtual Keys API from ButterflyMX — 2 operation(s) for virtual keys.
Scroll within the panel for all 14 ·
Open Collections 15
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONButterflyMX Access groups API
OPEN COLLECTIONButterflyMX Access Logs API
OPEN COLLECTIONButterflyMX Access Points API
OPEN COLLECTIONButterflyMX Access Tools API
OPEN COLLECTIONButterflyMX Building Integrations API
OPEN COLLECTIONButterflyMX Buildings API
OPEN COLLECTIONButterflyMX Calls API
OPEN COLLECTIONButterflyMX Devices API
OPEN COLLECTIONButterflyMX Door Release Requests API
OPEN COLLECTIONButterflyMX Keychains API
OPEN COLLECTIONButterflyMX Tenant Integrations API
OPEN COLLECTIONButterflyMX Tenants API
OPEN COLLECTIONButterflyMX Units API
OPEN COLLECTIONButterflyMX Virtual Keys API
OPEN COLLECTIONScroll within the panel for all 15 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
butterflymx-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Butterflymx Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Resources
Every other property we hold for ButterflyMX — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/butterflymx · machine-readable index on apis.io
This is an independent, third-party profile of ButterflyMX, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.