An attestation is a signed statement from an issuer. A useful integration manages the whole lifecycle: what gets signed, how recipients check it, how the evidence is shared, and what happens when the statement should no longer be relied on.
Define the record before calling the API
Choose a stable business reference, the issuer responsible for the statement, and the minimum payload required for the workflow. Use the supported schema and exact encoding documented for your API version. Do not improvise signing formats from a visual certificate or an old code sample.
For a course completion record, the important fields might include a course reference and approved completion details. The institution decides what the statement means. Truthlocks signs and manages the record within the configured issuing workflow.
Issue and retain the result
Use the correct issuing identity and configured signing key. Store the returned record identifier and the evidence your application needs for later checks. Handle validation, permission, and service errors explicitly. If an issuing request times out, determine whether a record was created before retrying a write.
Check the actual idempotency behavior of the endpoint and SDK version you use. A retry limit alone does not establish that repeating a write cannot create duplicate business events.
Check before presenting a conclusion
Verify the supported record using the appropriate public-key information. Keep signature integrity, issuer context, and current status visible as separate parts of the result. If verification is unavailable, say so and give the user a retry or review path rather than displaying a successful badge.
Share and manage changes
A verification link gives recipients a route to the current check. A supported proof bundle can carry signatures, keys, and available log proofs for independent inspection. Offline evidence cannot report a revocation that occurred after the package was created.
Define who can revoke a record and when a corrected statement requires a new issuance. Test a revoked record and a changed payload before integrating the success path into your user interface.
Build against current documentation
Use the current API documentation and your installed SDK’s method signatures. Begin with the course completion example or permit-record workflow, then adapt the fields and approval responsibilities to your system.