ApivomApivom
Get Demo

Dassault Systèmes 3DS Partner APIs Connector

Dassault Systèmes' API Gateway for channel partners — order search and details, accreditations, price lists and product information, package offer contents, and sales leads and opportunities — registered in Apivom Atlas as 19 routes for 3DEXPERIENCE, SOLIDWORKS and CATIA resellers who want their orders and pipeline in their own CRM.

What you can do

  • Order APIs (api4partners): search orders, read order details, search the partner's accreditations
  • Catalogue: search price lists and product price lists, product information and package offer contents
  • Sales APIs: create, update, read and search leads and opportunities; search portfolio items
  • v1 endpoints for order search, order details and accreditations alongside their deprecated v0 versions; API-key generation route
  • 19 routes (8 read-only) on apigw-prd.3ds.com with a pre-production gateway, documented in the AI integration guide (llms.txt)

Use cases

  • Orders where your account managers work — Search and import orders per legal entity so every 3DEXPERIENCE or SOLIDWORKS order is visible on the customer record next to the rest of the account history.
  • Pipeline registered with the vendor — Create and update leads and opportunities at Dassault Systèmes from your own CRM, with portfolio items attached, so deal registration stops being a second data entry.
  • Quotes from the current price list — Read price lists, product information and package offer contents to build quotes on the vendor's current catalogue rather than a stale spreadsheet.

Dassault Systèmes gives its channel partners a programmatic surface through the 3DS API Gateway, split into two families. The order APIs let a partner search its orders with filters, read a single order in full, check the accreditations held by the Partner Legal Entity, and browse the commercial catalogue — price lists, the products on a price list, product information and package offer contents — plus a route to generate API keys. The sales APIs cover the partner pipeline: create, update, read and search leads and opportunities, and look up portfolio items. Each API key is bound to one Partner Legal Entity, so a multi-entity partner connects one key per entity, and Dassault Systèmes requires every integration to be validated on the pre-production gateway first. Apivom Atlas catalogues all 19 routes, 8 read-only, with the credential contract and the AI integration guide (llms.txt), and logs each call per tenant. No Apivom product workflow calls these APIs today — Apivom's current 3DEXPERIENCE automation for partners works on the DSx.Client Care & Order portal through Apivom Staff — so an order or pipeline sync on this connector is scoped per customer.

Authentication

Your 3DS API Gateway key — Dassault Systèmes issues one per Partner Legal Entity — sent as the X-API-Key header on every call; validate on the pre-production gateway (apigw-ppt) first. Stored keys are encrypted in your Iris tenant; Apivom Atlas forwards, logs and stores nothing.

Frequently asked questions

Can I switch this connector on today?

The connector is registered in Apivom Atlas — every route is catalogued, the credential contract is published and the AI integration guide (llms.txt) is live — and your credential can be stored in Apivom Iris. Wiring it into a product workflow (sync, automation, notifications) is done per customer: tell us the use case and we scope it with you.

Why does my company need more than one API key?

Dassault Systèmes issues one key per Partner Legal Entity, so a partner with several legal entities connects one key for each; a leaked key is then limited to a single entity's data. Apivom stores each key against the entity it belongs to.

What is the pre-production gateway for?

apigw-ppt.3ds.com is the integration-validation environment Dassault Systèmes requires before any activity on production (apigw-prd.3ds.com). The connector supports both, so a tenant validates on PPT first and switches the environment afterwards.

Does the connector place or cancel orders?

No. The order APIs are read-only (search orders, order details, accreditations, catalogue); the writes in this connector are on the sales side — leads and opportunities — and on key generation.

Does Apivom charge per API call for this connector?

No. Connectors are part of your Apivom tenant and are not metered in the Atlas portal. The vendor's own pricing, quotas and rate limits still apply to the account you connect — Apivom paces its calls to stay inside them and shows every call in your tenant's integration log.

Where are my credentials stored and who can see the traffic?

Apivom Atlas is a stateless gateway: it never stores vendor credentials or tokens. The Apivom product that connects keeps the credential encrypted in your tenant database, and every request and response is logged in your tenant only — your data is never shared across tenants.

More Atlas integrations

AI integration guide (llms.txt)

Machine-readable markdown — feed it to your AI assistant as integration instructions.