Request

Response

    Create Translation Job
    POST

    job

    Creates a job to translate the specified source design from one format to another, generating derivatives of the source design. You can optionally:

    • Extract selected parts of a design and export the set of geometries to the OBJ format.
    • Generate different-sized thumbnails.

    Follow the step-by-step tutorials for detailed instructions on how to use this operation to translate files, extract geometries, and generate thumbnails.

    When the translation job runs, progress information and details of the generated derivatives are logged to a JSON file that is called a manifest. A manifest is typically created the first time you translate the source design. Thereafter the system updates the same manifest each time a translation job is executed for that source design. If necessary, you can set the x-ads-force header to true, which deletes the existing manifest and creates a fresh manifest. However, if you do so, all derivatives generated prior to this are deleted.

    A translation job is asynchronous and runs as a background process. There is no need not keep the HTTP connection open until the job completes. Use Fetch Manifest to check for the job’s completion status.

    Resource Information

    Method and URI
    POST
    https://developer.api.autodesk.com/modelderivative/v2/designdata/job
    Method and URI (EMEA)
    POST
    https://developer.api.autodesk.com/modelderivative/v2/regions/eu/designdata/job
    Authentication Context
    user context optional
    Required OAuth Scopes
    data:read and (data:write or data:create)
    Data Format
    JSON
    Rate Limit
    500 calls per minute

    Request

    Headers

    Authorization*
    string
    Must be Bearer <token>, where <token> is obtained via POST /authentication/v2/token
    Content-Type*
    string
    Must be application/json
    region
    enum:string
    Specifies where to store the manifest and derivatives. Possible values are:
    • US : (Default) Data center for the US region.
    • EMEA : Data center for the European Union, Middle East, and Africa regions.
    • AUS : (Beta) Data centre for the Australia region.

    Note:

    • Beta features are subject to change. Please avoid using them in production environments.
    • The Model Derivative service ignores this parameter if you use the EMEA URI for this operation.
    • Calling this operation twice for the same source design with different values for this parameter creates two distinct sets of manifests and derivatives. See GDPR Compliance for more information.
    x-ads-force
    bool
    • true: Deletes the existing manifest and derivatives of the source design before translation.
    • false: (Default) Updates existing manifest and generates derivatives only for the formats that the source design has no derivatives.
    x-ads-derivative-format
    enum:string
    Specifies how to interpret the formats.advanced.objectIds request body attribute for OBJ output. Possible values are:
    • latest: (Default) Consider formats.advanced.objectIds to be SVF2 Object IDs.
    • fallback: Consider formats.advanced.objectIds to be SVF Object IDs.

    Note

    1. This parameter applies only to designs with legacy SVF derivatives generated by the BIM 360 Docs service.
    2. The BIM 360 Docs service now generates SVF2 derivatives. SVF2 Object IDs may not be compatible with the SVF Object IDs previously generated by the BIM 360 Docs service. Setting this header to fallback may resolve backward compatibility issues resulting from Object IDs of legacy SVF derivatives being retained on the client side.
    3. If you use this header with one derivative (URN), you must use it consistently across the following operations for that derivative.

    * Required

    Request

    Body Structure

    Attributes that Apply to All Outputs

    Expand all
    input*
    object
    An object describing the attributes of the source design.
    urn*
    string
    The URL safe Base64 encoded URN of the source design.

    Note: The URN is returned as the objectID once you complete uploading the source design to APS. This value must be converted to a Base64 (URL Safe) encoded string before you can specify it for this attribute.
    compressedUrn
    bool
    • true: The source design is compressed as a zip file. The design can consist of a single file or as in the case of Autodesk Inventor, multiple files. If set to true, you must specify the rootFilename attribute.
    • false: (Default) The source design is not compressed.
    rootFilename
    string
    The file name of the top-level component of the source design. Mandatory if compressedUrn is set to true.
    checkReferences
    bool
    • true: Instructs the server to check for references and download all referenced files. If the design consists of multiple files (as with Autodesk Inventor assemblies) the translation job fails if this attribute is not set to true.
    • false: (Default) Does not check for any references.

    Set this attribute to true if the design specified by the input.urn attribute contains references (for example, an Inventor assembly file). Refer to the tutorial Translate a Source File that Contains References for an example usage of this attribute.

    output*
    object
    An object describing the attributes of the requested derivatives.
    destination
    object
    DEPRECATED Group of destination settings.

    Note: This attribute is replaced by the region header.

    region
    string
    DEPRECATED Region in which to store outputs. Use the region header to specify what region to store outputs.

    Note: This attribute is replaced by the region header.

    formats*
    array: object
    Group of requested formats/types. User can request multiple formats.
    type*
    string
    The requested output types. Possible values: dwg, fbx, ifc, iges, obj, step, stl, svf, svf2, thumbnail. For a list of supported types, call the List Supported Formats operation.
    misc
    object
    Group of misc parameters
    workflow
    string
    The workflow id created for a webhook, used to listen to Model Derivative events. It needs to be no more than 36 chars, and only ASCII, decimal and hyphen are accepted.

    Refer to the tutorial Creating a Webhook and Listening to Events for details.

    workflowAttribute
    object
    A user-defined JSON object, which you can use to set some custom workflow information. It needs to be less than 1KB and will be ignored if misc.workflow parameter is not set.
    * Required

    Attributes that Apply to SVF or SVF2 Outputs

    Case 1 - Input file type is not RVT, IFC, NWD, or VUE:

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Valid values are:
    • svf - for the SVF output type.
    • svf2 - for the SVF2 output type.
    views*
    array: string
    Possible values: 2d, 3d
    * Required

    Case 2 - Input file type is DGN:

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Valid values are:
    • svf - for the SVF output type.
    • svf2 - for the SVF2 output type.
    views*
    array:string
    Possible values: 2d, 3d
    advanced
    object
    A set of special options applicable when the input file type is DGN.
    requestedLinkageIDs
    array:integer
    An array containing user data linkage IDs of the linkage data to be extracted from the DGN file. Linkage data is not extracted if you do not specify this attribute.
    * Required

    Case 3 - Input file type is DWG:

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Valid values are:
    • svf - for the SVF output type.
    • svf2 - for the SVF2 output type.
    views*
    array: string
    Possible values: 2d, 3d
    advanced
    object
    A set of special options applicable when the input file type is DWG.
    2dviews
    enum: string
    The format that 2D views must be rendered to. Available options are:
    • legacy - (Default) Render to a model derivative specific file format.
    • pdf - Render to the PDF file format. If you choose this option, only properties with semantic values are extracted from the DWG file.
    * Required

    Case 4 - Input file type is IFC:

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Valid values are:
    • svf - for the SVF output type.
    • svf2 - for the SVF2 output type.
    views*
    array: string
    Possible values: 2d, 3d
    advanced
    object
    A set of special options applicable when the input file type is IFC.
    switchLoader
    bool
    DEPRECATED Switches the IFC loader from the Navisworks IFC loader to the new Revit IFC loader, when translating from the IFC input format to SVF. This attribute defaults to false.
    conversionMethod
    string
    Specifies the IFC loader to use during translation. Available options are:
    • legacy - Use IFC loader version 1, which is based on the Navisworks IFC loader. Supports IFC 2x3.
    • modern - Use IFC loader version 2, which is based on the Revit IFC loader. Supports IFC 2x3 and IFC 4.
    • v3 - Use IFC loader version 3, which is based on the Revit IFC loader. Supports IFC 2x3, IFC 4, and IFC 4.3.
    • v4 - (Recommended) Use IFC loader version 4, which is a native solution specifically designed for Autodesk Platform Services (APS). It does not depend on Navisworks or Revit. Supports IFC 2x3, IFC 4, and IFC 4.3.

    If both switchLoader and conversionMethod are specified, Model Derivative uses the conversionMethod parameter. If conversionMethod is not specified, Model Derivative uses the switchLoader parameter.

    buildingStoreys
    string
    Specifies how storeys are translated. Available options are:
    • hide - (Default) storeys are extracted but not visible by default.
    • show - storeys are extracted and are visible by default.
    • skip - storeys are not translated.

    Note These options do not apply when conversionMethod is set to legacy.

    spaces
    string
    Specifies how spaces are translated. Available options are:
    • hide - (Default) spaces are translated but are not visible by default.
    • show - spaces are translated and are visible by default.
    • skip - spaces are not translated.

    Note These options do not apply when conversionMethod is set to legacy.

    openingElements
    string
    An option to be specified when the input file type is IFC. Specifies how openings are translated. Available options are:
    • hide - (Default) openings are translated but are not visible by default.
    • show - openings are translated and are visible by default.
    • skip - openings are not translated.

    Note These options do not apply when conversionMethod is set to legacy.

    * Required

    Case 5 - Input file type is NWD:

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Valid values are:
    • svf - for the SVF output type.
    • svf2 - for the SVF2 output type.
    views*
    array: string
    Possible values: 2d, 3d
    advanced
    object
    A set of special options applicable when the input file type is Navisworks.
    hiddenObjects
    bool
    Specifies whether hidden objects must be extracted or not.
    • true: Extract hidden objects from the input file.
    • false: (Default) Do not extract hidden objects from the input file.
    basicMaterialProperties
    bool
    Specifies whether basic material properties must be extracted or not.
    • true: Extract properties for basic materials.
    • false: (Default) Do not extract properties for basic materials.
    autodeskMaterialProperties
    bool
    Specifies how to handle Autodesk material properties.
    • true: Extract properties for Autodesk materials.
    • false: (Default) Do not extract properties for Autodesk materials.
    timelinerProperties
    bool
    Specifies whether timeliner properties must be extracted or not.
    • true: Extract timeliner properties.
    • false: (Default) Do not extract timeliner properties.
    * Required

    Case 6 - Input file type is RVT:

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Valid values are:
    • svf - for the SVF output type.
    • svf2 - for the SVF2 output type.
    views*
    array: string
    Possible values: 2d, 3d
    advanced
    object
    A set of special options applicable when the input file type is Revit.
    2dviews
    enum: string
    The format that 2D views must be rendered to. Available options are:
    • legacy - (Default) Render to a model derivative specific file format.
    • pdf - Render to the PDF file format. This option applies only to Revit 2022 files and newer.
    extractorVersion
    enum: string
    Specifies what version of the Revit translator/extractor to use. Possible values:
    • next - Makes the translation job use the newest available version of the translator/extractor. This option is meant to be used by beta testers who wish to test a pre-release version of the translator. If no pre-release version is available, this option makes the translation job use the current official release version.
    • previous - Makes the translation job use the previous official release version of the translator/extractor. This option is meant to be used as a workaround in case of regressions caused by a new official release of the translator/extractor.

    If this attribute is not specified, the system uses the current official release version.

    generateMasterViews
    bool
    Generates master views when translating from the Revit input format to SVF. This option is ignored for all other input formats. This attribute defaults to false.

    Master views are 3D views that are generated for each phase of the Revit model. A master view contains all elements (including “room” elements) present in the host model for that phase. The display name of a master view defaults to the name of the phase it is generated from. However, if a view with that name already exists, the Model Derivative service appends a suffix to the default display name.

    Notes:

    1. Master views do not contain elements from linked models.
    2. Enabling this option can increase the time it takes to translate the model.
    materialMode
    string
    Specifies the materials settings to apply to the generated derivatives. Available options are:
    • auto - (Default) Use the current setting of the default view of the input file.
    • basic - Use basic materials.
    • autodesk - Use Autodesk materials.
    * Required

    Case 7 - Input file type is VUE:

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Valid values are:
    • svf - for the SVF output type.
    • svf2 - for the SVF2 output type.
    views*
    array: string
    Possible values: 2d, 3d
    advanced
    object
    A set of special options applicable when the input file type is VUE.
    hierarchy
    enum
    Specifies how the hierarchy of items are determined.
    • Classic: (Default) Uses hardcoded rules to set the hierarchy of items.
    • SystemPath: Uses a linked XML or MDB2 properties file to set hierarchy of items. You can use this option to make the organization of items consistent with SmartPlant 3D.

    Notes:

    1. The functioning of the SystemPath depends on the default setting of the property SP3D_SystemPath or System Path.
    2. The pathing delimiter must be \.
    3. If you want to customize further, import the VUE file to Navisworks. After that, use POST job on the resulting Navisworks (nwc/nwd) file.
    * Required

    Attributes that Apply to Thumbnail Outputs

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Must be thumbnail for the thumbnail output type.
    advanced
    object
    Advanced options for thumbnail type.
    width
    int
    Set the width. Possible values: 100, 200, 400
    height
    int
    Set the height. Possible values: 100, 200, 400
    * Required

    Attributes that Apply to STL Outputs

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Must be stl for the STL output type.
    advanced
    object
    Advanced options for stl output type.
    format
    string
    Default format is binary. Possible values: binary, ascii
    exportColor
    bool
    Color is exported by default. If set to true, color is exported. If set to false, color is not exported.
    exportFileStructure
    enum: string
    • single (Default): creates one STL file for all the input files (assembly file).
    • multiple: creates a separate STL file for each object.
    * Required

    Attributes that Apply to STEP Outputs

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Must be step for the STEP output type.
    advanced
    object
    Advanced options for step output type.
    applicationProtocol
    string
    A STEP file can be generated with the following application protocols:
    • 203 for configuration controlled design,
    • 214 for core data for automotive mechanical design processes,
    • 242 for managed model based 3D engineering.

    By default, 214 will be exported.

    tolerance
    float
    Possible values: between 0 and 1. By default it is set at 0.001.
    * Required

    Attributes that Apply to IGES Outputs

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Must be iges for the IGES output type.
    advanced
    object
    Advanced options for iges output type.
    tolerance
    float
    Possible values: between 0 and 1. By default it is set at 0.001.
    surfaceType
    string
    Possible values: bounded, trimmed, wireframe. By default it is set to bounded surface.
    sheetType
    string
    Export the sheet body to IGES open, shell, surface or wireframe. By default, it is set to surface.
    solidType
    string
    Export the solid body to IGES solid, surface or wireframe. By default, it is set to solid.
    * Required

    Attributes that Apply to OBJ Outputs

    Expand all
    formats*
    object
    A JSON object representing the requested output. types.
    type*
    string
    The requested output type. Must be obj for the OBJ output type.
    advanced
    object
    Advanced options for obj output type.
    exportFileStructure
    enum:string
    Ignored for geometry extraction.
    • single (default): creates one OBJ file for all the input files (assembly file).
    • multiple: creates a separate OBJ file for each input file.
    unit
    enum:string
    Translate models into different units; this causes the values to change. For example, from millimeters (10, 123, 31) to centimeters (1.0, 12.3, 3.1). If the source unit or the unit you are translating into is not supported, the values remain unchanged. Possible values:
    • meter, decimeter, centimeter, millimeter, micrometer, nanometer
    • yard, foot, inch, mil, microinch

    Note that this feature does not support F3D files.

    modelGuid
    string
    Required for geometry extraction. The model view ID (guid). Currently only valid for 3d views.
    objectIds
    array: int
    Required for geometry extraction. List object ids to be translated. -1 will extract the entire model. Currently only valid for 3d views.
    * Required

    Attributes that Apply to DWG Outputs

    Note that when translating RVT to DWG, it only translates the selected 2D views of the model. You can choose which of the 2D views you need to translate (to DWG) through the Revit addon Publish Settings. If nothing selected, all sheet views (if any) would be translated by default.

    Expand all
    formats*
    object
    A JSON object representing the requested output types.
    type*
    string
    The requested output type. Must be dwg for the DWG output type.
    advanced
    object
    Advanced options for dwg output type.
    exportSettingName
    string
    The export settings should be one of the DWG Export settings name pre-saved in the document.

    If the string is invalid, or the specified settings name is not found in the document, one of the following would be used according to the following priority.

    1. The active settings in the document retrieved by Revit API public static ExportDWGSettings GetActivePredefinedSettings(Document aDoc) on the document. The active settings are the settings selected in the Modify DWG Export dialog and saved in the document.
    2. The default settings, which are the values set by default when a Revit API object is created from the class DWGExportOptions.

      • Revit API public static IList<string> ListNames(Document aDoc): Returns a list of names of all the pre-defined DWG export settings in the document.
      • Revit API public static ExportDWGSettings FindByName(Document aDoc, string name): Returns the pre-defined non-in-session exporting settings for DWG in the given document with the specified name.

    Please refer to Export to DWG or DXF and Revit API Developers Guide in Revit help for details.

    * Required

    Attributes that Apply to IFC Outputs

    Note that when translating RVT to IFC, it does not matter whether or not there is a 3D view in the model. All the elements in the model would be translated to IFC.

    Expand all
    formats*
    object
    A JSON object representing the requested output.
    type*
    string
    The requested output type. Must be ifc for the IFC output type.
    advanced
    object
    Advanced options for ifc output type.
    exportSettingName
    string
    The export settings should be one of the IFC Export settings pre-saved in the document.
    If the string is invalid, or the specified settings are not found in the document, the system will use the default settings. The default settings are obtained by creating a Revit API object from the class IFCExportOptions.
    The list of settings pre-saved in the document can be accessed from Revit dialog ‘Export IFC’. But there is currently no Revit API for getting this data from the document.
    * Required

    Response

    HTTP Status Code Summary

    200
    OK
    Success. Note that you still need to check whether the asynchronous job is complete by calling the Fetch Manifest operation.
    201
    CREATED
    The requested file type has been previously generated and has not been replaced by the new source file.
    400
    BAD REQUEST
    Invalid request. E.g., the input URN format is invalid.
    401
    UNAUTHORIZED
    Invalid authorization header.
    403
    FORBIDDEN
    Access denied regardless of authorization status.
    404
    NOT FOUND
    Endpoint does not exist.
    406
    NOT ACCEPTABLE
    The request is not acceptable. E.g., the output type is not supported.
    409
    CONFLICT
    The request conflicts with a previous request that is still in progress.
    429
    TOO MANY REQUEST
    Rate limit exceeded (500 requests per minute); wait some time before retrying.
    500
    INTERNAL SERVICE ERROR
    Unexpected service interruption.

    Response

    HTTP Headers

    x-ads-app-identifier
    string
    The service identifier comprise service name, version and environment.
    x-ads-startup-time
    string
    The service startup time with data format EEE MMM dd HH:mm:ss Z yyyy.
    x-ads-duration
    string
    The request duration in milliseconds.

    Response

    Body Structure (200/201)

    result
    string
    reporting success status
    urn
    string
    the urn identifier of the source file
    acceptedJobs
    array: object
    list of the requested outputs
    output
    array: object
    identical to the request body. For more information please see the request body structure above.

    Response

    Body Structure (400)

    diagnostics
    string
    reason for failure

    Example 1

    A successful attempt kicking off a job for the translation of an Inventor model to SVF2, where the source files are packaged as a single zip file (200).

    Note: This request does not explicitly specify a region header. So, the system assumes the default region, which is US.

    Request

    curl -X 'POST' \
         -H 'Content-Type: application/json; charset=utf-8' \
         -H 'Authorization: Bearer PtnrvrtSRpWwUi3407QhgvqdUVKL'
         -v 'https://developer.api.autodesk.com/modelderivative/v2/designdata/job' \
         -d
          '{
             "input": {
               "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6bW9kZWxkZXJpdmF0aXZlL0E1LnppcA",
               "compressedUrn": true,
               "rootFilename": "A5.iam"
             },
             "output": {
               "formats": [
                 {
                   "type": "svf2",
                   "views": [
                     "2d",
                     "3d"
                   ]
                 }
               ]
             }
           }'
    
    Show More

    Response

    Status Code: 200 OK
    Content-Type:application/json;charset=utf-8
    Access-Control-Allow-Credentials:true
    Access-Control-Allow-Origin:*
    x-ads-app-identifier:platform-viewing-2016.05.03.1102.2f6bfbf-production
    x-ads-startup-time:Wed May 11 14:03:54 CST 2016
    x-ads-duration:280 ms
    
    {
      "result": "success",
      "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6bW9kZWxkZXJpdmF0aXZlL0E1LnppcA",
      "acceptedJobs": {
        "output": {
          "formats": [
            {
              "type": "svf2",
              "views": [
                "2d",
                "3d"
              ]
            }
          ]
        }
      }
    }
    
    Show More

    Example 2

    A successful attempt kicking off a job for the translation of an Inventor part file to SVF2. The derivatives are to be stored in the in the EMEA region.

    Request

    curl -X 'POST' \
         -H 'Content-Type: application/json; charset=utf-8' \
         -H 'Authorization: Bearer PtnrvrtSRpWwUi3407QhgvqdUVKL...' \
         -H 'region: EMEA' \
         -v 'https://developer.api.autodesk.com/modelderivative/v2/designdata/job' \
         -d '{
                 "input": {
                     "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6anBfZW1lYV9idWNrZXQvYm94LmlwdA=="
                 },
                 "output": {
                     "formats": [
                         {
                             "type": "svf2",
                             "views": [
                                 "2d",
                                 "3d"
                             ]
                         }
                     ]
                 }
             }'
    
    Show More

    Response

    Status Code: 200 OK
    Content-Type:application/json;charset=utf-8
    Access-Control-Allow-Credentials:true
    Access-Control-Allow-Origin:*
    x-ads-app-identifier:platform-viewing-2023.11.01.52.7902cdefa-production
    x-ads-startup-time:Mon Nov 27 04:47:37 UTC 2023
    x-ads-duration:1083 ms
    
    {
        "result": "success",
        "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6anBfZW1lYV9idWNrZXQvYm94LmlwdA",
        "acceptedJobs": {
            "output": {
                "formats": [
                    {
                        "type": "svf2",
                        "views": [
                            "2d",
                            "3d"
                        ]
                ]
            }
        }
    }
    
    Show More

    Example 3

    Illustrates what happens when you kick off a job for a source file that was translated previously (201).

    Request

    curl -X 'POST' \
         -H 'Content-Type: application/json; charset=utf-8' \
         -H 'Authorization: Bearer PtnrvrtSRpWwUi3407QhgvqdUVKL' \
         -H 'x-ads-force: false' -v 'https://developer.api.autodesk.com/modelderivative/v2/designdata/job' \
         -H 'region: US' \
         -d '{
               "input": {
                 "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6bW9kZWxkZXJpdmF0aXZlL0E1LnppcA",
                 "compressedUrn": true,
                 "rootFilename": "A5.iam"
               },
               "output": {
                 "formats": [
                   {
                     "type": "svf2",
                     "views": [
                       "2d",
                       "3d"
                     ]
                   }
                 ]
               }
             }'
    
    Show More

    Response

    Status Code: 201 Created
    Content-Type:application/json;charset=utf-8
    Access-Control-Allow-Credentials:true
    Access-Control-Allow-Origin:*
    x-ads-app-identifier:platform-viewing-2016.05.03.1102.2f6bfbf-production
    x-ads-startup-time:Wed May 11 14:03:54 CST 2016
    x-ads-duration:280 ms
    
    {
      "result": "created",
      "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6bW9kZWxkZXJpdmF0aXZlL0E1LnppcA",
      "acceptedJobs": {
          "formats": [
            {
              "type": "svf2",
              "views": [
                "2d",
                "3d"
              ]
            }
          ]
        }
      }
    }
    
    Show More

    Example 4

    A successful attempt at starting a job to export geometry corresponding to the specified object ids to the OBJ format (200).

    Request

    curl -X 'POST' \
         -H 'Content-Type: application/json; charset=utf-8' \
         -H 'Authorization: Bearer PtnrvrtSRpWwUi3407QhgvqdUVKL' \
         -v 'https://developer.api.autodesk.com/modelderivative/v2/designdata/job' \
         -d
    '{
       "input": {
         "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6bW9kZWxkZXJpdmF0aXZlL0E1LnppcA"
       },
       "output": {
         "formats": [
           {
             "type": "obj",
             "advanced": {
               "modelGuid": "4f981e94-8241-4eaf-b08b-cd337c6b8b1f",
               "objectIds": [
                 2,
                 3,
                 4
               ]
             }
           }
         ]
       }
     }'
    
    Show More

    Response

    Status Code: 200 OK
    Content-Type:application/json;charset=utf-8
    Access-Control-Allow-Credentials:true
    Access-Control-Allow-Origin:*
    x-ads-app-identifier:platform-viewing-2016.05.03.1102.2f6bfbf-production
    x-ads-startup-time:Wed May 11 14:03:54 CST 2016
    x-ads-duration:280 ms
    
    {
      "result": "success",
      "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6bW9kZWxkZXJpdmF0aXZlL0E1LnppcA",
      "acceptedJobs": {
        "output": {
          "destination": {
            "region": "us"
          },
          "formats": [
            {
              "type": "obj",
              "advanced": {
                "modelGuid": "4f981e94-8241-4eaf-b08b-cd337c6b8b1f",
                "objectIds": [
                  2,
                  3,
                  4
                ]
              }
            }
          ]
        }
      }
    }
    
    Show More

    Example 5

    A failed attempt to start a job for extracting geometry. The job request failed because the specified object ids are invalid (400).

    Request

    curl -X 'POST' \
         -H 'Content-Type: application/json; charset=utf-8' \
         -H 'Authorization: Bearer PtnrvrtSRpWwUi3407QhgvqdUVKL' \
         -v 'https://developer.api.autodesk.com/modelderivative/v2/designdata/job' \
         -d '{
               "input": {
                 "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6bW9kZWxkZXJpdmF0aXZlL0E1LnppcA"
               },
               "output": {
                 "formats": [
                   {
                     "type": "obj",
                     "advanced": {
                       "modelGuid": "4f981e94-8241-4eaf-b08b-cd337c6b8b1f",
                       "objectIds": [
                         -2
                       ]
                     }
                   }
                 ]
               }
             }'
    
    Show More

    Response

    Status Code: 400 Bad Request
    Content-Type:application/json;charset=utf-8
    x-ads-app-identifier:platform-viewing-2016.05.03.1102.2f6bfbf-production
    x-ads-startup-time:Wed May 11 14:03:54 CST 2016
    x-ads-duration:478 ms
    x-ads-exception-id:53ff8a6f-a49c-460a-b48c-79862e7eddb5
    x-ads-troubleshooting:Invalid Request
    
    {
      "diagnostic":"The values of 'objectIds' should be equal or greater than 0. You can also set the value as [-1] for getting the whole model."
    }
    
    Show More

    Example 6

    Successful creation of a job with webhook workflow specified (200)

    Request

    curl -X 'POST' \
         -H 'Content-Type: application/json; charset=utf-8' \
         -H 'Authorization: Bearer PtnrvrtSRpWwUi3407QhgvqdUVKL'
         -v 'https://developer.api.autodesk.com/modelderivative/v2/designdata/job' \
         -d
          '{
             "input": {
               "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6bW9kZWxkZXJpdmF0aXZlL0E1LnppcA",
               "compressedUrn": true,
               "rootFilename": "A5.iam"
             },
                         "misc": {
               "workflow": "my-workflow-id",
               "workflowAttribute": {
                 "myfoo": 33,
                 "projectId": "someURN",
                 "myobject": {
                   "nested": true
                 }
               }
             },
             "output": {
               "formats": [
                 {
                   "type": "svf",
                   "views": [
                     "2d",
                     "3d"
                   ]
                 }
               ]
             }
           }'
    
    Show More

    Response

    Status Code: 200 OK
    Content-Type:application/json;charset=utf-8
    Access-Control-Allow-Credentials:true
    Access-Control-Allow-Origin:*
    x-ads-app-identifier:platform-viewing-2016.05.03.1102.2f6bfbf-production
    x-ads-startup-time:Wed May 11 14:03:54 CST 2016
    x-ads-duration:280 ms
    
    {
      "result": "success",
      "urn": "dXJuOmFkc2sub2JqZWN0czpvcy5vYmplY3Q6bW9kZWxkZXJpdmF0aXZlL0E1LnppcA",
      "acceptedJobs": {
        "output": {
          "formats": [
            {
              "type": "svf",
              "views": [
                "2d",
                "3d"
              ]
            }
          ]
        }
      }
    }
    
    Show More
     
    ______
    icon-svg-close-thick

    Cookie preferences

    Your privacy is important to us and so is an optimal experience. To help us customize information and build applications, we collect data about your use of this site.

    May we collect and use your data?

    Learn more about the Third Party Services we use and our Privacy Statement.

    Strictly necessary – required for our site to work and to provide services to you

    These cookies allow us to record your preferences or login information, respond to your requests or fulfill items in your shopping cart.

    Improve your experience – allows us to show you what is relevant to you

    These cookies enable us to provide enhanced functionality and personalization. They may be set by us or by third party providers whose services we use to deliver information and experiences tailored to you. If you do not allow these cookies, some or all of these services may not be available for you.

    Customize your advertising – permits us to offer targeted advertising to you

    These cookies collect data about you based on your activities and interests in order to show you relevant ads and to track effectiveness. By collecting this data, the ads you see will be more tailored to your interests. If you do not allow these cookies, you will experience less targeted advertising.

    icon-svg-close-thick

    THIRD PARTY SERVICES

    Learn more about the Third-Party Services we use in each category, and how we use the data we collect from you online.

    icon-svg-hide-thick

    icon-svg-show-thick

    Strictly necessary – required for our site to work and to provide services to you

    Qualtrics
    We use Qualtrics to let you give us feedback via surveys or online forms. You may be randomly selected to participate in a survey, or you can actively decide to give us feedback. We collect data to better understand what actions you took before filling out a survey. This helps us troubleshoot issues you may have experienced. Qualtrics Privacy Policy
    Akamai mPulse
    We use Akamai mPulse to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Akamai mPulse Privacy Policy
    Digital River
    We use Digital River to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Digital River Privacy Policy
    Dynatrace
    We use Dynatrace to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Dynatrace Privacy Policy
    Khoros
    We use Khoros to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Khoros Privacy Policy
    Launch Darkly
    We use Launch Darkly to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Launch Darkly Privacy Policy
    New Relic
    We use New Relic to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. New Relic Privacy Policy
    Salesforce Live Agent
    We use Salesforce Live Agent to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Salesforce Live Agent Privacy Policy
    Wistia
    We use Wistia to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Wistia Privacy Policy
    Tealium
    We use Tealium to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Tealium Privacy Policy
    Upsellit
    We use Upsellit to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Upsellit Privacy Policy
    CJ Affiliates
    We use CJ Affiliates to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. CJ Affiliates Privacy Policy
    Commission Factory
    We use Commission Factory to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Commission Factory Privacy Policy
    Google Analytics (Strictly Necessary)
    We use Google Analytics (Strictly Necessary) to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Google Analytics (Strictly Necessary) Privacy Policy
    Typepad Stats
    We use Typepad Stats to collect data about your behaviour on our sites. This may include pages you’ve visited. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our platform to provide the most relevant content. This allows us to enhance your overall user experience. Typepad Stats Privacy Policy
    Geo Targetly
    We use Geo Targetly to direct website visitors to the most appropriate web page and/or serve tailored content based on their location. Geo Targetly uses the IP address of a website visitor to determine the approximate location of the visitor’s device. This helps ensure that the visitor views content in their (most likely) local language.Geo Targetly Privacy Policy
    SpeedCurve
    We use SpeedCurve to monitor and measure the performance of your website experience by measuring web page load times as well as the responsiveness of subsequent elements such as images, scripts, and text.SpeedCurve Privacy Policy
    Qualified
    Qualified is the Autodesk Live Chat agent platform. This platform provides services to allow our customers to communicate in real-time with Autodesk support. We may collect unique ID for specific browser sessions during a chat. Qualified Privacy Policy

    icon-svg-hide-thick

    icon-svg-show-thick

    Improve your experience – allows us to show you what is relevant to you

    Google Optimize
    We use Google Optimize to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Google Optimize Privacy Policy
    ClickTale
    We use ClickTale to better understand where you may encounter difficulties with our sites. We use session recording to help us see how you interact with our sites, including any elements on our pages. Your Personally Identifiable Information is masked and is not collected. ClickTale Privacy Policy
    OneSignal
    We use OneSignal to deploy digital advertising on sites supported by OneSignal. Ads are based on both OneSignal data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that OneSignal has collected from you. We use the data that we provide to OneSignal to better customize your digital advertising experience and present you with more relevant ads. OneSignal Privacy Policy
    Optimizely
    We use Optimizely to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Optimizely Privacy Policy
    Amplitude
    We use Amplitude to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Amplitude Privacy Policy
    Snowplow
    We use Snowplow to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Snowplow Privacy Policy
    UserVoice
    We use UserVoice to collect data about your behaviour on our sites. This may include pages you’ve visited. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our platform to provide the most relevant content. This allows us to enhance your overall user experience. UserVoice Privacy Policy
    Clearbit
    Clearbit allows real-time data enrichment to provide a personalized and relevant experience to our customers. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID.Clearbit Privacy Policy
    YouTube
    YouTube is a video sharing platform which allows users to view and share embedded videos on our websites. YouTube provides viewership metrics on video performance. YouTube Privacy Policy

    icon-svg-hide-thick

    icon-svg-show-thick

    Customize your advertising – permits us to offer targeted advertising to you

    Adobe Analytics
    We use Adobe Analytics to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, and your Autodesk ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Adobe Analytics Privacy Policy
    Google Analytics (Web Analytics)
    We use Google Analytics (Web Analytics) to collect data about your behavior on our sites. This may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. We use this data to measure our site performance and evaluate the ease of your online experience, so we can enhance our features. We also use advanced analytics methods to optimize your experience with email, customer support, and sales. Google Analytics (Web Analytics) Privacy Policy
    AdWords
    We use AdWords to deploy digital advertising on sites supported by AdWords. Ads are based on both AdWords data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that AdWords has collected from you. We use the data that we provide to AdWords to better customize your digital advertising experience and present you with more relevant ads. AdWords Privacy Policy
    Marketo
    We use Marketo to send you more timely and relevant email content. To do this, we collect data about your online behavior and your interaction with the emails we send. Data collected may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, email open rates, links clicked, and others. We may combine this data with data collected from other sources to offer you improved sales or customer service experiences, as well as more relevant content based on advanced analytics processing. Marketo Privacy Policy
    Doubleclick
    We use Doubleclick to deploy digital advertising on sites supported by Doubleclick. Ads are based on both Doubleclick data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Doubleclick has collected from you. We use the data that we provide to Doubleclick to better customize your digital advertising experience and present you with more relevant ads. Doubleclick Privacy Policy
    HubSpot
    We use HubSpot to send you more timely and relevant email content. To do this, we collect data about your online behavior and your interaction with the emails we send. Data collected may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, email open rates, links clicked, and others. HubSpot Privacy Policy
    Twitter
    We use Twitter to deploy digital advertising on sites supported by Twitter. Ads are based on both Twitter data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Twitter has collected from you. We use the data that we provide to Twitter to better customize your digital advertising experience and present you with more relevant ads. Twitter Privacy Policy
    Facebook
    We use Facebook to deploy digital advertising on sites supported by Facebook. Ads are based on both Facebook data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Facebook has collected from you. We use the data that we provide to Facebook to better customize your digital advertising experience and present you with more relevant ads. Facebook Privacy Policy
    LinkedIn
    We use LinkedIn to deploy digital advertising on sites supported by LinkedIn. Ads are based on both LinkedIn data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that LinkedIn has collected from you. We use the data that we provide to LinkedIn to better customize your digital advertising experience and present you with more relevant ads. LinkedIn Privacy Policy
    Yahoo! Japan
    We use Yahoo! Japan to deploy digital advertising on sites supported by Yahoo! Japan. Ads are based on both Yahoo! Japan data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Yahoo! Japan has collected from you. We use the data that we provide to Yahoo! Japan to better customize your digital advertising experience and present you with more relevant ads. Yahoo! Japan Privacy Policy
    Naver
    We use Naver to deploy digital advertising on sites supported by Naver. Ads are based on both Naver data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Naver has collected from you. We use the data that we provide to Naver to better customize your digital advertising experience and present you with more relevant ads. Naver Privacy Policy
    Quantcast
    We use Quantcast to deploy digital advertising on sites supported by Quantcast. Ads are based on both Quantcast data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Quantcast has collected from you. We use the data that we provide to Quantcast to better customize your digital advertising experience and present you with more relevant ads. Quantcast Privacy Policy
    Call Tracking
    We use Call Tracking to provide customized phone numbers for our campaigns. This gives you faster access to our agents and helps us more accurately evaluate our performance. We may collect data about your behavior on our sites based on the phone number provided. Call Tracking Privacy Policy
    Wunderkind
    We use Wunderkind to deploy digital advertising on sites supported by Wunderkind. Ads are based on both Wunderkind data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Wunderkind has collected from you. We use the data that we provide to Wunderkind to better customize your digital advertising experience and present you with more relevant ads. Wunderkind Privacy Policy
    ADC Media
    We use ADC Media to deploy digital advertising on sites supported by ADC Media. Ads are based on both ADC Media data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that ADC Media has collected from you. We use the data that we provide to ADC Media to better customize your digital advertising experience and present you with more relevant ads. ADC Media Privacy Policy
    AgrantSEM
    We use AgrantSEM to deploy digital advertising on sites supported by AgrantSEM. Ads are based on both AgrantSEM data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that AgrantSEM has collected from you. We use the data that we provide to AgrantSEM to better customize your digital advertising experience and present you with more relevant ads. AgrantSEM Privacy Policy
    Bidtellect
    We use Bidtellect to deploy digital advertising on sites supported by Bidtellect. Ads are based on both Bidtellect data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Bidtellect has collected from you. We use the data that we provide to Bidtellect to better customize your digital advertising experience and present you with more relevant ads. Bidtellect Privacy Policy
    Bing
    We use Bing to deploy digital advertising on sites supported by Bing. Ads are based on both Bing data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Bing has collected from you. We use the data that we provide to Bing to better customize your digital advertising experience and present you with more relevant ads. Bing Privacy Policy
    G2Crowd
    We use G2Crowd to deploy digital advertising on sites supported by G2Crowd. Ads are based on both G2Crowd data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that G2Crowd has collected from you. We use the data that we provide to G2Crowd to better customize your digital advertising experience and present you with more relevant ads. G2Crowd Privacy Policy
    NMPI Display
    We use NMPI Display to deploy digital advertising on sites supported by NMPI Display. Ads are based on both NMPI Display data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that NMPI Display has collected from you. We use the data that we provide to NMPI Display to better customize your digital advertising experience and present you with more relevant ads. NMPI Display Privacy Policy
    VK
    We use VK to deploy digital advertising on sites supported by VK. Ads are based on both VK data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that VK has collected from you. We use the data that we provide to VK to better customize your digital advertising experience and present you with more relevant ads. VK Privacy Policy
    Adobe Target
    We use Adobe Target to test new features on our sites and customize your experience of these features. To do this, we collect behavioral data while you’re on our sites. This data may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, your IP address or device ID, your Autodesk ID, and others. You may experience a different version of our sites based on feature testing, or view personalized content based on your visitor attributes. Adobe Target Privacy Policy
    Google Analytics (Advertising)
    We use Google Analytics (Advertising) to deploy digital advertising on sites supported by Google Analytics (Advertising). Ads are based on both Google Analytics (Advertising) data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Google Analytics (Advertising) has collected from you. We use the data that we provide to Google Analytics (Advertising) to better customize your digital advertising experience and present you with more relevant ads. Google Analytics (Advertising) Privacy Policy
    Trendkite
    We use Trendkite to deploy digital advertising on sites supported by Trendkite. Ads are based on both Trendkite data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Trendkite has collected from you. We use the data that we provide to Trendkite to better customize your digital advertising experience and present you with more relevant ads. Trendkite Privacy Policy
    Hotjar
    We use Hotjar to deploy digital advertising on sites supported by Hotjar. Ads are based on both Hotjar data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Hotjar has collected from you. We use the data that we provide to Hotjar to better customize your digital advertising experience and present you with more relevant ads. Hotjar Privacy Policy
    6 Sense
    We use 6 Sense to deploy digital advertising on sites supported by 6 Sense. Ads are based on both 6 Sense data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that 6 Sense has collected from you. We use the data that we provide to 6 Sense to better customize your digital advertising experience and present you with more relevant ads. 6 Sense Privacy Policy
    Terminus
    We use Terminus to deploy digital advertising on sites supported by Terminus. Ads are based on both Terminus data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that Terminus has collected from you. We use the data that we provide to Terminus to better customize your digital advertising experience and present you with more relevant ads. Terminus Privacy Policy
    StackAdapt
    We use StackAdapt to deploy digital advertising on sites supported by StackAdapt. Ads are based on both StackAdapt data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that StackAdapt has collected from you. We use the data that we provide to StackAdapt to better customize your digital advertising experience and present you with more relevant ads. StackAdapt Privacy Policy
    The Trade Desk
    We use The Trade Desk to deploy digital advertising on sites supported by The Trade Desk. Ads are based on both The Trade Desk data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that The Trade Desk has collected from you. We use the data that we provide to The Trade Desk to better customize your digital advertising experience and present you with more relevant ads. The Trade Desk Privacy Policy
    RollWorks
    We use RollWorks to deploy digital advertising on sites supported by RollWorks. Ads are based on both RollWorks data and behavioral data that we collect while you’re on our sites. The data we collect may include pages you’ve visited, trials you’ve initiated, videos you’ve played, purchases you’ve made, and your IP address or device ID. This information may be combined with data that RollWorks has collected from you. We use the data that we provide to RollWorks to better customize your digital advertising experience and present you with more relevant ads. RollWorks Privacy Policy

    Are you sure you want a less customized experience?

    We can access your data only if you select "yes" for the categories on the previous screen. This lets us tailor our marketing so that it's more relevant for you. You can change your settings at any time by visiting our privacy statement

    Your experience. Your choice.

    We care about your privacy. The data we collect helps us understand how you use our products, what information you might be interested in, and what we can improve to make your engagement with Autodesk more rewarding.

    May we collect and use your data to tailor your experience?

    Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.