POST
/
verify
curl --request POST \
  --url https://api.isofold.com/verify \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '{
  "original": [
    {}
  ],
  "rewritten": [
    {}
  ]
}'
{
  "equal": true,
  "differences": [
    {}
  ]
}

Submit two result sets and verify whether they are semantically equivalent.

This endpoint is typically used to compare:

  • The original query result
  • The Isofold-optimized query result

Useful for audit logging, testing, and compliance scenarios.

​
Request

{
  "original": [
    { "id": 1, "email": "a@example.com" },
    { "id": 2, "email": "b@example.com" }
  ],
  "rewritten": [
    { "id": 2, "email": "b@example.com" },
    { "id": 1, "email": "a@example.com" }
  ]
}

​
Fields

FieldTypeRequiredDescription
originalarray✅Result set from the original query
rewrittenarray✅Result set from the rewritten query

​
Response

{
  "equal": true,
  "differences": []
}

If the results do not match, you’ll see the differences:

{
  "equal": false,
  "differences": [
    {
      "row": 2,
      "original": { "id": 3, "email": "c@example.com" },
      "rewritten": null
    }
  ]
}

​
Notes

  • Comparison is order-insensitive
  • Field names must match exactly
  • Null vs undefined are treated as distinct

Use this endpoint to integrate Isofold verification into your CI, analytics pipelines, or regulated audit flows.

Next: Query Completion Webhook

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json

Response

200 - application/json

Verification result

The response is of type object.