M-Files

M-Files is a metadata-driven document and information management platform that connects documents to their business context, turning disconnected files into connected, trusted information. It provides AI-powered document management with built-in governance, workflow and document automation, and compliance, and integrates deeply with Microsoft 365. Trusted by 6,000+ organizations, M-Files exposes developer access through the M-Files Web Service (MFWS) REST API, a COM/.NET API, and the UIX and Vault Application Framework (VAF) extensibility frameworks. It was surfaced as a portfolio company of Partech.

M-Files publishes 1 API on the APIs.io network. Tagged areas include Company, Infrastructure Saas, Document Management, Information Management, and Content Services.

M-Files’ developer surface includes documentation, API reference, getting-started guide, support, engineering blog, pricing, signup flow, and 18 more developer resources.

🌐 Visit website 📡 Source on GitHub

35.6/100 thin ▬ flat Agent 3/100 human only Front door AI 5/6 prominent saas Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0

AccessSelf serve

1 APIs

Company Infrastructure Saas Document ManagementInformation ManagementContent ServicesWorkflow Automation Compliance Enterprise Content Management

Kin Score

Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0

Composite quality — 35.6/100 · thin

Contract Quality 0.0 / 21

Developer Ergonomics 10.9 / 17

Access Clarity 8.5 / 17

Operational Transparency 1.5 / 11

Contract Governance 1.9 / 10

Discoverability 5.5 / 9

Regulatory Posture 4.7 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/m-files: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 1

Individual APIs this provider publishes, each with its own machine-readable definition.

M-Files Web Service (MFWS) REST API

JSON over HTTPS REST API for the M-Files information management platform. Served per M-Files Server / Cloud vault under a /REST/ base path; supports objects, files, vaults, view...

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

M Files Authentication

oauth2/apiKey/http · 6 schemes

SECURITY

M Files Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

M Files Vulnerability Disclosure

disclosure policy published

SECURITY

M Files Trust Center

ISO/IEC 27001, SOC 2, GDPR

SECURITY

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 2

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

WellKnown

WellKnown

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Conventions

Conventions

Conformance

Conformance

Lifecycle

Lifecycle

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 7

Authentication, authorization, and security posture

TrustCenter

Compliance

Authentication

DomainSecurity

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

TrustCenter

TrustCenter

Scroll for all 7

Operate 1

Status, limits, changes, and where to get help

Support

Support

Commercial 2

Pricing, plans, and the legal terms of use

Pricing

Pricing

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: m-files
name: M-Files
description: M-Files is a metadata-driven document and information management platform that connects documents to their business
  context, turning disconnected files into connected, trusted information. It provides AI-powered document management with
  built-in governance, workflow and document automation, and compliance, and integrates deeply with Microsoft 365. Trusted
  by 6,000+ organizations, M-Files exposes developer access through the M-Files Web Service (MFWS) REST API, a COM/.NET API,
  and the UIX and Vault Application Framework (VAF) extensibility frameworks. It was surfaced as a portfolio company of Partech.
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://www.m-files.com/favicon.ico
url: https://raw.githubusercontent.com/api-evangelist/m-files/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- partech
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-20'
tags:
- Company
- Infrastructure Saas
- Document Management
- Information Management
- Content Services
- Workflow Automation
- Compliance
- Enterprise Content Management
tags_raw:
- Company
- Infrastructure Saas
- Document Management
- Information Management
- Content Services
- Workflow Automation
- Compliance
- Enterprise Content Management
- Document-Management
- Workflow-Automation
apis:
- name: M-Files Web Service (MFWS) REST API
  description: JSON over HTTPS REST API for the M-Files information management platform. Served per M-Files Server / Cloud
    vault under a /REST/ base path; supports objects, files, vaults, views, value lists, and search using standard GET/POST/PUT/DELETE
    verbs. Authenticated via an X-Authentication session token, OAuth 2.0 bearer, SSO, or pre-shared keys.
  humanURL: https://developer.m-files.com/APIs/REST-API/
  properties:
  - type: APIReference
    url: https://developer.m-files.com/APIs/REST-API/Reference/
  - type: Authentication
    url: authentication/m-files-authentication.yml
  - type: Conventions
    url: conventions/m-files-conventions.yml
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Website
  url: https://www.m-files.com/
- type: DeveloperPortal
  url: https://developer.m-files.com/
- type: Documentation
  url: https://developer.m-files.com/
- type: APIReference
  url: https://developer.m-files.com/APIs/REST-API/Reference/
- type: GettingStarted
  url: https://developer.m-files.com/Getting-Started/
- type: Support
  url: https://support.m-files.com/
- type: Blog
  url: https://www.m-files.com/blog/
- type: GitHubOrganization
  url: https://github.com/m-files
- type: Pricing
  url: https://www.m-files.com/editions/
- type: SignUp
  url: https://www.m-files.com/try-m-files/
- type: PrivacyPolicy
  url: https://www.m-files.com/privacy-policy/
- type: TrustCenter
  url: https://www.m-files.com/about/trust-center/
- type: Compliance
  url: https://www.m-files.com/about/trust-center/
- type: Packages
  url: packages/m-files-packages.yml
- type: SDKs
  url: packages/m-files-packages.yml
- type: Authentication
  url: authentication/m-files-authentication.yml
- type: Conventions
  url: conventions/m-files-conventions.yml
- type: Conformance
  url: conformance/m-files-conformance.yml
- type: Lifecycle
  url: lifecycle/m-files-lifecycle.yml
- type: DomainSecurity
  url: security/m-files-domain-security.yml
- type: VulnerabilityDisclosure
  url: security/m-files-vulnerability-disclosure.yml
- type: Security
  url: https://www.m-files.com/about/trust-center/
- type: TrustCenter
  url: security/m-files-trust-center.yml
- type: LLMsTxt
  url: llms/m-files-llms.txt
- type: WellKnown
  url: well-known/m-files-well-known.yml
x-enrichment:
  date: '2026-07-20'
  status: enriched
  artifacts_added: 10
  pass: local-v1

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/m-files"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/m-files/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/m-files/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.