How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Microsoft Power Platform Records API

The Records API from Microsoft Power Platform — 2 operation(s) for records.

Microsoft Power Platform Records API is one of 7 APIs that Microsoft Power Platform publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Records. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 5 operations across 2 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 9.2.

Requests are made against a single base URL, https://{org}.api.crm.dynamics.com/api/data/v9.2.

5 operations 2 paths 1 schemas 1 DELETE2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
9.2
Base URL
https://{org}.api.crm.dynamics.com/api/data/v9.2/
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Microsoft Power Platform Records API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 1 scope. By default, every request must be authenticated.

  • oauth2 — Microsoft Entra ID OAuth 2.0. Use the resource/scope corresponding to the Dataverse environment, e.g. https://{org}.api.crm.dynamics.com/.default for client cr…

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Records 5
GET
/{entitySetName}
Retrieve records from a Dataverse table
listRecords 7 params → 200
POST
/{entitySetName}
Create a record
createRecord 1 param body → 204201
GET
/{entitySetName}({id})
Retrieve a record by id
getRecord 3 params → 200404
PATCH
/{entitySetName}({id})
Update or upsert a record
updateRecord 2 params body → 204
DELETE
/{entitySetName}({id})
Delete a record
deleteRecord 2 params → 204

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is RecordCollection (3 properties). Each schema is shown below with its type and property counts.

RecordCollection
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

microsoft-power-platform-records-api-openapi.yml Raw ↑

Other APIs Microsoft Power Platform publishes across the network.

Microsoft Dataverse Web API
Power Platform Admin API
Power Platform Connectors
Microsoft Power Platform Metadata API
Power Platform API
Power Platform Enterprise Policies (Azure Resource Manager)
Where this information came from

This is an independent, third-party profile of Microsoft Power Platform Records API, 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.