GET /modelderivative/v2/designdata/{urn}/manifest
Retrieves the manifest of the specified source design.
The manifest is a JSON file containing information about all the derivatives translated from the specified source design. It contains information such as the URNs of the derivatives, the translation status of each derivative, and much more.
The first time you translate a source design, the Model Derivative service creates a manifest for that design. Thereafter, every time you translate that source design, even to a different format, the Model Derivative service updates the same manifest. It does not create a new manifest. Instead, the manifest acts like a central registry for all the derivatives of your source design created through the Model Derivative service.
When the Model Derivative service starts a translation job (as a result of a request you make using Create Translation Job </en/docs/model-derivative/v2/reference/http/jobs/job-POST/>_), it keeps on updating the manifest at regular intervals. So, you can use the manifest to check the status and progress of each derivative that is being generated. When multiple derivatives have been requested each derivative may complete at a different time. So, each derivative has its own status attribute. The manifest also contains an overall status attribute. The overall status becomes complete when the status of all individual derivatives become complete.
Once the translation status of a derivative is complete you can download the derivative.
Note: You cannot download 3D SVF2 derivatives.
Servers
- https://developer.api.autodesk.com
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
urn |
String | Yes |
The URL-safe Base64 encoded URN of the 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:
Valid values:
|
Accept-Encoding |
String | No |
A comma separated list of the algorithms you want the response to be encoded in, specified in the order of preference. If you specify |
How to start integrating
- Add HTTP Task to your workflow definition.
- 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.
- Click Test request to test run your request to the API and see the API's response.