Skip to main content

Getting Started with Credentials

Basic Credential Operations

Issue credentials using the /credentials endpoint with a template and recipient information:
curl -X POST "https://api.hixbe.com/certify/credentials" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Hixbe-Version: 2026-01-01" \
  -H "Content-Type: application/json" \
  -d '{
    "template_id": "tmpl_123",
    "recipient": {
      "name": "John Doe",
      "email": "john@example.com"
    },
    "expires_at": "2026-12-31T23:59:59Z"
  }'
You can issue certificates, badges, diplomas, licenses, and other verifiable credentials using customizable templates.
Recipients receive a secure link via email or direct API response. They can view, download, and share their verifiable credentials.

Templates and Design

Design templates through the API or dashboard with custom layouts, branding, and variable fields:
curl -X POST "https://api.hixbe.com/certify/templates" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Hixbe-Version: 2026-01-01" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Completion Certificate",
    "type": "certificate",
    "design": {
      "background_color": "#ffffff",
      "text_fields": [
        {"label": "Recipient Name", "variable": "recipient_name"},
        {"label": "Course", "variable": "course_name"},
        {"label": "Completion Date", "variable": "completion_date"}
      ]
    }
  }'
Yes, templates support custom colors, fonts, logos, and layouts. You can include images, signatures, and security features.
Templates can be updated, but this affects future credentials only. Existing issued credentials remain unchanged.

Verification and Validation

Credential Verification

Use the verification endpoint with the credential ID:
curl -X POST "https://api.hixbe.com/certify/credentials/verify" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Hixbe-Version: 2026-01-01" \
  -H "Content-Type: application/json" \
  -d '{
    "credential_id": "cred_1234567890"
  }'
Verification confirms: credential authenticity, issuer validity, expiration status, revocation status, and tamper-proofing.
Yes, credentials include public verification URLs that anyone can use without API access.

Public Verification

Yes, you can white-label verification pages with your branding and custom domains.

Badges and Micro-Credentials

Badge Management

Badges are typically smaller achievements or skills, while certificates represent larger accomplishments like course completion or degrees.
Create badges similar to certificates but with badge-specific metadata:
curl -X POST "https://api.hixbe.com/certify/badges" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Hixbe-Version: 2026-01-01" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "JavaScript Expert",
    "description": "Demonstrated advanced JavaScript skills",
    "image_url": "https://example.com/badge-image.png",
    "criteria": "Complete advanced JS course with 90%+ score"
  }'
Yes, you can create badge pathways where earning one badge unlocks requirements for others.

Programs and Pathways

Learning Programs

Programs are structured learning pathways with multiple credentials, prerequisites, and progression tracking.
Create programs with credential requirements and progression rules:
curl -X POST "https://api.hixbe.com/certify/programs" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Hixbe-Version: 2026-01-01" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Web Development Certification",
    "description": "Complete web development pathway",
    "credentials": [
      {"template_id": "tmpl_html", "required": true},
      {"template_id": "tmpl_css", "required": true},
      {"template_id": "tmpl_js", "required": true}
    ]
  }'
As learners earn individual credentials, the system tracks progress and automatically issues program completion certificates.

Security and Compliance

Credential Security

Credentials use cryptographic signatures, tamper-proofing, and blockchain-based verification to ensure authenticity.
No, each credential contains cryptographic proofs that prevent forgery and detect tampering.
We comply with GDPR and other privacy regulations. Personal data is encrypted and you control data retention policies.

Revocation Management

Use the revoke endpoint to mark credentials as invalid:
curl -X POST "https://api.hixbe.com/certify/credentials/revoke" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Hixbe-Version: 2026-01-01" \
  -H "Content-Type: application/json" \
  -d '{
    "credential_id": "cred_1234567890",
    "reason": "Policy violation"
  }'
Revoked credentials show as invalid in verification checks and display revocation notices to viewers.
Yes, you can unrevoke credentials if the revocation was made in error.

Integration and Webhooks

Certification Webhooks

  • credential.issued - New credential issued
  • credential.verified - Credential verification performed
  • credential.revoked - Credential revoked
  • badge.earned - Badge awarded
  • program.completed - Program completion
Register webhook endpoints for certification events:
curl -X POST "https://api.hixbe.com/certify/webhooks" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Hixbe-Version: 2026-01-01" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://yourapp.com/webhooks/certify",
    "events": ["credential.issued", "credential.revoked"]
  }'
Verify webhook signatures and implement idempotency using event IDs to handle duplicate notifications.

Audit and Compliance

Audit Logging

All credential operations are logged: issuance, verification, revocation, viewing, and sharing activities.
Use the audit logs endpoint to retrieve activity history:
curl -X GET "https://api.hixbe.com/certify/audit-logs?credential_id=cred_123" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Hixbe-Version: 2026-01-01"
Audit logs are retained for 7 years to comply with regulatory requirements.

Testing and Development

Sandbox Testing

Use the sandbox environment to create test credentials without affecting production data.
Sandbox credentials have their own verification URLs and don’t appear in production verification systems.
No, sandbox and production are separate. You’ll need to recreate templates and credentials in production.

Performance and Scaling

Rate Limits and Scaling

Certification API allows 200 requests per minute per API key, with higher limits for enterprise accounts.
Use batch endpoints for issuing multiple credentials efficiently, or implement queuing for large volumes.
Yes, we provide integrations with popular LMS platforms like Moodle, Canvas, and custom systems.

Error Handling

Common Certification Errors

This credential ID is already in use. Use unique identifiers for each credential.
Credential data doesn’t match the template schema. Validate data before submission.
Credential verification failed. Check if the credential was revoked or tampered with.

Pricing and Billing

Certification Costs

Billing is typically per credential issued, with volume discounts available. Verification checks may have separate pricing.
Credentials are stored securely with no additional storage fees. Custom verification domains may have additional costs.
Enterprise plans offer unlimited credentials, white-labeling, and priority support.

Use Cases and Examples

Common Implementation Patterns

Issue certificates upon course completion, track learner progress, and provide verifiable proof of skills.
Create badge pathways for career development, maintain certification records, and enable easy verification.
Automatically issue certificates to event attendees, with QR codes for easy verification.

Need More Help?

Certification API Docs

Complete API reference

Webhooks

Set up credential event notifications

Error Handling

Handle credential errors

Best Practices

Credential integration best practices

Troubleshooting

Certification-specific issues

Support

Contact our support team