</> For Developers
Certificate API integration for developers
TRUE's REST API issues a blockchain secured certificate from a single HTTP call. Five endpoints cover the whole surface: create, retrieve, list, update and revoke. Verification data comes back in the same response, so nothing else has to be wired up before a credential can be checked.
TL;DR
TRUE's certificate API is a REST interface with five endpoints. POST a template ID, a recipient and a set of fields, and the API creates the certificate, writes its cryptographic fingerprint to a blockchain, emails the recipient and returns a verification URL on your own domain. Authentication is a bearer API key, scoped per environment, and a sandbox key lets you exercise the whole flow without issuing real credentials. Batch issuing and webhooks cover volume and event handling, so an LMS, CRM or student system can drive issuance without anyone opening a dashboard. Most teams have a working integration inside one to two weeks.
- Five endpoints, one per lifecycle action: create, retrieve, list, update, revoke.
- Blockchain proof is included in every response, with no second call to make.
- Verification URLs sit on your own domain, so shared credentials point back to you.
- Sandbox keys exercise the full API without touching production quotas.
What is TRUE's certificate API?
A REST API that turns a completion record into a verifiable credential. You send recipient data and a template reference over HTTPS, and TRUE returns an issued certificate with its blockchain proof attached. There is no SDK to install and no message queue to run.
TRUE's Certificate API is designed for developers who need to automate credential issuance without wrestling with complexity.
Five endpoints
Create, retrieve, list, update, and revoke certificates. That's the entire API surface. No complexity, no bloat.
Restful architecture
Standard HTTP methods, JSON payloads, predictable responses. If you've integrated any modern API, you know how to use TRUE.
Blockchain included
Every certificate is automatically secured on blockchain. No additional config. No separate calls. Verification in every response.
How far has API driven credentialing spread?
Far enough that an API is now the default way organisations expect to move credential data, and far enough that the EU has legislated a wallet to receive it. The figures below are published third party research, not TRUE platform data.
- 82% of organisations have adopted some level of an API first approach, and 25% now run fully API first, a 12% increase on 2024. Source: Postman, 2025 State of the API Report, a survey of more than 5,700 developers, architects and executives.
- Every EU Member State must offer at least one EU Digital Identity Wallet by 2026, built to common specifications, and the Commission lists education diplomas among the documents it will carry. Source: European Commission, on Regulation (EU) 2024/1183, adopted 20 May 2024.
- Only 52% of large employers verify all the academic credentials they are shown, falling to 37% at medium sized organisations and 29% at small ones. Source: Prospects Luminate, November 2025, from a YouGov survey of 526 HR decision makers.
A credential that ships with its own verification URL closes that last gap without asking the verifier to do anything. The rest of this page covers how to issue one.
How do I issue a certificate with a single API call?
POST to /v1/certificates with a template ID, the recipient's name and email, and the fields your template expects. That one call creates the document, anchors it on chain and emails the recipient. The response carries the verification URL and the transaction hash.
Issue your first certificate with a single API call.
Create a Certificate
curl -X POST https://api.trueoriginal.com/v1/certificates \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template_id": "tmpl_abc123",
"recipient": {
"name": "Maria Andersson",
"email": "[email protected]"
},
"fields": {
"course_name": "Advanced Project Management",
"completion_date": "2026-03-03",
"credential_id": "PM-2026-0042"
}
}'One call does everything
The certificate is created, blockchain-secured, and sent via email. All from one API call.
API keys are generated in your TRUE dashboard. Create separate keys for development, staging, and production.
Response with blockchain proof
Every response includes blockchain verification data. The certificate is immediately verifiable. No waiting, no separate verification calls.
Verification URLs use your custom domain, keeping your brand front and center.
Response
{
"id": "cert_xyz789",
"status": "issued",
"recipient": {
"name": "Maria Andersson",
"email": "[email protected]"
},
"verification_url": "https://verify.yourorg.com/cert_xyz789",
"blockchain": {
"network": "polygon",
"transaction_hash": "0x1234...abcd",
"confirmed": true
},
"created_at": "2026-03-03T09:15:00Z"
}
Which endpoints does the certificate API expose?
Five, one per lifecycle action. Create issues a credential, retrieve and list read them back, update changes status or metadata, and delete revokes. Revocation updates the blockchain record rather than erasing it, so the audit trail survives.
Everything you need to automate certificate issuance.
| Method | Endpoint | Description |
|---|---|---|
| POST | /v1/certificates | Create and issue a new certificate |
| GET | /v1/certificates/{id} | Retrieve certificate data and verification status |
| GET | /v1/certificates | List all issued certificates with filters |
| PUT | /v1/certificates/{id} | Update certificate status or metadata |
| DELETE | /v1/certificates/{id} | Revoke a certificate (blockchain record updated) |
Which systems can trigger certificate issuance?
Any system that can make an HTTP request. TRUE connects to Canvas LMS, Moodle, Learnster and Salesforce directly, and a custom student or HR system calls the same endpoints. The trigger is normally a completion event you already record.
TRUE connects to the platforms your organization already uses.
Salesforce
Trigger issuance when opportunities close or certifications are earned
Canvas LMS
Issue certificates automatically on course completion
Moodle
Automate credentials based on quiz scores or completion
Learnster
Turn a course completion event into an issued credential
How does the API handle bulk issuing and event notifications?
Bulk issuing goes through a batch endpoint that accepts an array of recipients and returns a job ID you can poll. Webhooks push the other direction, firing when a credential is issued, viewed, shared, verified or revoked, so your own reporting stays current without polling.
Bulk operations
Issuing hundreds or thousands of certificates? Use the batch endpoint for efficient bulk issuance.
Upload recipient arrays, get a batch job ID, and track progress. For teams without dev resources, CSV upload in the dashboard works too.
Batch Issuance
curl -X POST .../v1/certificates/batch \
-H "Authorization: Bearer YOUR_API_KEY" \
-d '{
"template_id": "tmpl_abc123",
"recipients": [
{"name": "Anna", "email": "anna@..."},
{"name": "Erik", "email": "erik@..."},
...
]
}'Webhook Event
{
"event": "certificate.verified",
"certificate_id": "cert_xyz789",
"timestamp": "2026-03-03T10:30:00Z",
"data": {
"viewer_location": "Stockholm, SE",
"referrer": "linkedin.com"
}
}Real-time webhooks
Get notified when certificates are issued, viewed, shared, or verified. Configure multiple endpoints filtered by event type.
Events: certificate.issued, certificate.viewed, certificate.shared, certificate.verified, certificate.revoked
What do teams automate with the certificate API?
Three patterns cover most integrations: graduation runs driven by a student record system, compliance training where the credential carries an expiry date, and course completion where the share itself is the marketing. Each one replaces a manual export and mail merge.
Automated graduation
Student system marks graduates → webhook triggers issuance → graduates receive blockchain diplomas instantly. Share on LinkedIn the same day.
Compliance training
LMS completion triggers certificate with expiration date. HR receives webhook confirmation. Analytics track auditor verifications.
Course completion
Platform detects completion → API issues credential → learner shares → every share drives enrollments back to your platform.
What are the API's rate limits, security and reliability guarantees?
Rate limits scale by plan, from 60 requests a minute on Standard to custom limits on Enterprise. TLS 1.3 is required, API keys are scoped by environment, and enterprise plans add IP allowlisting and full activity logging. Webhook deliveries retry automatically on failure.
Rate limits
| Standard | 60 req/min, batch 100 |
| Professional | 300 req/min, batch 500 |
| Enterprise | Custom limits |
Security
| Encryption | TLS 1.3 required |
| Auth | API keys, scoped by env |
| Enterprise | IP allowlisting available |
| Audit | Full activity logging |
Reliability
| SLA | 99.9% uptime (enterprise) |
| Webhooks | Automatic retry on failure |
| Status | status.trueoriginal.com |
Response codes
| 200, 201 | Success / Created |
| 400 | Validation error |
| 401 | Invalid API key |
| 429 | Rate limit exceeded |
What do developers ask before integrating?
The four questions below cover language support, sandbox testing, integration time and whether blockchain anchoring needs configuring. The short version: any language that speaks HTTP, yes there is a sandbox, one to two weeks, and no configuration needed.
What programming languages are supported?
TRUE's REST API works with any language that can make HTTP requests. Documentation includes examples in curl, JavaScript, Python, and PHP.
Is there a sandbox environment?
Yes. Sandbox API keys let you test the full API without issuing real certificates or consuming production quotas.
How quickly can we integrate?
Most integrations go live within one to two weeks. The API has only 5 endpoints, making integration straightforward for experienced developers.
Is blockchain verification automatic?
Yes. Every certificate is automatically secured on blockchain. No additional configuration. No separate calls. Verification data is included in every API response.
What customers say
“The animation looks fantastic, and it’s so simple for our recipients. It has made things much easier for us at Sitevision with the digital certificates.”
“We are very happy with our work with TRUE Original. Their technology let our customers get lots of positive attention.”
Ready to automate certificate issuance?
Request API keys and you can issue a sandbox credential the same day. Five endpoints cover the whole surface, blockchain anchoring needs no configuration, and most teams are in production inside one to two weeks. The docs carry working examples in curl, JavaScript, Python and PHP.
Related resources
Learn more about certificate workflows and automation.
Design automated workflows for certificate issuance and distribution.
Credential lifecycle managementManage credentials from issuance through renewal and revocation.
Blockchain verificationHow blockchain technology secures and verifies digital credentials.
Tech partner certification platformAPI-first partner certification programmes for tech companies that automate everything.