Dassault Systèmes · Schema

Lead Opportunity Attributes

3DEXPERIENCEPLMProduct Lifecycle ManagementCADManufacturingSolidWorksCATIAENOVIAEngineering3D Collaboration

Properties

Name Type Description
partnerLeadOpportunityId object
name string Name assigned to the lead-opportunity
dsOwnerEmail object
status object
forecastCategory object
closeDate string Expected date for the closing of the sale in ISO 8601 format (like YYYY-MM-DDThh:mm:ss.sssZ)
cometCampaignCode string COMET Campaign code
reasonWon array 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 `STRNG_VAL_PROP` (Stronger value proposition).
reasonLost array 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_ : At creation time, if value is not provided,
competitors array List of the competitors. In current state of the API, the list of valid values will be provided through direct communication with partners (mail or 3DSwym discussion).
reasonWonLostComment string Comment associated to WON or LOST reasons
gtmTacticId string identification of GoToMarket.
description string description associated to the lead-opportunity
nextMilestone string Description of the next activity to be done
nextMilestoneDate string Next Milestone date in ISO 8601 format (like YYYY-MM-DDThh:mm:ss.sssZ)
currency object
View JSON Schema on GitHub

JSON Schema

lead-opportunity_attributes.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://api-evangelist.github.io/dassault/json-schema/lead-opportunity_attributes.json",
  "title": "Lead Opportunity Attributes",
  "type": "object",
  "properties": {
    "partnerLeadOpportunityId": {
      "$ref": "#/components/schemas/partnerLeadOpportunityId"
    },
    "name": {
      "type": "string",
      "description": "Name assigned to the lead-opportunity",
      "example": "Projekt Big-Picture Topic + MBSE (STEP 1+2)"
    },
    "dsOwnerEmail": {
      "$ref": "#/components/schemas/dsOwnerEmail"
    },
    "status": {
      "$ref": "#/components/schemas/lead-opportunity-status",
      "example": "LEAD_OPEN"
    },
    "forecastCategory": {
      "$ref": "#/components/schemas/forecastCategory",
      "example": "UPSIDE"
    },
    "closeDate": {
      "type": "string",
      "format": "date-time",
      "description": "Expected date for the closing of the sale in ISO 8601 format (like YYYY-MM-DDThh:mm:ss.sssZ)",
      "example": "2025-08-01T18:03:16.325Z"
    },
    "cometCampaignCode": {
      "type": "string",
      "description": "COMET Campaign code",
      "example": "OC2DE17TAQ1C13018"
    },
    "reasonWon": {
      "type": "array",
      "description": "\nIdentification of the reason a lead or an opportunity is won.\n\n_Note_ : At creation time, if value is not provided, it will be defaulted to `STRNG_VAL_PROP` (Stronger value proposition).",
      "items": {
        "$ref": "#/components/schemas/reason_won"
      }
    },
    "reasonLost": {
      "type": "array",
      "description": "\nA 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).\n\n_Note_ : At creation time, if value is not provided, it will be defaulted to `NO_PROJECT`.",
      "items": {
        "$ref": "#/components/schemas/reason_lost"
      }
    },
    "competitors": {
      "type": "array",
      "description": "List of the competitors. \nIn current state of the API, the list of valid values will be provided through direct communication with partners (mail or 3DSwym discussion). \n",
      "items": {
        "type": "string"
      }
    },
    "reasonWonLostComment": {
      "type": "string",
      "description": "Comment associated to WON or LOST reasons",
      "example": "The Customer has no budget"
    },
    "gtmTacticId": {
      "type": "string",
      "description": "identification of GoToMarket."
    },
    "description": {
      "type": "string",
      "description": "description associated to the lead-opportunity",
      "example": "Projekt Dashboard - Big-Picture TopicPilotprojekt"
    },
    "nextMilestone": {
      "type": "string",
      "description": "Description of the next activity to be done",
      "example": "Next activity is to make a demo to the Customer"
    },
    "nextMilestoneDate": {
      "type": "string",
      "format": "date-time",
      "description": "Next Milestone date in ISO 8601 format (like YYYY-MM-DDThh:mm:ss.sssZ)",
      "example": "2025-08-01T18:03:16.325Z"
    },
    "currency": {
      "$ref": "#/components/schemas/currency"
    }
  }
}

Work with this as data

Every JSON Schema 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 schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • 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 JSON Schema
curl "https://apis.io/api/v1/json-schemas/lead-opportunity_attributes"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

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.

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