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

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 implements Dassault Systèmes sales process called 'LEVERAGE' in accordance with the VALUE Engagement framework.LEVERAGE is an acronym that stands for Listen, Explore, Validate, Establish, Reach AGreement & Experience.

Dassault Systèmes leads-opportunities API is one of 12 APIs that Dassault Systèmes publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include leads-opportunities. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 3 paths, and defines 31 schemas. It is described by OpenAPI 3.1.1, at version 0.10.0.

Requests are made against 5 base URLs: https://apigw-prd.3ds.com, https://apigw-ppt.3ds.com, https://apigw-qal.3ds.com, https://apigw-ptd.3ds.com, https://apigw-ppd.3ds.com.

4 operations 3 paths 31 schemas 1 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.1
API Version
0.10.0
Base URL
https://apigw-prd.3ds.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Dassault Systèmes leads-opportunities API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (ApiKeyAuth). By default, every request must be authenticated.

Paths & Operations 4

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

leads-opportunities 4

This section defines the operations related to leads and opportunities for sales pipeline management. These ressources are managed with 'MySalesPipeline' application which impleme…

POST
/sales/api4partners/v0/leads-opportunities
Create a lead-opportunity object
createLeadsOpportunities body → 201400401403406429503
PATCH
/sales/api4partners/v0/leads-opportunities/{id}
Update a lead-opportunity object
updateLeadOpportunitiesDetails 1 param body → 200400401403406429503
GET
/sales/api4partners/v0/leads-opportunities/{id}
Get details of a lead-opportunity object
getLeadsOpportunities 1 param → 200401403429500503
POST
/sales/api4partners/v0/leads-opportunities/search
Search for leads-opportunities
searchLeadsOpportunities body → 200400401403429503

Schemas 31

The contract defines 31 schemas that model the data the API accepts and returns. The most detailed are lead-opportunity_attributes (16 properties), customerLegalEntity (12 properties), post_leads-opportunities_data (6 properties), patch_leads-opportunities_data (6 properties). Each schema is shown below with its type and property counts.

406_leads-opportunities
object
3 properties
post_leads-opportunities_search
object
Request body schema for searching leads-opportunities
1 property 1 required
offerLine
object
One of the item within an offer.
3 properties 1 required
400_post_leads-opportunities
object
response in case of Bad Request operation
3 properties 3 required
429_too_many_requests
object
Too Many Requests
1 property 1 required
partnerContact
object
Partner contact information
3 properties 3 required
lead-opportunity_attributes
object
16 properties
403_basic_forbidden
object
Access Forbidden.
1 property 1 required
201_post_leads-opportunities
object
response in case of successful operation
5 properties 4 required
reason_won
string
Identification of the reason a lead or an opportunity is won. Note : At Creation time, if Value is Not provided, it will be defaulted to 'STRNGVALPROP' (Strong…
customerLegalEntity
object
identification of the target Customer Legal Entity
12 properties 3 required
customerContact
object
Customer Contact Information
6 properties 3 required
200_get_leads-opportunities
object
Response in case of a successful get operation on leadsOpportunities
3 properties 2 required
lead-opportunity-status
string
Status of the lead-opportunity (LEVERAGE Processs)
200_patch_leads-opportunities
object
Response in case of successful update operation on lead-Opportunities object
3 properties 2 required
lead-opportunity_patch
object
Core attributes of the lead-opportunity in case of update.
1 required
currency
string
Three-letter ISO 4217 currency code representing the transaction currency. Must be exactly 3 uppercase alphabetic characters (e.g., USD for US Dollar, EUR for…
partnerLeadOpportunityId
string
Unique Identifier of the lead-opportunity in the CRM system of the 3DS partner.
country
nullstring
Country Location
revenueType
string
The type of revenue
200_post_leads-opportunities_search
object
Response body schema for searching leads-opportunities
3 properties 2 required
reason_lost
string
A list of reason lost is used to identify the reason(s) for loss of an opportunity and for a Lead (which will give insight for the lessons learnt). Note : It i…
patch_leads-opportunities_data
object
Request body schema for updating leads-opportunities
6 properties 1 required
forecastCategory
string
Forecast Category is an assessment done by the Sales Expert to report his/her level of confidence that the Opportunity will close on the Close Date with the re…
400_patch_leads-opportunities
object
Response in case of Bad Request operation for updating leadsOpportunities object
3 properties 3 required
401_basic_unauthorized
object
Unauthorized
1 property 1 required
500_get_leads-opportunities
object
Response in case of Bad Request for retrieving lead-opportunity details
4 properties 3 required
503_leads-opportunities
object
Service Unavailable
3 properties 2 required
dsOwnerEmail
string
email of the 3DS Partner Sales Manager (PSM). Note : It is defaulted to the primary 3DS PSM if not provided at creation time.
post_leads-opportunities_data
object
request body for creating a new lead-opportunity object.
6 properties 4 required
lead-opportunity_post
object
Core attributes of the lead-opportunity in case of creation.
5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dassault-leads-opportunities-api-openapi.yml Raw ↑

Other APIs Dassault Systèmes publishes across the network.

3DEXPERIENCE Manufacturing Web Services
3DEXPERIENCE CAD Collaboration Web Services
3DEXPERIENCE Manufacturing Process Web Services
3DEXPERIENCE Project Task Web Services
3DEXPERIENCE Issue Web Services
API4Partners
Dassault Systèmes accreditations API
Dassault Systèmes apikeys API
Dassault Systèmes orders API
Dassault Systèmes portfolio-items API
Dassault Systèmes price-lists API
Where this information came from

This is an independent, third-party profile of Dassault Systèmes leads-opportunities 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.