Provenance Proof data ingestion API

POST {{baseUrl}}/data/binary-files

The /data/binary-files endpoint is used to upload of Json files only. The file name provided must be unique.

Request headers

x-evl-client-id

x-evl-client-secret

Content-Type multipart/form-data

Authentication and Security

To get started using the API, access to the API requires authentication headers which will be provided from the developer support team. Please contact them to your get client id & secret.

The body form data is being used to specify the file name and path as and schema information as form data in the body of the API request.

The first form data information indicates which schema is being used. The schema header needs the name of the schema which is being used to provide the stone details.

1schemaID :

If there is a custom schema being used for the submission of the stones, the developer support team will provide you with the name of the custom schema as it is being known by the system. If you are using one of the standard schemas, the below schema id references can be used:



Schema purpose



Schema ID



Schema purpose



Schema ID



Raw Gems



rawgemsv3



Cut Gems



cutgemsv3



Pearls



pearls

The other form data information being used is the file name. There are no guidelines for the naming of the JSON files but they need to be unique for every submission, the form data field file allows you to specify the file name and path to the file.

Request Body

[{"name"=>"schemaId", "value"=>"pearls", "datatype"=>"string"}, {"name"=>"file", "value"=>nil, "datatype"=>"null"}]

HEADERS

KeyDatatypeRequiredDescription
x-evl-client-idnull
x-evl-client-secretnull