ScoreDetect API

For developers only. This is a test API endpoint during the configuration of your custom integration with the ScoreDetect API.

Generates a SHA-256 checksum hash. Requires a form-data key called file which accepts either a File or Text input type. Once added, the API takes in the input and performs a SHA-256 hash function, and returns a JSON object of the checksum value.

Generates a valid unique certificate ID. This can be useful for preparing the certificate ID, for example, before a blockchain transaction is made.

Specify the certificate ID (uuid) to fetch from with the ?id= query string parameter.

Specify the certificate ID (uuid) to fetch from with the ?id= query string parameter.

The certificate requires a form-data key called hash which accepts a 64-character SHA-256 hash string. However, our legacy feature also provides a key called file which accepts either a File or Text input type. Once added, the API uses the hash, or takes in the input file and performs a SHA-256 hash function before sending it to the blockchain. This ensures a "privacy-first" approach. We recommend using sending the request with the hash key for unlimited file size and optimum security best practices.

The certificate metadata (not the blockchain transaction) can be updated by adding the body as a JSON stringified object containing 2 properties: the certificateId (the certificate ID) and metadata (an object containing e.g. { "username": "anonymous", "certificateType": "plain_text_upload", "displayCreatedBy": false }. The username is the ScoreDetect username (default is anonymous), certificateType accepts 2 values: plain_text_upload or file_upload, and displayCreatedBy accepts a boolean value of true or false.

Add 1 or more "certificateIds" in an array, as a raw body JSON for example { "certificateIds": [ "12345678-1234-1234-1234-123456789012", "22345678-1234-1234-1234-123456789012" ] }. Once the certificate is deleted, the response will return the deleted certificate IDs.