Verify
/v1/verify/{fingerprint}Verify a 128-bit binary fingerprint and retrieve the exact FDA source. Provides cryptographic proof of citations with mathematical certainty.
Overview
The Verify endpoint enables independent verification of citations with cryptographic certainty. Anyone can verify that a fingerprint corresponds to exact FDA source text - even months or years after the original search.
Verification uses XOR-based Hamming distance for mathematical proof. A Hamming distance of 0 means exact match (verified). Any non-zero distance means the fingerprint doesn't match (not verified).
Path Parameters
fingerprintstringrequired128-character binary string (0s and 1s only). The fingerprint must be exactly 128 bits and contain only valid binary digits.
Response Structure
Responses follow a standard structure with status: 1, msg, and data containing the verification result. When a fingerprint is found, data contains verification details. When not found, data.detail will be "Not Found".
statusintegerResponse status. 1 indicates success.
msgstringStatus message, typically "operation successful".
dataobjectThe verification result data. The structure differs based on whether the fingerprint is found:
When fingerprint is NOT found:
detailstringContains "Not Found" when the fingerprint is not in the verify database.
When fingerprint IS found:
verifiedbooleanTrue if exact match found (Hamming distance = 0), false otherwise.
textstring | nullFDA label text segment (null if not verified).
drugobject | nullDrug information (null if not verified).
sectionstring | nullDocument section (null if not verified).
sourceobject | nullSource URL (null if not verified).
messagestring | nullError message explaining why verification failed (null if successful).
Use Cases
Important Notes
Fingerprint must be exactly 128 characters long. Shorter or longer strings will be rejected.
Note: Not all fingerprints returned by the Search API may be available in the Verify database. If a fingerprint from search results returns "Not Found", it means that specific fingerprint is not currently indexed in the verify database. The verify endpoint is working correctly, but has limited coverage compared to the search endpoint.
Fingerprint must contain only binary digits (0s and 1s). Any other characters will cause validation failure.
Hamming distance = 0 means exact match. This provides cryptographic-level certainty of verification.
Error Responses
All error responses follow a standard structure with status: 0, errorCode, and msg fields: