Skip to content
cursareDocs
Sign inGet started

Start here

  • Overview
  • Getting started
  • Platform concepts

Create

  • Content
  • Editor and blocks
  • Block reference

Publish & access

  • Publishing and access
  • Custom domain & white-label

Learners

  • Learner experience
  • Learners and enrollments
  • Progress and certificates

Teams & cohort

  • Teams
  • Cohorts

Sales

  • Offers & checkout
  • Payments & payouts
  • Affiliates
  • Links
  • Insights and reports

Admin

  • Organization & security
  • Subscription, trial & billing
  • Appearance
  • Members & roles
  • Audit log

Developer

  • Integrations
  • Google Classroom
  • Open Badges
  • Zoom
  • Learner UI registry
  • API keys & webhooks
  • MCP server
  • API reference
Explore the API

Open Badges credentials

Open Badges available in the organization app list

The credentials integration turns a completed course certificate into a signed, portable digital credential. Cursare keeps the academic result as the source of truth and delegates artifact generation to a separate provider. The first provider is the local Open Badges 3.0-based issuer.

Enable the issuer

  1. Open Settings → Apps → Open Badges.
  2. Enter the institution's public issuer name.
  3. Enter the institution's official HTTPS URL.
  4. Save the configuration.

On first activation, Cursare creates an Ed25519 key pair dedicated to the organization. The private key is encrypted; the public issuer document exposes only the verification key.

Learner experience

After the learner completes every step in the published version, the certificate page offers the credential download. The first request creates a vc+jwt artifact; later requests return the exact same credential.

The credential identifies the issuer, learner, completed content, completion date, and public verification URL. If the enrollment enters a refund state, the public lookup reports the credential as revoked.

Disconnect without breaking history

Disconnecting stops new issuance while retaining the public key and existing credentials. Previously delivered artifacts remain verifiable. Enabling the same issuer again reuses the current key so earlier signatures remain valid.

Interoperability, not certification

The artifact follows the structure of an OpenBadgeCredential verifiable credential. This release does not represent 1EdTech conformance certification for Cursare. Validate compatibility with a target wallet before making a specific commercial promise.

See the official Open Badges 3.0 specification for the standard and its formal requirements.

Provider architecture

digital_credentials is the organization capability and open_badges is the active provider. Enrollment rows contain no provider-specific fields. Issued records retain their format, signing key, and artifact, so a future provider can replace the current one without rewriting academic history.

Progress and certificatesUnderstand completion, verification, and revocation.IntegrationsReview every available capability and provider.
PreviousGoogle ClassroomNextZoom

Your privacy choices

The technical Tag Manager container is required to apply your choices. Analytics and marketing cookies and storage remain optional and stay off until you authorize them. Privacy Policy.

Sign-in, security, core functions and consent enforcement.

Audience measurement such as Google Analytics.

Marketing storage, campaign attribution and optional tags.