Delete a scene
DELETE
photoscene/{photosceneid}
Deletes a photoscene and its associated assets (images, output files, …).
Resource Information
Method and URI | DELETE https://developer.api.autodesk.com/photo-to-3d/v1/photoscene/{photosceneid} |
Authentication Context | user context optional |
Required OAuth Scopes | data:write |
Data Format | JSON |
Request
Headers
Authorization* string | Must be Bearer <token> , where <token> is obtained via either a two-legged or three-legged OAuth flow. |
* Required
Request
URI Parameters
photosceneid string | Specifies the ID of the photoscene |
Response
HTTP Status Code Summary
200 OK | The photoscene was successfully deleted |
403 Forbidden | Unauthorized |
Response
Body Structure (200)
Expand all
msg string | A human readable notification that the operation was successful. |
Error object | Even though the the service returns a HTTP Status Code of 200, it may return an error payload, which provides details on why the operation failed. |
code int | A code that identifies the error type. See Error List for possible values |
msg string | A short, human readable explanation of the error |
Example 1
This example demonstrates successfully deleting the photoscene bearing photosceneid AtAuFsedTdqWdhF9VzHepp5oM9PITiuizI4xdMbz.
Request
curl -v 'https://developer.api.autodesk.com/photo-to-3d/v1/photoscene/AtAuFsedTdqWdhF9VzHepp5oM9PITiuizI4xdMbz' \
-X 'DELETE' \
-H 'Authorization: Bearer eyjhbGCIOIjIuzI1NiISimtpZCI6...'
Response
{
"msg": "No error"
}
Example 2
This example demonstrates an attempt to delete a non-existent photoscene.
Request
curl -v 'https://developer.api.autodesk.com/photo-to-3d/v1/photoscene/BtAuFsedTdqWdhF9VzHepp5oM9PITiuizI4xdMbz' \
-X 'DELETE' \
-H 'Authorization: Bearer eyjhbGCIOIjIuzI1NiISimtpZCI6...'
Response
{
"Error": {
"code": "19",
"msg": "Specified photoscene ID doesn't exist in the database"
}
}