Dassault Systèmes
Dassault Systèmes provides the 3DEXPERIENCE platform with thousands of publicly available REST APIs for product design, simulation, and manufacturing industries. The platform covers SolidWorks, CATIA, ENOVIA, and 3D collaboration tools, exposing web services across engineering items, manufacturing processes, CAD collaboration, project tasks, and partner order management through standardized RESTful endpoints.
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 Dassault Systèmes the way a machine reads it — 168 machine-readable artifacts across 12 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 — Dassault Systèmes scores 54.1/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 Dassault Systèmes
Each block below is one kind of artifact we hold for Dassault Systèmes. 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.
3DEXPERIENCE Manufacturing Web Services
REST API for managing manufacturing item data, manufacturing BOMs, and process plans on the 3DEXPERIENCE platform used in production and factory planning.
3DEXPERIENCE CAD Collaboration Web Services
REST API for CAD collaboration and coordination on the 3DEXPERIENCE platform, enabling integration with SolidWorks, CATIA, and other CAD tools for managing design data and versi...
3DEXPERIENCE Manufacturing Process Web Services
REST API for managing manufacturing processes, process plans, and operations on the 3DEXPERIENCE platform, supporting digital manufacturing and process simulation workflows.
3DEXPERIENCE Project Task Web Services
REST API for project management and task handling on the 3DEXPERIENCE platform, enabling integration with project schedules, milestones, and team assignments within ENOVIA appli...
3DEXPERIENCE Issue Web Services
REST API for change and issue tracking on the 3DEXPERIENCE platform, supporting engineering change orders, problem reports, and corrective actions within the product lifecycle.
API4Partners
REST API for Dassault Systèmes channel partners to manage orders, price lists, accreditations, leads, and portfolio items through the partner gateway, using API key authentication.
Dassault Systèmes accreditations API
This section defines all the operations related to accreditations, including the search of accreditations for a specfic partner.
Dassault Systèmes apikeys API
This section defines the operations related to API keys . Current API key management still requires some interaction with Dassault Systèmes Information System (IS) team. This pr...
Dassault Systèmes leads-opportunities API
This section defines the operations related to leads and opportunities for sales pipeline management. These ressources are managed with 'MySalesPipeline' application which imple...
Dassault Systèmes orders API
This section defines the operations related to orders, including the creation, management, and fulfillment of orders. It provides a comprehensive overview of the order lifecycle...
Dassault Systèmes portfolio-items API
This section defines the operations related to sales portfolio-items. The portfolio items are used in the definition of leads-opportunities in 'MySalesPipeline' application.
Dassault Systèmes price-lists API
This section defines all the operations related to price lists, including the search of price lists for a specfic partner.
Scroll within the panel for all 12 ·
Pricing 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.
Dassault 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.
Dassault Finops
FINOPSSemantic 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.
Dassault Api Context
JSON-LDDassault 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.
Dassault Systèmes API Rules
SPECTRALJSON Schema 77
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.
200 Accreditations Search
JSON SCHEMA200 Get Leads Opportunities
JSON SCHEMA200 Get Orders
JSON SCHEMA200 Get Portfolio Items Search
JSON SCHEMA200 Patch Leads Opportunities
JSON SCHEMA200 Post Apikeys
JSON SCHEMA200 Post Leads Opportunities Search
JSON SCHEMA200 Post Orders Search
JSON SCHEMA200 Price Lists Search
JSON SCHEMA201 Post Leads Opportunities
JSON SCHEMA400 Accreditations Search
JSON SCHEMA400 Get Portfolio Items Search
JSON SCHEMA400 Patch Leads Opportunities
JSON SCHEMA400 Post Leads Opportunities
JSON SCHEMA400 Post Orders Search
JSON SCHEMA401 Basic Unauthorized
JSON SCHEMA403 Basic Forbidden
JSON SCHEMA406 Leads Opportunities
JSON SCHEMA429 Too Many Requests
JSON SCHEMA4Xx Get Orders
JSON SCHEMA500 Get Leads Opportunities
JSON SCHEMA503 Leads Opportunities
JSON SCHEMAAccreditations Search Data
JSON SCHEMABillto Po Reference
JSON SCHEMABillto Sales Representative
JSON SCHEMABooking Datetime
JSON SCHEMABusiness Unit
JSON SCHEMACountry
JSON SCHEMACountry Code
JSON SCHEMACountry Name
JSON SCHEMACreation Datetime
JSON SCHEMACurrency
JSON SCHEMACustomercontact
JSON SCHEMACustomerlegalentity
JSON SCHEMADate Time From
JSON SCHEMADate Time To
JSON SCHEMADsowneremail
JSON SCHEMADs Offering
JSON SCHEMADs Received Po Date
JSON SCHEMAError
JSON SCHEMAForecastcategory
JSON SCHEMAInfo
JSON SCHEMAInfo Response Base Attributes
JSON SCHEMAInfo Response Portfolio Items
JSON SCHEMAInstalled Base Number
JSON SCHEMALead Opportunity Status
JSON SCHEMALead Opportunity Attributes
JSON SCHEMALead Opportunity Patch
JSON SCHEMALead Opportunity Post
JSON SCHEMALegal Entity
JSON SCHEMALocal Time Zone
JSON SCHEMAOfferline
JSON SCHEMAOnline Consent Status
JSON SCHEMAOnline Instance Seat Id
JSON SCHEMAOrder Get Data
JSON SCHEMAOrder Line
JSON SCHEMAOrder Processing Status
JSON SCHEMAOrder Revenue Type
JSON SCHEMAOrder Sub Line
JSON SCHEMAOrder Type
JSON SCHEMAOrders Search Data
JSON SCHEMAOrders Search Req
JSON SCHEMAPartnercontact
JSON SCHEMAPartnerleadopportunityid
JSON SCHEMAPatch Leads Opportunities Data
JSON SCHEMAPortfolio Items Data
JSON SCHEMAPost Leads Opportunities Data
JSON SCHEMAPost Leads Opportunities Search
JSON SCHEMAPrice Lists Search Data
JSON SCHEMAProduct Type
JSON SCHEMAReason Lost
JSON SCHEMAReason Won
JSON SCHEMARecurring Charge Billing Cycle
JSON SCHEMARevenuetype
JSON SCHEMASub Order Type
JSON SCHEMATransaction
JSON SCHEMATransaction Type
JSON SCHEMAScroll within the panel for all 77 ·
Examples 69
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 69 ·
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.
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 Dassault Systèmes — 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.
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 3
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 3
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/dassault · machine-readable index on apis.io