For the complete documentation index, see llms.txt. This page is also available as Markdown.

Verification

What is it?

Verification allows the lab to check that the diamond received in the lab is the diamond that is registered on Tracr. This is done using the data that the client has uploaded onto Tracr and submitted to the lab.

How does it work?

The lab submits a POST /v2/diamonds/{diamond_id}/verify (reference) request with the Tracr ID, and the client-submitted Carat Weight and Shape Group. GIS compares these values with the data declared by the manufacturer.

Tracr checks that the diamond is a polished diamond registered in Tracr with a supported scan report.

Required data:

  • Tracr ID

  • Client-submitted Carat Weight (this should be what the client submits to the lab).

  • Client-submitted Shape (this should be what the client submits to the lab).

Call POST /v2/diamonds/kzsrfx4dxupa7a8uyn15wund/verify

{
    "carat_weight": 0.160,
    "shape_group": "Princess"
}
{
    "status": "success"
}
{
    "status": "failure",
    "data": {
        "carat_weight": {
            "matched": false,
            "known_value": "0.160",
            "given_value": "2.010",
            "tolerance": "0.020"
        },
        "shape_group": {
            "matched": true,
            "known_value": "Princess",
            "given_value": "Princess"
        }
    }
}

HTTP response status code

200 : Success

Returned when the request has been successfully processed.

404 : Not Found

Returned when a Diamond is not found in the Tracr network.

410 : Gone

Returned when the diamond has been deleted.

412 : Precondition Failed

Returned when there has not been a successful verify request for this diamond.

422 : Unprocessable Entity

Returned when the request doesn't match the endpoint data requirements.

500 : Internal Server Error

Returned when an internal error occurred within GIS. Please contact Tracr Support if you meet with this issue.

Last updated