Review and approve models
Approve a model or send it back to our 3D team with comments, through the API or in your CharpstAR account.
When a model has passed our quality check, it waits for your approval. The review.requested event tells you, with a reviewUrl that opens the model in your CharpstAR account. Approve or request changes there or through the API.
Approve a model or request changes
POST/api/v1/products/{article}/reviewreviews:writedecision is approve or request_changes.
approvepublishes the model, exactly as approving in your CharpstAR account does.asset.approvedfollows once its files are live. A product with variants is approved with all of them.request_changessends the model back to our 3D team with your comments. Each comment hastextand an optionalimageUrl, an https link to a photo or drawing that shows it. We copy the image to your account.
{
"decision": "request_changes",
"comments": [
{
"text": "The legs should be oiled oak, see the photo.",
"imageUrl": "https://media.example.com/ch-1001/legs.jpg"
}
]
}curl -sS -X POST https://platform.charpstar.co/api/v1/products/CH-1001/review \
-H "Authorization: Bearer $CHARPSTAR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "decision": "request_changes", "comments": [{ "text": "The seat is too thick", "imageUrl": "https://example.com/seat.jpg" }] }'A model that is not waiting for you answers 409 not_ready.
From the third change request on the same model, extra revisions will likely be charged, so that request is made in your CharpstAR account, where you confirm it; the API answers 409 not_ready.
Change a delivered model
Changes to a model that is already delivered are requested the same way. It stays delivered and its links keep working while we make the change, and each one counts against your yearly change allowance (402 allowance_reached once it is used up).