GET /modelderivative/v2/designdata/{urn}/manifest/{derivativeUrn}/signedcookies

Returns a download URL and a set of signed cookies, which lets you securely download the derivative specified by the derivativeUrn URI parameter. The signed cookies have a lifetime of 6 hours. You can use range headers with the returned download URL to download the derivative in chunks, in parallel.

Servers

Path parameters

Name Type Required Description
urn String Yes

The URL-safe Base64 encoded URN of the source design.

derivativeUrn String Yes

The URL-encoded URN of the derivative. Use the Fetch Manifest operation </en/docs/model-derivative/v2/reference/http/manifest/urn-manifest-GET/>_to obtain the URNs of derivatives for the specified source design.

Request headers

Name Type Required Description
region String No

Specifies the data center where the manifest and derivatives of the specified source design are stored. Possible values are:

  • US - (Default) Data center for the US region.
  • EMEA - Data center for the European Union, Middle East, and Africa.
  • AUS - Data center for the Australia region.
  • CAN - Data center for the Canada region.
  • DEU - Data center for the Germany region.
  • IND - Data center for the India region.
  • JPN - Data center for the Japan region.
  • GBR - Data center for the United Kingdom region.

Valid values:

  • "US"
  • "IND"
  • "AUS"
  • "EMEA"
  • "CAN"
  • "JPN"
  • "GBR"
  • "DEU"

Query parameters

Name Type Required Description
minutes-expiration Integer No

Specifies how many minutes the signed cookies should remain valid. Default value is 360 minutes. The value you specify must be lower than the default value for this parameter. If you specify a value greater than the default value, the Model Derivative service will return an error with an HTTP status code of 400.

response-content-disposition String No

The value that must be specified as the response-content-disposition query string parameter with the download URL. Must begin with attachment. This value defaults to the default value corresponding to the derivative/file.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.