Microsoft Power Apps
Collection of APIs for Microsoft Power Apps platform enabling low-code application development, automation, and data connectivity.
Solid contracts, transparent operations, and an easy start — typically complete on four or five facets with one clear soft spot.
API Evangelist profiles Microsoft Power Apps the way a machine reads it — 73 machine-readable artifacts across 1 API, 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 — Microsoft Power Apps scores 58.3/100 (strong), with a separate agent-readiness read of 27/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from Microsoft Power Apps'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/microsoft-power-apps/"
title="Microsoft Power Apps on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/microsoft-power-apps.svg"
alt="Microsoft Power Apps Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/microsoft-power-apps/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/microsoft-power-apps/"
title="Microsoft Power Apps on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/microsoft-power-apps/card.svg"
alt="Microsoft Power Apps 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 Microsoft Power Apps
Each block below is one kind of artifact we hold for Microsoft Power Apps. 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 12
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.
Power Apps Management API
API for administrative tasks including environment management, app sharing, and user permissions.
Power Apps Connectors API
API for working with custom and standard connectors to integrate external services and data sources.
Power Apps Canvas Apps API
API specific to Canvas Apps for creating pixel-perfect user interfaces with drag-and-drop functionality.
Power Apps Model-driven Apps API
API for Model-driven Apps that automatically generate UI based on data model and business logic.
Power Apps Component Framework (PCF) API
Framework API for professional developers to create reusable code components for model-driven and canvas apps using TypeScript and web technologies.
Power Platform REST API
Unified RESTful API for Power Platform administration including environment management, governance, licensing, app management, and capacity reporting.
Power Pages Web API
Web API for Power Pages (formerly Power Apps Portals) enabling CRUD operations on Dataverse tables from external-facing portal web pages.
Dataverse Organization Service SDK
.NET SDK providing strongly-typed access to Microsoft Dataverse through the IOrganizationService interface for server-side development and plugins.
Power Apps Code Apps API
API and SDK for building code-first Power Apps using popular frameworks like React and Vue, developed in any code-first IDE and deployed to Power Apps.
Microsoft Power Apps Accounts API
Operations on the account entity set. An account represents a business that is a customer or potential customer, typically the company billed in business transactions.
Microsoft Power Apps Contacts API
Operations on the contact entity set. A contact represents a person with whom a business unit has a relationship, such as a customer, supplier, or colleague.
Microsoft Power Apps Entities API
Operations on the entity definition entity set. Provides metadata about Dataverse tables (entities) including their logical names, collection names, and structural information. ...
Scroll within the panel for all 12 ·
Postman Collections 3
A runnable collection turns the contract into something a developer can execute in seconds. We profile them because the fastest way to trust an API is to make a real call against it.
Ready-to-run Postman collections for exercising this provider's APIs.
Open Collections 5
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 COLLECTIONMicrosoft Power Apps Microsoft Dataverse Web Accounts API
OPEN COLLECTIONMicrosoft Power Apps Microsoft Dataverse Web API
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the things the Kin Score reads for access clarity — renamed from commercial clarity in rubric 0.12, because a free statutory interface has access terms and no commercial ones.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Microsoft Power Apps Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Features 5
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
Low-Code Development
Visual drag-and-drop app building with Power Fx formulas and pre-built templates.
Microsoft Dataverse
Built-in data platform with security, business logic, and integration capabilities.
Custom Connectors
Connect to any external API through standard and custom connector definitions.
Model-Driven Apps
Automatically generated UIs based on data model and business logic configuration.
Component Framework
Professional code components using TypeScript for custom controls in canvas and model-driven apps.
Semantic Vocabularies 2
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Spectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
Microsoft Power Apps API Rules
SPECTRALMicrosoft Power Apps API Rules
SPECTRALJSON Schema 14
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
Account
JSON SCHEMAAccountCollection
JSON SCHEMAContact
JSON SCHEMAContactCollection
JSON SCHEMAAccountCollection
JSON SCHEMAAccount
JSON SCHEMAContactCollection
JSON SCHEMAContact
JSON SCHEMAEntityCollection
JSON SCHEMAEntity
JSON SCHEMAODataError
JSON SCHEMAMicrosoft Power Apps Dataverse Entity Schema
JSON SCHEMAEntityCollection
JSON SCHEMAODataError
JSON SCHEMAScroll within the panel for all 14 ·
JSON Structure 8
JSON Structure captures the data shapes in a form built for tooling — a complement to JSON Schema that keeps the model machine-legible.
JSON Structure definitions describing this provider's data shapes.
Microsoft Power Apps Dataverse Web Account Structure
JSON STRUCTUREMicrosoft Power Apps Dataverse Web Contact Structure
JSON STRUCTUREMicrosoft Power Apps Dataverse Web Entity Structure
JSON STRUCTUREMicrosoft Power Apps Structure
JSON STRUCTUREScroll within the panel for all 8 ·
Examples 7
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Scroll within the panel for all 7 ·
Security 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.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 4
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Business Process Automation
Digitize paper-based processes and manual workflows with custom business applications.
Customer Portal
Build external-facing portals using Power Pages with Dataverse Web API integration.
Field Service Apps
Create mobile applications for field workers with offline capabilities and data sync.
Data Management
Build CRUD applications on Dataverse for managing business data with role-based security.
Integrations 3
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Microsoft 365
Native integration with Teams, SharePoint, Outlook, and Excel for productivity workflows.
Dynamics 365
Shared Dataverse platform with Dynamics 365 CRM and ERP modules for unified data.
Power Automate
Trigger automated flows from Power Apps for cross-system process automation.
Resources
Every other property we hold for Microsoft Power Apps — 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 1
Portal, sign-up, and the first successful call
Documentation 5
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 5
Authentication, authorization, and security posture
Learn 2
Tutorials, courses, talks, and written guidance
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
← All providers · Data indexed from github.com/api-evangelist/microsoft-power-apps · machine-readable index on apis.io
This is an independent, third-party profile of Microsoft Power Apps, 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.