Microsoft Dynamics
Microsoft Dynamics 365 is a suite of enterprise resource planning (ERP) and customer relationship management (CRM) applications. It provides APIs across three main platforms: Business Central for small and mid-sized business ERP, Dataverse Web API for CRM and customer engagement, and Finance & Operations for enterprise-grade ERP covering finance, supply chain, manufacturing, and human resources. All APIs use OData v4 conventions and authenticate via Microsoft Entra ID.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles Microsoft Dynamics the way a machine reads it — 44 machine-readable artifacts across 19 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 — Microsoft Dynamics scores 53.4/100 (developing), with a separate agent-readiness read of 48/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-07-27 · rubric v0.5
How we profile Microsoft Dynamics
Each block below is one kind of artifact we hold for Microsoft Dynamics. 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 19
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.
Microsoft Dynamics Accounts API
The Accounts API from Microsoft Dynamics — 3 operation(s) for accounts.
Microsoft Dynamics Activities API
The Activities API from Microsoft Dynamics — 1 operation(s) for activities.
Microsoft Dynamics Cases API
The Cases API from Microsoft Dynamics — 1 operation(s) for cases.
Microsoft Dynamics Companies API
The Companies API from Microsoft Dynamics — 1 operation(s) for companies.
Microsoft Dynamics Contacts API
The Contacts API from Microsoft Dynamics — 2 operation(s) for contacts.
Microsoft Dynamics Customers API
The Customers API from Microsoft Dynamics — 3 operation(s) for customers.
Microsoft Dynamics Employees API
The Employees API from Microsoft Dynamics — 1 operation(s) for employees.
Microsoft Dynamics General Ledger API
The General Ledger API from Microsoft Dynamics — 2 operation(s) for general ledger.
Microsoft Dynamics Human Resources API
The Human Resources API from Microsoft Dynamics — 1 operation(s) for human resources.
Microsoft Dynamics Items API
The Items API from Microsoft Dynamics — 1 operation(s) for items.
Microsoft Dynamics Journals API
The Journals API from Microsoft Dynamics — 1 operation(s) for journals.
Microsoft Dynamics Leads API
The Leads API from Microsoft Dynamics — 2 operation(s) for leads.
Microsoft Dynamics Opportunities API
The Opportunities API from Microsoft Dynamics — 2 operation(s) for opportunities.
Microsoft Dynamics Products API
The Products API from Microsoft Dynamics — 1 operation(s) for products.
Microsoft Dynamics Purchase Invoices API
The Purchase Invoices API from Microsoft Dynamics — 1 operation(s) for purchase invoices.
Microsoft Dynamics Purchase Orders API
The Purchase Orders API from Microsoft Dynamics — 2 operation(s) for purchase orders.
Microsoft Dynamics Sales Invoices API
The Sales Invoices API from Microsoft Dynamics — 1 operation(s) for sales invoices.
Microsoft Dynamics Sales Orders API
The Sales Orders API from Microsoft Dynamics — 2 operation(s) for sales orders.
Microsoft Dynamics Vendors API
The Vendors API from Microsoft Dynamics — 2 operation(s) for vendors.
Scroll within the panel for all 19 ·
Open Collections 4
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).
Microsoft Dynamics 365 Business Central API
OPEN COLLECTIONMicrosoft Dynamics 365 / Dataverse Webhooks
OPEN COLLECTIONMicrosoft Dynamics 365 Dataverse Web API
OPEN COLLECTIONMicrosoft Dynamics 365 Finance & Operations Data API
OPEN COLLECTIONGraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
Microsoft Dynamics 365 GraphQL Schema
This conceptual GraphQL schema represents the Microsoft Dynamics 365 CRM and ERP platform, covering
GRAPHQLPricing 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 six things the Kin Score reads for commercial clarity.
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 Dynamics 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.
Semantic Vocabularies 1
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.
Microsoft Dynamics Context
JSON-LDSpectral Rules 1
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 Dynamics API Rules
SPECTRALJSON Schema 10
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 SCHEMAContact
JSON SCHEMACustomer
JSON SCHEMAEmployee
JSON SCHEMAItem
JSON SCHEMALead
JSON SCHEMAOpportunity
JSON SCHEMASales Invoice
JSON SCHEMASales Order
JSON SCHEMAVendor
JSON SCHEMAScroll within the panel for all 10 ·
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.
Resources
Every other property we hold for Microsoft Dynamics — 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 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/microsoft-dynamics · machine-readable index on apis.io