Skip to content

Verification

The verification endpoint lets you confirm that a signed document is authentic by checking its SHA-256 hash against inSigner’s records.

POST /api/v1/verify

Checks both the original document hash and the signed document hash. Returns whether a matching document exists in your organization.

Required scope: documents.read

Request body

FieldTypeRequiredDescription
hashstring64-character hex SHA-256 hash of the document
Terminal window
# First, compute the SHA-256 hash of the document
SHA256=$(shasum -a 256 document.pdf | awk '{print $1}')
# Then verify it
curl -X POST https://app.insigner.co/api/v1/verify \
-H "Authorization: Bearer isk_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d "{\"hash\": \"$SHA256\"}"
{
"data": {
"verified": true,
"documentId": "cm5x9abc123",
"documentName": "Sales Agreement Q3",
"status": "completed",
"completedAt": "2026-05-29T14:30:00.000Z",
"hashMatch": "signed"
}
}
FieldDescription
verifiedtrue if a matching document was found
documentIdThe document ID
documentNameThe document name
statusCurrent document status
completedAtWhen signing was completed
hashMatch"original" if matching the original PDF, "signed" if matching the signed PDF
{
"data": {
"verified": false,
"documentId": null,
"documentName": null,
"status": null,
"completedAt": null,
"hashMatch": null
}
}