Every time you call saveProduct or finishProductDesign, Customer's Canvas creates a state file representing all objects loaded in the editor. By default, these state files are saved in the ~\UserDataFolder\<someUserId>\states\ folder for a single user and they are kept forever until you delete these files manually. Customer's Canvas does not automatically clean them up. At the same time, you can use the Web API to manipulate state files in your application: list available state files, delete state files, or reload images in state files from their original sources.
This API works based on HTTPS requests and is handled by the StateFiles controller with the following methods:
| Function | Request type | URL |
|---|---|---|
| Get a list of user's state files | GET |
~/api/users/{userId}/states
|
| Download a user's state file | GET |
~/api/users/{userId}/states/{stateId}
|
| Delete a user's state file | DELETE |
~/api/users/{userId}/states/{stateId}
|
| Copy and clone a state file | POST |
~/api/users/{userId}/states/{stateId}
|
| Reload images in a state file | PATCH |
~/api/users/{userId}/states/{stateId}
|
The StateFiles controller requires the following parameters:
This controller can return the following errors:
Status Code: 403 Forbidden Content: HTTPS Required
Status Code: 403 Forbidden Content: Invalid Security Key
Status Code: 404 Not Found Content: The specified state file cannot be found.
Status Code: 400 Bad Request Content: This state already exists.
Status Code: 500 Internal Server Error Content: The remote server returned an error: (404) Not Found.
It is recommended to download a code sample written in ECMAScript 2015 that demonstrates how you can work with the API and refer to this sample when reading this topic.
The security model of Customer's Canvas requires you to pass X-CustomersCanvasAPIKey in request headers. The snippets below define the API security key in JavaScript code. It could be highly insecure if it runs on a public site. However, you can use it this way in your admin panel, or just for demonstration purposes.
For example, you will get the following response for the case when the default user has a state file.
Meet us at SGIA Expo. Las Vegas, NV. Oct. 18—19.
Status Code: 200 OK
Content:
[{
"stateId":"0777bb82-6f89-4e72-93b1-aad1b875602b",
"dateModified":"5/26/2018 8:29",
"surfaceCount":2,
"tag":null
}]
const userId = "default";
const url = `https://localhost:44300/api/users/${userId}/states`;
fetch(url).then(response => {
return response.json();
}).then(json => {
for (let i = 0; i < json.length; i++) {
const s = json[i];
console.log(s.stateId);
}
});
If the result is successful, this API returns a file stream:
Status Code: 200 OK Content-type: application/octet-stream
const userId = "JohnWood";
const stateId = "1f190673-226d-4c31-87b4-0140805cc445";
const url = `https://localhost:44300/api/users/${userId}/states/${stateId}`;
logElement.textContent = "init request";
fetch(url, {
method: "GET",
headers: {
"X-CustomersCanvasAPIKey": "UniqueSecurityKey",
'Accept': 'application/json',
"Content-Type": "application/json"
}
})
.then(
response => {
if (response.ok) {
console.log("The state file was downloaded successfully.");
console.log(response.url);
}
else
console.error("Failed to download the state file.");
},
e => console.error("Failed to download the state file.")
);
If the result is successful, this API can return the following:
Status Code: 200 OK Content: false
Status Code: 200 OK Content: true
const userId = "JohnWood";
const stateId = "1f190673-226d-4c31-87b4-0140805cc445";
const url = `https://localhost:44300/api/users/${userId}/states/${stateId}`;
fetch(url, {
method: "DELETE",
headers: {
"X-CustomersCanvasAPIKey": "UniqueSecurityKey",
"Content-Type": "application/json"
}
})
.then(
response => { return response.json(); },
e => console.log("Failed to delete the state file.")
)
.then(json => {
if (json === true)
console.log("The state file was deleted successfully.");
else if (json === false)
console.log("Requested state file is not found.");
});
To copy state files, you need to pass the following parameters in the request body:
const parameters = {
"CopyFrom": {
"UserId": "sourceUserId",
"StateId": "sourceStateId"
},
"Overwrite": true
};
Note that userId and stateId in the request URL are the destination identifiers.
When a state file has been successfully copied, this controller returns:
Status Code: 204 No Content
const userId = "JohnWood";
const stateId = "Invitation";
const sourceUserId = "masteruser";
const sourceStateId = "1f190673-226d-4c31-87b4-0140805cc445";
const url = `https://localhost:44300/api/users/${userId}/states/${stateId}`;
const parameters = {
"CopyFrom": {
"UserId": sourceUserId,
"StateId": sourceStateId
},
"Overwrite": true
};
fetch(url, {
method: "POST",
headers: {
"X-CustomersCanvasAPIKey": "UniqueSecurityKey",
"Accept": "application/json",
"Content-Type": "application/json"
},
body: JSON.stringify(parameters)
})
.then(
response => {
if (response.ok)
console.log("The state file was copied.");
else
console.log("Failed to copy the state file.");
}
);
You can reload images obtained from external sources through direct URLs. After your end users have added images through the Asset Manager, the original files may be changed. If the application requires those changes to be applied to saved state files, you can use this Web API method. This method will trigger Customer's Canvas to download new versions of these images and will replace them in the state file. Reloading images invalidates preview and hi-res links in the cache, thus they are recreated based on the new versions of these images when the application requests them next time.
If the original image has been edited so that its dimensions have changed, then the new image is arbitrarily resized to fit into the old bounds when reloading this image. If any of the original images are deleted, the controller returns the 500 Server error and does not reload images.
To reload all images in a state file, you should specify the MemorySourceReloadAll type in the request body.
Another use case of this method is replacing Depositphotos previews with purchased images. In this case, you should specify the PatchImageItems type and links to the purchased images. For an example, refer to the Depositphotos Assets topic.
When a state file has been successfully patched, this controller returns:
Status Code: 204 No Content
const userId = "JohnWood";
const stateId = "1f190673-226d-4c31-87b4-0140805cc445";
const url = `https://localhost:44300/api/users/${userId}/states/${stateId}`;
fetch(url, {
method: "PATCH",
headers: {
"X-CustomersCanvasAPIKey": "UniqueSecurityKey",
"Content-Type": "application/json"
},
body: JSON.stringify({
type: "MemorySourceReloadAll"
})
})
.then(
response => {
if (response.ok)
console.log("Images were reloaded successfully.");
else
console.log("Failed to reload images.");
}
);